US2021264434A1PendingUtilityA1

System and method using merchant token

Assignee: VISA INT SERVICE ASSPriority: Jun 17, 2013Filed: May 12, 2021Published: Aug 26, 2021
Est. expiryJun 17, 2033(~6.9 yrs left)· nominal 20-yr term from priority
Inventors:John F. Sheets
G06Q 20/401G06Q 20/32G06Q 20/4016G06Q 20/20G06Q 20/3226H04L 2463/102H04L 12/1457G06Q 20/385G06Q 20/40G06Q 20/3276G06Q 20/3674
67
PatentIndex Score
0
Cited by
0
References
0
Claims

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

exact text as granted — not AI-modified
1 .- 16 . (canceled) 
     
     
         17 . A computer-implemented method comprising:
 receiving, by a first server computer and from a communication device, a transaction request message for a transaction, the transaction request message comprising a merchant token, and transaction data comprising a transaction amount, after the communication device obtains the merchant token from a merchant access device;   determining, by the first server computer, a merchant account identifier associated with associated with the merchant token; and   sending, by the first server computer, a message comprising the merchant account identifier to a second server computer that holds a merchant account associated with the merchant account identifier, wherein the merchant account is credited with the transaction amount.   
     
     
         18 . The method of  claim 17 , wherein the message is an authorization response message. 
     
     
         19 . The method of  claim 17 , wherein the message is an OCT message. 
     
     
         20 . The method of  claim 17 , wherein the merchant access device displays the merchant token in the form of a QR code. 
     
     
         21 . The method of  claim 17 , wherein the transaction request message comprises a consumer identifier associated with a consumer operating the communication device. 
     
     
         22 . The method of  claim 17 , wherein the merchant account identifier is in the form of a primary account number (PAN). 
     
     
         23 . The method of  claim 17 , wherein the merchant token is dynamic and changes with each transaction. 
     
     
         24 . The method of  claim 17 , wherein the merchant access device is a merchant POS terminal. 
     
     
         25 . The method of  claim 17 , wherein the first server computer is a payment processing network computer. 
     
     
         26 . The method of  claim 17 , wherein the message is transmitted to a merchant computer by the second server computer after the second server computer receives the message. 
     
     
         27 . The method of  claim 17 , wherein a consumer operating the communication device is prompted to provide confirmation to initiate the transaction before the transaction request message is sent to the first server computer. 
     
     
         28 . The method of  claim 17 , wherein the message is modified to include the merchant identifier before the message is sent to the second server computer. 
     
     
         29 . A first server computer comprising:
 a processor; and   a computer readable medium coupled to the processor, the computer readable medium comprising code, executable by the processor for causing the processor to implement operations comprising:   receiving, from a communication device, a transaction request message for a transaction, the transaction request message comprising a merchant token, and transaction data comprising a transaction amount, after the communication device obtains the merchant token from a merchant access device;   determining a merchant account identifier associated with associated with the merchant token; and   sending a message comprising the merchant account identifier to a second server computer that holds a merchant account associated with the merchant identifier, wherein the merchant account is credited with the transaction amount.   
     
     
         30 . The first server computer of  claim 29 , wherein the first server computer is a payment processing network computer. 
     
     
         31 . The first server computer of  claim 29 , wherein the message is an authorization response message. 
     
     
         32 . The first server computer of  claim 29 , wherein the message is an OCT message. 
     
     
         33 . The first server computer of  claim 29 , wherein the merchant identifier is a deposit only merchant identifier. 
     
     
         34 . The first server computer of  claim 29 , wherein the merchant identifier is sixteen characters long. 
     
     
         35 . A method comprising:
 receiving, by a communication device, a merchant token from an access device; and   transmitting, by the communication device, a transaction request message comprising the merchant token and transaction data comprising a transaction amount to a first server computer, after the communication device obtains the merchant token from a merchant access device, wherein the first server computer determines a merchant account identifier associated with associated with the merchant token, and sends a message comprising the merchant account identifier to a second server computer that holds a merchant account associated with the merchant identifier, wherein the merchant account is credited with the transaction amount.   
     
     
         36 . The method of  claim 35 , wherein the merchant account is a deposit only account.

Join the waitlist — get patent alerts

Track US2021264434A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.