IP Library › Granted Patent US 11,715,101
Granted Patent B2
US 11,715,101 · App. 17/565,546 · Granted Aug 1, 2023

Single-use payment tokens

Inventors: Aaron Braundmeier (O'Fallon, MO); Anthony Hake (Lake St Louis, MO)
Assignee: MASTERCARD INTERNATIONAL INCORPORATED
G06Q20/385
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,715,101
App. No.
17/565,546
Granted
Aug 1, 2023
Kind
B2
Abstract

Provided are systems and methods for managing and implementing single-use payment-enabled tokens. In one example, a method may include distributing, via a server, a payment-enabled token to a payment application on a computing device, the payment-enabled token being mapped to a payment account of the payment application via a tokenization service, detecting use of the payment-enabled token as a payment via the payment application, and in response to the detecting, deactivating the payment-enabled token at the server and storing an identifier of the payment-enabled token and an additional data element of the payment-enabled token that identifies the payment account together within a data structure of the server.

Claims (34)

1. A computing system comprising:

a storage device; and

a processor configured to

distribute a payment-enabled token to a hardware element on a user device which includes a payment application installed therein, and store a mapping of the payment-enabled token to a payment account number (PAN) held in the payment application via the storage device,

detect an initial use of the payment-enabled token as a form of payment within a payment transaction by the payment application via a submission of the payment-enabled token to an electronic payment network coupled to the tokenization service,

in response to detection of the initial use of the payment-enabled token, deactivate the payment-enabled token via the tokenization service, and change the mapping in the storage device to indicate that the payment-enabled token is no longer mapped to the PAN, wherein the changing comprises changing the mapping in the storage device to map a payment account reference (PAR) value of the payment-enabled token which links back to the PAN to an identifier of the payment-enabled token within one or more of a table, a document, and a file in the storage device,

receive a request to access the payment transaction made with the deactivated payment-enabled token, wherein the request comprises an identifier of the payment-enabled token, and

map the identifier of the payment-enabled token to the PAN based on the changed mapping in the storage device, and accessing content from the payment transaction based on the PAN.

2. The computing system of claim 1 , wherein the PAR value comprises a twenty-nine character alphanumeric data element including four characters dedicated to a bin controller.

3. The computing system of claim 1 , wherein the processor is configured to pull the payment-enabled token out of a pool of available single-use tokens stored in the storage device and store the payment-enabled token in a temporary pool of deactivated single-use tokens stored in the storage device.

4. The computing system of claim 3 , wherein the processor is further configured to return the payment-enabled token to the pool of available single-use tokens in the storage device after expiration of a predetermined amount of time.

5. The computing system of claim 1 , wherein the processor is configured to attach a deactivation flag to the payment-enabled token in the storage device which distinguishes the payment-enabled token from other single-use tokens that are not deactivated within the storage device.

6. The computing system of claim 1 , wherein the processor is further configured to generate and execute a time-to-live job which comprises a pointer to the payment-enabled token stored in the storage device, detect expiration of a predefined period of time based on the execution of the time-to-live job, and in response to the detection, return the payment-enabled token to a pool of available payment-enabled tokens.

7. The computing system of claim 1 , wherein the processor is further configured to receive a refund request for the payment transaction made via the payment-enabled token, and in response, verify the payment-enabled token corresponds to the PAN based on the changed mapping of the payment-enabled token in the storage device.

8. A method comprising:

distributing a payment-enabled token to a hardware element on a user device which includes a payment application installed therein, and store a mapping of the payment-enabled token being to a payment account number (PAN) held in the payment application via the storage device;

detecting an initial use of the payment-enabled token as a form of payment by the payment application via a submission of the payment-enabled token to an electronic payment network coupled to the tokenization service;

in response to the detecting the initial use of the payment-enabled token, deactivating the payment-enabled token via the tokenization service, and changing the mapping in the storage device to indicate that the payment-enabled token is no longer mapped to the payment account, wherein the changing comprises changing the mapping in the storage device to map a payment account reference (PAR) value of the payment-enabled token which links back to the PAN to an identifier of the payment-enabled token within one or more of a table, a document, and a file in the storage device;

receiving a request to access the payment transaction made with the deactivated payment-enabled token, wherein the request comprises an identifier of the payment-enabled token; and

mapping the identifier of the payment-enabled token to the PAN based on the changed mapping in the storage device, and accessing content from the payment transaction based on the PAN.

9. The method of claim 8 , wherein the PAR value comprises a twenty-nine character alphanumeric data element including four characters dedicated to a bin controller.

10. The method of claim 8 , wherein the deactivating comprises pulling the payment-enabled token out of a pool of available single-use tokens stored in the storage device and storing the payment-enabled token in a temporary pool of deactivated single-use tokens stored in the storage device.

11. The method of claim 10 , wherein the method further comprises returning the payment-enabled token to the pool of available single-use tokens in the storage device after expiration of a predetermined amount of time.

12. The method of claim 8 , wherein the deactivating comprises attaching a deactivation flag to the payment-enabled token in the storage device which distinguishes the payment-enabled token from other single-use tokens that are not deactivated within the storage device.

13. The method of claim 8 , wherein the method further comprises generating and executing a time-to-live job which comprises a pointer to the payment-enabled token stored in the storage device, detecting expiration of a predefined period of time based on the execution of the time-to-live job, and in response to the detection, returning the payment-enabled token to a pool of available payment-enabled tokens.

14. The method of claim 8 , wherein the method further comprises receiving a refund request for the payment transaction made via the payment-enabled token, and in response, verifying the payment-enabled token corresponds to the payment account based on the changed mapping of the payment-enabled token in the storage device.

15. A non-transitory computer-readable medium comprising instructions which when executed by a processor cause a computer to perform a method comprising:

distributing a payment-enabled token to a hardware element on a user device which includes a payment application installed therein, and storing a mapping of the payment-enabled token to a payment account held in the payment application via a storage device of a tokenization service;

detecting an initial use of the payment-enabled token as a form of payment by the payment application via a submission of the payment-enabled token by the payment application to an electronic payment network coupled to the tokenization service;

in response to the detecting of the initial use, deactivating the payment-enabled token via the tokenization service, and changing the mapping in the storage device to indicate that the payment-enabled token is no longer mapped to the payment account, wherein the changing comprises changing the mapping in the storage device to map a payment account reference (PAR) value of the payment-enabled token which links back to the PAN to an identifier of the payment-enabled token within one or more of a table, a document, and a file in the storage device;

receiving a request to access the payment transaction made with the deactivated payment-enabled token, wherein the request comprises an identifier of the payment-enabled token; and

mapping the identifier of the payment-enabled token to the PAN based on the changed mapping in the storage device, and accessing content from the payment transaction based on the PAN.

16. The non-transitory computer-readable medium of claim 15 , wherein the deactivating comprises pulling the payment-enabled token out of a pool of available single-use tokens in the storage device and storing the payment-enabled token in a temporary pool of deactivated single-use tokens in the storage device.

17. The non-transitory computer-readable medium of claim 15 , wherein the deactivating comprises attaching a deactivation flag to the payment-enabled token in the storage device which distinguishes the payment-enabled token from other single-use tokens that are not deactivated by the tokenization service.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 30, 2021
From: BRAUNDMEIER, AARON; HAKE, ANTHONY
To: MASTERCARD INTERNATIONAL INCORPORATED
Reel/Frame 058505/0552 →
Continuity (1)
Related Publication 20230214829A1 · Jul 6, 2023