Systems and methods for secure and transparent cardless transactions
First Claim
Patent Images
1. A method for authorizing a transaction between a consumer and a merchant, the method comprising:
- receiving, at a server of a non-merchant entity, a consumer message from an access device used by the consumer, wherein the consumer message includes;
account information that identifies an account of the consumer to be used for the transaction; and
a transaction identifier that identifies the transaction and that is different from the account information;
receiving, at the non-merchant server, an amount associated with the transaction, wherein the transaction identifier is separate from the amount associated with the transaction;
sending, to a merchant server from the non-merchant server, a funding message including the transaction identifier, wherein the funding message is an authorization response message indicating whether the transaction is approved or not approved, and wherein the non-merchant server sends the funding message after receiving the consumer message; and
providing, to the merchant server from the non-merchant server, code that is incorporated into an application page that is sent from the merchant to the consumer before the non-merchant server receives the consumer message, wherein the code provides a link to other code that directs the consumer message to the non-merchant server, the consumer message being created from information in the application page, andwherein the consumer is not required to enroll in any program or service or to have been previously enrolled in any program or service before sending the consumer message.
1 Assignment
0 Petitions
Accused Products
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.
393 Citations
30 Claims
-
1. A method for authorizing a transaction between a consumer and a merchant, the method comprising:
-
receiving, at a server of a non-merchant entity, a consumer message from an access device used by the consumer, wherein the consumer message includes; account information that identifies an account of the consumer to be used for the transaction; and a transaction identifier that identifies the transaction and that is different from the account information; receiving, at the non-merchant server, an amount associated with the transaction, wherein the transaction identifier is separate from the amount associated with the transaction; sending, to a merchant server from the non-merchant server, a funding message including the transaction identifier, wherein the funding message is an authorization response message indicating whether the transaction is approved or not approved, and wherein the non-merchant server sends the funding message after receiving the consumer message; and providing, to the merchant server from the non-merchant server, code that is incorporated into an application page that is sent from the merchant to the consumer before the non-merchant server receives the consumer message, wherein the code provides a link to other code that directs the consumer message to the non-merchant server, the consumer message being created from information in the application page, and wherein the consumer is not required to enroll in any program or service or to have been previously enrolled in any program or service before sending the consumer message. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18)
-
-
19. A system for authorizing a transaction between a consumer and a merchant, the system comprising:
-
a server having an external interface for receiving a consumer message from an access device used by the consumer, wherein the consumer message includes; account information that identifies an account of the consumer to be used for the transaction; and a transaction identifier that identifies the transaction and that is different from the account information, and wherein the server is associated with a non-merchant entity; one or more processors; and one or more memory devices containing instructions for directing the one or more processors to; receive, at the non-merchant server, an amount associated with the transaction, wherein the transaction identifier is separate from the amount associated with the transaction; send, to a merchant server from the non-merchant server, a funding message including the transaction identifier, wherein the funding message is an authorization response message indicating whether the transaction is approved or not approved, and wherein the non-merchant server sends the funding message after receiving the consumer message; and provide, to the merchant server from the non-merchant server, code that is incorporated into an application page that is sent from the merchant to the consumer before the non-merchant server receives the consumer message, wherein the code provides a link to other code that directs the consumer message to the non-merchant server, wherein the consumer is not required to enroll in any program or service or to have been previously enrolled in any program or service before sending the consumer message. - View Dependent Claims (20, 21, 22, 23)
-
-
24. A computer program product comprising a non-transitory computer readable medium encoded with a plurality of instructions for controlling a processor to perform an operation for authorizing a transaction between a consumer and a merchant, the instructions comprising:
-
receiving, at a server of a non-merchant entity, a consumer message from an access device used by the consumer, wherein the consumer message includes; account information that identifies an account of the consumer to be used for the transaction; and a transaction identifier that identifies the transaction and that is different from the account information; receiving, at the non-merchant server, an amount associated with the transaction, wherein the transaction identifier is separate from the amount associated with the transaction; and sending, to a merchant server from the non-merchant server, a funding message including the transaction identifier, wherein the funding message is an authorization response message indicating whether the transaction is approved or not approved, and wherein the non-merchant server sends the funding message after receiving the consumer message; and providing, to the merchant server from the non-merchant server, code that is incorporated into an application page that is sent from the merchant to the consumer before the non-merchant server receives the consumer message, wherein the code provides a link to other code that directs the consumer message to the non-merchant server, the consumer message being created from information in the application page, and wherein the consumer is not required to enroll in any program or service or to have been previously enrolled in any program or service before sending the consumer message. - View Dependent Claims (25, 26, 27, 28, 29, 30)
-
Specification