Enhancement of mobile device initiated transactions
US-2016132875-A1 · May 12, 2016 · US
US2022012723A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2022012723-A1 |
| Application number | US-202117474022-A |
| Country | US |
| Kind code | A1 |
| Filing date | Sep 13, 2021 |
| Priority date | Mar 12, 2015 |
| Publication date | Jan 13, 2022 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Methods, systems, and computer program products for replaying tokenized payment transactions are disclosed. A computer-implemented method may include generating or receiving a token for a tokenized payment transaction involving a merchant, creating an association between the token and the tokenized payment transaction, storing the association between the token and the tokenized payment transaction, providing the token to the merchant during the tokenized payment transaction to authorize payment, receiving a request from the merchant to provide the token during a subsequent transaction relating to the tokenized payment transaction, selecting a transaction record corresponding to the tokenized payment transaction to retrieve the token for the second transaction, and determining the token to provide to the merchant in the second transaction. In some examples, a non-payment identifier previously generated by a merchant or a user device is associated with the tokenized payment transaction and provided to the merchant to complete the second transaction.
Opening claim text (preview).
1 . (canceled) 2 . A method comprising: providing, by a user device, a payment token to a device associated with a merchant, the payment token for payment during a payment transaction between the user device and the device associated with the merchant, the payment token provided as a form of payment in the payment transaction; associating, by the user device, a non-payment identifier with the payment token and the tokenized payment transaction, wherein a digital receipt or a record indicates the association of the non-payment identifier, the payment token, and the payment transaction; determining, based on a second transaction, that the non-payment identifier is to be provided to the merchant for the second transaction that is related to the payment transaction; and providing the non-payment identifier to the merchant as part of the second transaction to allow the merchant to subsequently reference at least one detail of the payment transaction. 3 . The method of claim 2 , wherein the non-payment identifier is for subsequent retrieval of transaction data of the payment transaction. 4 . The method of claim 2 , wherein the second transaction involves a return of at least one item to the merchant, the item being a part of the payment transaction. 5 . The method of claim 2 , wherein second transaction is performed via a second device that is different from the user device, wherein both the user device and the second device are authenticated devices for a user, wherein the transaction and the second transaction are associated with the user. 6 . The method of claim 2 , wherein the non-payment identifier is a QR code or a bar code that is displayed by the user device for access by a merchant device associated with the merchant. 7 . The method of claim 6 , wherein the merchant device is the device, and wherein the QR code of the non-payment identifier is a part of the digital receipt. 8 . The method of claim 2 , wherein the non-payment identifier, the payment token, and a linkage between the non-payment identifier is stored at a server for retrieval by one or more of the user device and the device associated with the merchant. 9 . The method of claim 2 , wherein the second transaction is initiated by a second user device that is authenticated to use the non-payment identifier. 10 . A user device, comprising: a non-transitory memory storing instructions; and a processor configured to execute the instructions to cause the user device to: provide a payment token to a device associated with a merchant, the payment token for payment during a payment transaction between the user device and the device associated with the merchant; associate a non-payment identifier with the payment token and the tokenized payment transaction, said associating comprising storing the association of the non-payment identifier, the payment token, and the payment transaction; determine, based on a second transaction, that the non-payment identifier is to be provided to the merchant for the second transaction that is related to the payment transaction; and provide the non-payment identifier to the merchant during the second transaction to allow the merchant to subsequently reference at least one detail of the payment transaction. 11 . The device of claim 10 , wherein executing the instructions further causes the device to generate the non-payment identifier to identify the tokenized payment transaction. 12 . The device of claim 10 , wherein the second transaction involves a return of at least one item to the merchant, the item being a part of the payment transaction. 13 . The device of claim 10 , wherein the non-payment identifier is a QR code or a bar code that is displayed by the user device for access by a merchant device associated with the merchant. 14 . The device of claim 10 , wherein said providing the non-payment identifier comprises providing a QR code or a bar code, via a display the user device, for access by a merchant device associated with the merchant. 15 . The device of claim 10 , wherein the non-payment identifier is for subsequent retrieval of transaction data of the payment transaction. 16 . A non-transitory machine-readable medium having instructions stored thereon, the instructions executable to cause performance of operations comprising: providing a payment token to a device associated with a merchant, the payment token for payment during a payment transaction between a user device and the device associated with the merchant; associating a non-payment identifier with the payment token and the tokenized payment transaction, said associating comprising storing the association of the non-payment identifier, the payment token, and the payment transaction; determining, based on a second transaction, that the non-payment identifier is to be provided to the merchant for the second transaction that is related to the payment transaction; and providing the non-payment identifier to the merchant during the second transaction to allow the merchant to subsequently reference at least one detail of the payment transaction. 17 . The non-transitory machine-readable medium of claim 16 , wherein the operations further comprise generating the non-payment identifier to identify the tokenized payment transaction. 18 . The non-transitory machine-readable medium of claim 16 , wherein the second transaction involves a return of at least one item to the merchant, the item being a part of the payment transaction 19 . The non-transitory machine-readable medium of claim 16 , wherein the non-payment identifier is a QR code or a bar code that is displayed by the user device for access by a merchant device associated with the merchant. 20 . The non-transitory machine-readable medium of claim 16 , wherein said providing the non-payment identifier comprises providing a QR code or a bar code, via a display the user device, for access by a merchant device associated with the merchant. 21 . The non-transitory machine-readable medium of claim 16 , wherein the non-payment identifier is for subsequent retrieval of transaction data of the payment transaction.
Use of secure elements separate from M-devices · CPC title
involving electronic purses or money safes · CPC title
RFID or NFC payments by means of M-devices · CPC title
Establishing or using transaction specific rules · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.