SECONDARY AUTHENTICATION OF NETWORK TRANSACTIONS

• US 20170186003A1
• Filed: 12/28/2015
• Published: 06/29/2017
• Est. Priority Date: 12/28/2015
• Status: Active Application

• Current Assignee: NCR Corporation
• Original Assignee: NCR Corporation
• Inventors: Monaghan, Andrew David
• Application Number:
  US14/979,894
• Publication Number:
  US 20170186003A1
• Time in Patent Office: Days
• CPC Class Codes: G06Q 20/4016 involving fraud or risk level assessment in transaction processing
• CPC Class Codes: G06Q 20/405 Establishing or using transaction specific rules
• CPC Class Codes: G06Q 20/425 using two different networks, one for transaction and one for security confirmation

Abstract

Various embodiments herein each include at least one of systems, methods, and software for secondary authentication of network transactions. Some such embodiments, for example, provide a secondary authentication channel to authenticate and authorize payment tendering with a bankcard, payment account, and the like. One method embodiment includes determining whether to approve an account authorization request in view of other data stored in a database with regard to the account. When determined that the account authorization request is denied, transmitting a request to obtain a secondary authorization of the account authorization request.

Claims

1. A method comprising:

receiving an account payment authorization request for an amount that exceeds an allowed amount for the account;

applying a rule against the account payment authorization request and other data available in a database with regard to the account to determine whether to approve the account payment authorization request; and

when application of the rule determines that the account payment authorization request is denied, transmitting a request to obtain a secondary authorization of the account payment authorization request.

2. The method of claim 1, wherein:

the rule identifies a plurality of data items to consider as factors, which when present in the database are assigned weighted values based on the respective values of the data items; and

the rule defines at least one of one or more individual weighted values and a sum of weighted values that determine whether the account payment authorization request is to be approved or denied subject to obtaining the secondary authorization.

3. The method of claim 1, wherein receiving the account payment authorization request includes receiving a payment authorization request from an entity receiving a payment tender associated with the account of the account payment authorization request.

4. The method of claim 3, wherein the payment tender is received through a provisioning of one of a bankcard, a wireless signal from a customer device, and a set of bankcard or account data via an input mechanism of a computing device.

5. The method of claim 1, wherein transmitting the secondary authorization request is performed via one or more transmission mechanisms as defined within data in association with the account.

6. The method of claim 1, wherein transmitting the secondary authorization request includes transmitting a request for secondary authorization input via at least one of:

an SMS message to a mobile device of a holder of the account;

an in-app message to an app that executes on a mobile device of the holder of the account;

an electronic message to a teller or clerk station located in proximity to a location where the account payment authorization request originated; and

an automated interactive voice response telephone call to a phone number associated with the holder of the account.

7. The method of claim 1, further comprising:

receiving a satisfactory reply to the request for secondary authorization; and

approving the account payment authorization request.

8. The method of claim 1, wherein the other data available in the database includes:

data identifying, or from which an identification can be made of, a location from which a holder of the account last logged in to the account;

data identifying a date, time, and location of at least one recent transaction; and

a detected location of a mobile device of the holder of the account.

9. The method of claim 1, wherein the allowed amount for the account is zero based on a prior potential or actual account fraud activity determination.

10. A multi-channel authorization method comprising:

receiving a transaction request from a customer via a first channel;

ascertaining whether additional authentication is required based on an acceptable risk criterion;

gathering enrichment evidence from an evidence supplier without customer or staff member interaction in the event that the acceptable risk criterion is not met; and

fulfilling the transaction in the event that the enrichment evidence meets an acceptance criterion.

11. The method of claim 10, wherein the acceptable risk criterion is met when the transaction is for a value below a transaction threshold.

12. The method of claim 11, wherein the accept risk criterion is also met when the transaction is similar to a previous accepted transaction or in a location previously used for accepted transactions.

13. The method of claim 10, wherein the evidence supplier includes at least one of:

a beacon located in a bank branch or other transaction fulfillment center; and

a repository storing login information for the customer'"'"'s online or mobile banking facility.

14. The method of claim 10, wherein the acceptance criterion comprises:

a transaction request originating at a physical location or online location that is consistent with a detected physical or online presence of the customer at a time proximate to when the transaction request was submitted.

15. The method of claim 10, further comprising:

requesting a secondary form of authentication from the customer in the event that the acceptance criterion is not met; and

fulfilling the transaction when the secondary form of authentication is validated.

16. A multi-channel authentication system comprising:

a first transaction channel located in a fulfillment center; and

a multi-channel authentication controller coupled to the first transaction channel, the multi-channel authentication controller including a processor and a memory storing instructions executable on the processor to perform data processing activities comprising;

receiving a transaction from the first transaction channel and the mobile device carried by the customer; and

approving the received transaction based in part on a beacon device identifier of a beacon device reported by a mobile device app that executes on the mobile device carried by the customer, the beacon device of the beacon device identifier located proximately to the the fulfillment center.

17. The multi-channel authentication system of claim 16, wherein the transaction fulfillment center is at least one of a bank branch, a retail outlet, a restaurant, and a controlled access point.

18. The multi-channel authentication system of claim 16, wherein the first transaction channel is at least one of a self-service terminal, a teller counter, an an assisted service terminal.