Systems and methods for secure and transparent cardless transactions
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.
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.
2. The method of claim 1 , further comprising sending, from the non-merchant server to an acquirer, a payment identifier associated with the consumer's account.
3. The method of claim 1 , wherein the account information includes a credit card number.
4. The method of claim 1 , wherein the non-merchant server is part of a payment processing network, further comprising:
sending an authorization request from the non-merchant server to an issuer of the account; and
receiving an authorization response from the issuer, wherein the authorization response message is based on the authorization response from the issuer.
5. The method of claim 1 , wherein the account information includes an account identifier, and wherein the funding message includes a payment identifier.
6. The method of claim 5 , wherein the payment identifier is not the account identifier, further comprising:
creating, at the non-merchant server, the payment identifier;
associating the payment identifier with the account identifier; and
receiving the payment identifier from an acquirer as part of an authorization request.
7. The method of claim 1 , further comprising:
prior to receiving the consumer message, receiving, at the non-merchant server from the merchant server, a transaction message including the transaction identifier.
8. The method of claim 7 , wherein receiving the amount associated with the transaction is accomplished via the transaction message.
9. The method of claim 1 , wherein the consumer message is directed to the non-merchant server when the consumer selects a particular payment method.
10. The method of claim 1 , wherein the access device used by the consumer is in a retail store associated with the merchant.
11. The method of claim 1 , wherein the consumer message is transmitted via a network connection between the access device and the non-merchant server.
12. The method of claim 1 , wherein the consumer message is transmitted via SMS or MMS.
13. The method of claim 1 , wherein the account information includes an account identifier, wherein the non-merchant entity is associated with an issuer of the consumer's account, and wherein the non-merchant entity creates at least a portion of the account identifier.
14. The method of claim 13 , wherein the portion of the account identifier is a Bank Identification Number (BIN) that is associated with the issuer.
15. The method of claim 1 , wherein no account information of the consumer's account is sent to the merchant or received from the merchant during the transaction.
16. The method of claim 1 , wherein the transaction identifier ties together messages associated with the same transaction.
17. The method of claim 16 , wherein the transaction identifier is a value used internally by the merchant to track transactions.
18. The method of claim 1 , wherein the other code is stored on the non-merchant server.
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.
20. The system of claim 19 , wherein the one or more processors are further configured to send, to an acquirer, a payment identifier associated with the consumer's account.
21. The system of claim 19 , wherein the one or more processors are further configured to:
send an authorization request from the non-merchant server to an issuer of the account; and
receive an authorization response from the issuer, wherein the response message is based on the authorization response from the issuer.
22. The system of claim 19 , wherein the account information includes an account identifier, and wherein the funding message includes a payment identifier that is not the account identifier, wherein the one or more processors are further configured to:
create, at the non-merchant server, the payment identifier; and
associate the payment identifier with the account identifier.
23. The system of claim 19 , wherein the one or more processors are further configured to:
prior to receiving the consumer message, receive, at the non-merchant server from the merchant server, a transaction message including the transaction identifier.
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.
25. The computer program product of claim 24 , wherein the instructions further comprise:
sending, to an acquirer, a payment identifier associated with the consumer's account.
26. The computer program product of claim 24 , wherein the non-merchant server is part of a payment processing network, wherein the instructions further comprise:
sending an authorization request from the non-merchant server to an issuer of the account; and
receiving an authorization response from the issuer, wherein the authorization response message is based on the authorization response from the issuer.
27. The computer program product of claim 24 , wherein the account information includes an account identifier, and wherein the funding message includes a payment identifier.
28. The computer program product of claim 27 , wherein the payment identifier is not the account identifier, wherein the instructions further comprise:
creating, at the non-merchant server, the payment identifier; and
associating the payment identifier with the account identifier.
29. The computer program product of claim 24 , wherein the instructions further comprise:
prior to receiving the consumer message, receiving, at the non-merchant server from the merchant server, a transaction message including the transaction identifier.
30. The computer program product of claim 24 , wherein the account information includes an account identifier, wherein the non-merchant entity is associated with an issuer of the consumer's account, and wherein the non-merchant entity creates at least a portion of the account identifier.