SYSTEM AND METHOD USING MERCHANT TOKEN

• US 20140372308A1
• Filed: 06/16/2014
• Published: 12/18/2014
• Est. Priority Date: 06/17/2013
• Status: Active Grant

• Current Assignee: Visa International Service Association (Visa, Inc.)
• Original Assignee: Visa International Service Association (Visa, Inc.)
• Inventors: Sheets, John
• Granted Patent: US 10,878,422 B2
• Time in Patent Office: Days
• US Class Current: 705/44
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/32 using wireless devices
• CPC Class Codes: G06Q 20/3226 Use of secure elements separate from M-devices
• CPC Class Codes: G06Q 20/3276 using a pictured code, e.g. barcode or QR-code, being read by the M-device
• CPC Class Codes: G06Q 20/3674 involving authentication
• 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: H04L 12/1457 using an account
• CPC Class Codes: H04L 2463/102 applying security measure for e-commerce data processing systems or methods, specially adapted for e-commerce G06Q30/00

Abstract

A merchant computer generates a token including a “pay-me” merchant account identifier and transaction data for a transaction conducted by a consumer. The merchant token can be obtained by a mobile communication device and transmitted to a payment processing network along with a device identifier for the mobile communication device and an authentication token provided by the consumer. The payment processing network can authenticate the device using the authentication token, retrieve a consumer account number based on the device identifier, and complete the transaction by pushing money into the merchant “pay-me” account from the consumer account.

Claims

1. A method comprising:

receiving, by a mobile communication device, a merchant token from an access device for a transaction, wherein the merchant token comprises a merchant account identifier and transaction data;

receiving, by the mobile communication device, an authentication token from a consumer operating the mobile communication device;

generating, by the mobile communication device, a transaction request message comprising the merchant token and the authentication token;

sending, by the mobile communication device, the transaction request message to a server computer; and

receiving a confirmation message that the transaction has been processed.

2. The method of claim 1, wherein the transaction request message further comprises a mobile communication device identifier for the mobile communication device,

wherein the server computer is configured to determine a consumer primary account number associated with the consumer using the mobile communication device identifier.

3. The method of claim 2, wherein the merchant account identifier is for a credit only account and is in a same format as a primary account number, wherein the server computer is further configured to:

send an authorization request message comprising the consumer'"'"'s primary account number to an issuer computer operated by an issuer that issued the consumer'"'"'s primary account number;

receive an authorization response message including the consumer'"'"'s primary account number from the issuer;

replace the consumer'"'"'s primary account number with the merchant account identifier to form a modified authorization response message; and

forward the modified authorization response message to the access device.

4. The method of claim 1, wherein the merchant token is generated by a merchant computer communicatively coupled to the access device.

5. The method of claim 1, wherein the merchant token is in the form of a machine readable code.

6. The method of claim 1, wherein the authentication token is a voice input by the consumer.

7. A mobile communication device comprising:

a processor; and

a computer readable medium comprising code, executable by the processor, for implementing a method comprising;

receiving, by the mobile communication device, a merchant token from an access device for a transaction, wherein the merchant token comprises a merchant account identifier, and transaction data;

receiving, by the mobile communication device, an authentication token from a consumer operating the mobile communication device;

generating, by the mobile communication device, a transaction request message comprising the merchant token and the authentication token;

sending, by the mobile communication device, the transaction request message to a server computer; and

receiving a confirmation message that the transaction has been processed.

8. The mobile communication device of claim 7, wherein the mobile communication device further comprises a secure element coupled to the processor.

9. The mobile communication device of claim 7, wherein the merchant token is in the form of a machine readable code.

10. The mobile communication device of claim 7, wherein the mobile communication device is a mobile phone.

11. A method comprising:

receiving, by a server computer, a transaction request message comprising a merchant token comprising a merchant account identifier, transaction data comprising a transaction amount, and a mobile communication device identifier or a consumer account identifier;

generating, by the server computer, an authorization request message comprising the transaction amount and the consumer account identifier;

sending, by the server computer, the authorization request message comprising the consumer account identifier to an issuer computer operated by an issuer that issued the consumer account identifier;

receiving, by the server computer, an authorization response message from the issuer computer comprising the consumer account identifier;

replacing, by the server computer, the consumer account identifier with the merchant account identifier to create a modified authorization response message; and

sending, by the server computer, the modified authorization response message to the merchant.

12. The method of claim 11 wherein the merchant account identifier is a one time use merchant account identifier.

13. The method of claim 11 wherein the mobile communication device identifier is received at the server computer, and wherein the method further comprises:

determining the consumer account identifier from the mobile communication device identifier before generating the authorization request message.

14. A server computer comprising a processor and a computer readable medium coupled to the processor, the computer readable medium comprising code, executable by the processor to implement a method comprising:

receiving a transaction request message comprising a merchant token comprising a merchant account identifier, transaction data comprising a transaction amount, and a mobile communication device identifier or a consumer account identifier;

generating an authorization request message comprising the transaction amount and the consumer account identifier;

sending the authorization request message comprising the consumer account identifier to an issuer computer operated by an issuer that issued the consumer account identifier;

receiving an authorization response message from the issuer computer comprising the consumer account identifier;

replacing the consumer account identifier with the merchant account identifier to create a modified authorization response message; and

sending the modified authorization response message to the merchant.

15. The server computer of claim 14 wherein the merchant account identifier is a one time use merchant account identifier.

16. The server computer of claim 14 wherein the mobile communication device identifier is received at the server computer, and wherein the method further comprises:

determining the consumer account identifier from the mobile communication device identifier before generating the authorization request message.