Cardless challenge systems and methods

• US 10,262,308 B2
• Filed: 01/25/2012
• Issued: 04/16/2019
• Est. Priority Date: 06/25/2007
• Status: Active Grant

• Current Assignee: Visa USA, Inc. (Visa, Inc.)
• Original Assignee: Visa USA, Inc. (Visa, Inc.)
• Inventors: Carlson, Mark, Keshan, Surendra, Faith, Patrick
• Primary Examiner(s): Kucab, Jamie R
• Application Number:
  US13/358,472
• Publication Number:
  US 20120123882A1
• Time in Patent Office: 2,638 Days
• Field of Search: 705 17
• CPC Class Codes: G06Q 20/00 Payment architectures, schemes or protocols apparatus for performing or posting payment transactions G07F7/08, G07F19/00; electronic cash registers G07G1/12
• CPC Class Codes: G06Q 20/02 involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
• CPC Class Codes: G06Q 20/027 involving a payment switch or gateway
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• CPC Class Codes: G06Q 20/3227 using secure elements embedded in M-devices
• CPC Class Codes: G06Q 20/3674 involving authentication
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 20/385 using an alias or single-use codes
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 20/401 Transaction verification
• CPC Class Codes: G06Q 20/4016 involving fraud or risk level assessment in transaction processing
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]
• CPC Class Codes: G06Q 30/0613 Third-party assisted
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G06Q 40/03 Credit; Loans; Processing thereof

Abstract

Systems, methods, and apparatus for handling and/or authorizing payment requests by a consumer for a transaction are provided. Challenge questions may be presented from the non-merchant to the consumer after receiving the payment information, thereby allowing a judicious determination of when to ask such challenge questions and allowing complex and probative questions. The time limit for such challenge questions may advantageously be unconstrained, while still preserving security. Also, a risk analysis may be started prior to the consumer submitting payment information, thus allowing an efficient and complex risk analysis. Information about an access device used by the consumer may be obtained at the non-merchant from the access device with code sent to the access device from the merchant, and the device information may be used in the risk analysis.

Claims

1. A method for conducting a transaction between a consumer and a merchant, the method comprising:

providing a checkout request by an access device used by the consumer to a merchant server, the checkout request being used to initiate the transaction;

receiving by the access device, an electronic message comprising application page software code;

displaying an application page using the application page software code including a first payment option and a second payment option, wherein the first payment option is linked to a non-merchant server and the second payment option is linked to the merchant server;

collecting device information using the application page software code;

receiving, by the access device, a selection of the first payment option;

receiving, by the access device used by the consumer, payment information at the application page; and

transmitting, by the access device, the payment information received at the application page and the collected device information to the non-merchant server, wherein the non-merchant server analyzes the collected device information to determine a risk for the transaction and processes the transaction using the payment information,

wherein after receiving the application page software code, the merchant server sends transaction information from the merchant server to the non-merchant server.

2. The method of claim 1, wherein the access device is a computer terminal.

3. The method of claim 1, wherein the transaction information includes at least one of:

an amount of the transaction;

or

one or more items to be purchased in the transaction.

4. The method of claim 1, further comprising:

subsequent to sending the transaction information, sending an authorization request from the non-merchant server, to an issuer computer.

5. The method of claim 1, wherein the merchant server receives a response message regarding the transaction, and wherein response message includes a response as to whether the transaction is authorized.

6. The method of claim 5, wherein response message includes a correlation ID.

7. The method of claim 6, wherein the merchant server generates the correlation ID and sends the correlation ID to the consumer or to the non-merchant server.

8. The method of claim 6, wherein the merchant server matches the correlation ID to the transaction with the consumer.

9. The method of claim 1, wherein the checkout request includes a stock keeping unit (SKU).

10. The method of claim 1, wherein the application page is a webpage that provides checkout functionality for the merchant.

11. The method of claim 1, wherein the non-merchant server is in a payment processing network.

12. The method of claim 1, further comprising:

after transmitting the payment information, permanently erasing the payment information from the application page.

13. The method of claim 1, wherein the payment information does not include a bank identification number (BIN) and the non-merchant server adds the BIN based on the received payment information from the application page.

14. The method of claim 1, wherein the device information includes an internet protocol (IP) address for the access device, an operating system of the access device, a private value resulting from code running on the access device, a user identifier that is different than the payment information, or a type of browser used by the access device.

15. The method of claim 1, wherein the method further comprises:

sending the device information about the access device to the non-merchant server not operated by the merchant.

16. A computer program product comprising a non-transitory computer readable medium storing a plurality of instructions that when executed by one or more processors direct the one or more processors to perform operations for conducting a transaction between a consumer and a merchant, the operations comprising:

providing a checkout request to a merchant server, the checkout request being used to initiate the transaction;

receiving an electronic message comprising application page software code;

displaying an application page using the application page software code including a first payment option and a second payment option, wherein the first payment option is linked to a non-merchant server and the second payment option is linked to the merchant server;

collecting device information using the application page software code;

receiving a selection of the first payment option;

receiving payment information at the application page; and

transmitting the payment information received at the application page and the collected device information to the non-merchant server, wherein the non-merchant server analyzes the collected device information to determine a risk for the transaction and processes the transaction using the payment information,

wherein after receiving the application page software code, the merchant server sends transaction information from the merchant server to the non-merchant server.

17. An access device comprising:

one or more processors; and

one or more memory devices containing instructions for directing the one or more processors to perform a method comprising;

providing a checkout request to a merchant server, the checkout request being used to initiate a transaction;

receiving an electronic message comprising application page software code;

displaying an application page using the application page software code including a first payment option and a second payment option, wherein the first payment option is linked to a non-merchant server and the second payment option is linked to the merchant server;

collecting device information using the application page software code;

receiving, by the access device, a selection of the first payment option;

receiving payment information at the application page; and

transmitting, by the access device, the payment information received at the application page and the collected device information to the non-merchant server, wherein the non-merchant server analyzes the collected device information to determine a risk for the transaction and processes the transaction using the payment information,

wherein after receiving the application page software code, the merchant server sends transaction information from the merchant server to the non-merchant server.