Systems and methods for secure and transparent cardless transactions

• US 8,606,700 B2
• Filed: 01/25/2012
• Issued: 12/10/2013
• 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): Norman, Samica L
• Application Number:
  US13/358,475
• Publication Number:
  US 20120150744A1
• Time in Patent Office: 685 Days
• Field of Search: 705/39, 705/44, 705/26, 705/26.81, 235/380
• US Class Current: 705/39
• 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. Payment information can be sent directly from a consumer to a non-merchant, thereby allowing no new entities to obtain the payment information. Transaction identifiers can be used to facilitate communications among the entities. The payment information can be sent to the non-merchant via a merchant application with a submit payment button directed to the non-merchant so little or no deviations from standard practices are required.

Claims

1. A method for requesting authorization of a transaction between a consumer and a merchant, the method comprising:

providing, to a server of the merchant by the consumer, a checkout request to initiate a transaction;

receiving, from the merchant server by an access device used by the consumer, a first code for displaying an application page containing a payment object directed to a server of a non-merchant entity;

receiving a selection of the payment object; and

sending, to a server of the non-merchant entity, a consumer message from the access device, wherein the consumer message includes;

account information of an account of the consumer to be used for the transaction; and

a transaction identifier corresponding to the transaction.

2. The method of claim 1, wherein the payment object is a submit payment element.

3. The method of claim 2, further comprising:

displaying an application page containing a plurality of payment mechanism options for the transaction, wherein a first subset of the payment mechanism options includes one or more first payment mechanisms; and

receiving a selection of one of the first payment mechanisms, wherein when a first payment mechanism is selected, a destination address of the payment object on the application page is the non-merchant server.

4. The method of claim 3, wherein when a payment mechanism not in the first subset is selected, a destination address of a submit payment element on the application page is the merchant server.

5. The method of claim 2, further comprising:

determining, via the first code, whether to change the destination of the submit payment element based on the selection of a payment mechanism.

6. The method of claim 1, wherein the payment object is a payment mechanism option.

7. The method of claim 6, further comprising:

when the payment mechanism option is activated, sending, from the access device to the non-merchant server, a transaction message including transaction information.

8. The method of claim 7, wherein the checkout request includes one or more items to be purchased in the transaction, and wherein the transaction message includes the items and an amount of the transaction.

9. The method of claim 6, wherein the payment mechanism option is directed to the non-merchant server via a link, the method further comprising:

using the link to retrieve code to display a submit payment element with the destination address directed to the non-merchant server.

10. The method of claim 9, wherein the link is an IFrame.

11. The method of claim 1, wherein the consumer is not required to enroll in a program or service or to have been previously enrolled in a program or service before sending the consumer message.

12. 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 an operation for conducting a transaction between a consumer and a merchant, the instructions comprising:

providing, to a server of the merchant by the consumer, a checkout request to initiate a transaction;

receiving, from the merchant server by an access device used by the consumer, a first code for displaying an application page containing a payment object directed to a server of a non-merchant entity;

receiving a selection of the payment object; and

sending, to a server of the non-merchant entity, a consumer message from the access device, wherein the consumer message includes;

account information of an account of the consumer to be used for the transaction; and

a transaction identifier corresponding to the transaction.

13. A system for conducting a transaction between a consumer and a merchant, the system comprising:

a server having an external interface, wherein the server is associated with the merchant;

one or more processors; and

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

providing, to a server of the merchant by the consumer, a checkout request to initiate a transaction;

receiving, from the merchant server by an access device used by the consumer, a first code for displaying an application page containing a payment object directed to a server of a non-merchant entity;

receiving a selection of the payment object; and

sending, to a server of the non-merchant entity, a consumer message from the access device, wherein the consumer message includes;

account information of an account of the consumer to be used for the transaction; and

a transaction identifier corresponding to the transaction.

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

receiving, at a server of the merchant from an access device used by the consumer, a checkout request to initiate a transaction;

providing, from the merchant server to the access device, a first code for displaying an application page containing a payment object directed to a server of a non-merchant entity,

wherein after activation of the payment object a consumer message is sent from the access device to the non-merchant server,

wherein the consumer message includes;

account information of an account of the consumer to be used for the transaction; and

a transaction identifier corresponding to the transaction.

15. The method of claim 14, wherein the payment object is a submit payment element.

16. The method of claim 15, further comprising:

providing, from the merchant server to the access device, a second code for displaying an application page containing a plurality of payment mechanism options for the transaction, wherein a first subset of the payment mechanism options includes one or more first payment mechanisms,

wherein when one of the first payment mechanisms is selected, a destination address of the submit payment element on the application page is a server not operated by the merchant.

17. The method of claim 15, wherein the first code determines whether to change the destination of the submit payment element based on the selection of a payment mechanism.

18. The method of claim 14, wherein the payment object is a payment mechanism option.

19. The method of claim 18, further comprising:

receiving, at the merchant server from the access device, a selection of one of the payment mechanism option; and

sending a link to the access device such that code is served from the non-merchant server to display a submit payment element with the destination address directed to the non-merchant server.

20. The method of claim 19, wherein the link is an IFrame.

21. The method of claim 18, wherein activation of the payment mechanism option sends, from the access device to the non-merchant server, a transaction message including transaction information.

22. The method of claim 21, wherein the checkout request includes one or more items to be purchased in the transaction, and wherein the transaction message includes the items and an amount of the transaction.

23. The method of claim 14, further comprising:

creating, at the merchant server, a transaction identifier corresponding to the transaction;

sending, from the merchant server to the access device, the transaction identifier; and

receiving, at the merchant server from the non-merchant server, a response message regarding the transaction, wherein the response message includes the transaction identifier.

24. The method of claim 23, wherein the account information includes an account identifier, and wherein the response message includes a payment identifier associated with the account of the consumer, further comprising:

sending, from the merchant server, an authorization request using the payment identifier received from the non-merchant server,

wherein the payment identifier is not the account identifier, and wherein only the non-merchant server knows the association between the payment identifier and the account identifier.

25. 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 an operation for conducting a transaction between a consumer and a merchant, the instructions comprising:

receiving, at a server of the merchant from an access device used by the consumer, a checkout request to initiate a transaction;

providing, from the merchant server to the access device, a first code for displaying an application page containing a payment object directed to a server of a non-merchant entity,

wherein after activation of the payment object a consumer message is sent from the access device to the non-merchant server,

wherein the consumer message includes;

account information of an account of the consumer to be used for the transaction; and

a transaction identifier corresponding to the transaction.

26. A system for conducting a transaction between a consumer and a merchant, the system comprising:

a server having an external interface, wherein the server is associated with the merchant;

one or more processors; and

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

receiving, at a server of the merchant from an access device used by the consumer, a checkout request to initiate a transaction;

providing, from the merchant server to the access device, a first code for displaying an application page containing a payment object directed to a server of a non-merchant entity,

wherein after activation of the payment object a consumer message is sent from the access device to the non-merchant server,

wherein the consumer message includes;

account information of an account of the consumer to be used for the transaction; and

a transaction identifier corresponding to the transaction.