IP Library Granted Patent US 10,706,407
Granted Patent B2
US 10,706,407 · App. 16/557,092 · Granted Jul 7, 2020

Systems and methods for payment management for supporting mobile payments

Inventors: Travis Lee Priest (Durango, CO); Daniel J. Ourada (Bend, OR); Matthew D. Ozvat (Durango, CO); Daniel J. Murphy (Castle Pines, CO); Nicholas G. Nayfack (Hal Moon Bay, CA); Charles E. Watts (Durango, CO)
Assignee: Worldpay, LLC
G06Q20/3226G06Q20/202G06Q20/3274G06Q20/385G06Q20/401G06Q30/0201
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 10,706,407
App. No.
16/557,092
Granted
Jul 7, 2020
Kind
B2
Abstract

Systems and methods for managing mobile payments is provided. An account issuer provides an application that is loaded onto a mobile device, which enables a consumer to pay for transactions. The mobile payment application generates a unique code. The code is read by the point of sale terminal, which is then provided to the payment management system. The payment management system contracts the account issuer and authenticates the code, thereby receiving a primary account number. Account number and transaction information is used to authorize the transaction via payment systems. The payment system accepts or declines the transaction in a response. Tokens may be generated for the account number, and value added services may be generated based upon user behaviors.

Claims (75)

1. A method for payment management of mobile payments, the method comprising:

receiving, by a server of a payment management system connected to an electronic network, a unique code and a merchant ID from a point of sale terminal of a merchant, the unique code encoding a tokenized primary account number and an account issuer payment token, wherein:

the unique code has been generated by a payment application installed in a mobile device of a user, the payment application enabling the user of the mobile device to pay for a transaction; and

the unique code is received from the point of sale terminal of the merchant upon the unique code being presented, by the mobile device of the user, to the point of sale terminal of the merchant;

transmitting, by the server of the payment management system, the unique code to a processing device of an account issuer, wherein the unique code is authenticated by the processing device of the account issuer;

receiving, by the server of the payment management system, a primary account number from the processing device of the account issuer, wherein the primary account number has been retrieved from an account database upon successful authentication of the unique code by the processing device of the account issuer;

validating, by the server of the payment management system, the merchant ID against merchant logs;

upon successful validation of the merchant ID, generating, by the server of the payment management system, a transaction token based on the primary account number;

transmitting, by the server of the payment management system, the transaction token to the point of sale terminal of the merchant; and

completing, by the server of the payment management system, a transaction based at least in part on the transaction token that has been received from the point of sale terminal of the merchant.

2. The method of claim 1 , wherein the validating ensures the merchant is configured for tokenization.

3. The method of claim 1 , further comprising:

receiving, by the server of the payment management system, a transaction total from the point of sale terminal of the merchant;

transmitting, by the server of the payment management system, the primary account number, the transaction total, and the merchant ID to a payment system;

receiving, by the server of the payment management system, a response from the payment system; and

transmitting, by the server of the payment management system, the response to the point of sale terminal of the merchant.

4. The method of claim 3 , wherein the response is transmitted to the point of sale terminal of the merchant with the transaction token.

5. The method of claim 1 , wherein the transaction token includes the primary account number, an expiration date of the transaction token, and a group ID, wherein the group ID is associated with a plurality of merchants.

6. The method of claim 5 , further comprising:

receiving, by the server of the payment management system, the transaction token from at least one point of sale terminal of the merchant;

validating, by the server of the payment management system, the merchant ID against the merchant logs, wherein the validating ensures the merchant is configured for tokenization;

decrypting, by the server of the payment management system, the transaction token;

comparing, by the server of the payment management system, the group ID with the merchant ID in the merchant logs;

providing, by the server of the payment management system, the primary account number to a payment system;

receiving, by the server of the payment management system, a second response from the payment system; and

transmitting, by the server of the payment management system, the second response to the at least one point of sale terminal of the merchant.

7. The method of claim 1 , wherein the transaction token is one of: a single use token and a recurring token.

8. The method of claim 1 , wherein the transaction token is generated in response to receiving, by the server of the payment management system, a token request from the point of sale terminal of the merchant.

9. A system for payment management of mobile payments, the system comprising:

one or more processors;

a data storage storing instructions which, when executed by the one or more processors, cause the one or more processors to perform steps comprising:

receiving, by a server of a payment management system connected to an electronic network, a unique code and a merchant ID from a point of sale terminal of a merchant, the unique code encoding a tokenized primary account number and an account issuer payment token, wherein:

the unique code has been generated by a payment application installed in a mobile device of a user, the payment application enabling the user of the mobile device to pay for a transaction; and

the unique code is received from the point of sale terminal of the merchant upon the unique code being presented, by the mobile device of the user, to the point of sale terminal of the merchant;

transmitting, by the server of the payment management system, the unique code to a processing device of an account issuer, wherein the unique code is authenticated by the processing device of the account issuer;

receiving, by the server of the payment management system, a primary account number from the processing device of the account issuer, wherein the primary account number has been retrieved from an account database upon successful authentication of the unique code by the processing device of the account issuer;

validating, by the server of the payment management system, the merchant ID against merchant logs;

upon successful validation of the merchant ID, generating, by the server of the payment management system, a transaction token based on the primary account number;

transmitting, by the server of the payment management system, the transaction token to the point of sale terminal of the merchant; and

completing, by the server of the payment management system, a transaction based at least in part on the transaction token that has been received from the point of sale terminal of the merchant.

10. The system of claim 9 , wherein the validating ensures the merchant is configured for tokenization.

11. The system of claim 9 , wherein the steps further comprise:

receiving, by the server of the payment management system, a transaction total from the point of sale terminal of the merchant;

transmitting, by the server of the payment management system, the primary account number, the transaction total, and the merchant ID to a payment system;

receiving, by the server of the payment management system, a response from the payment system; and

transmitting, by the server of the payment management system, the response to the point of sale terminal of the merchant.

12. The system of claim 11 , wherein the response is transmitted to the point of sale terminal of the merchant with the transaction token.

13. The system of claim 9 , wherein the transaction token includes the primary account number, an expiration date of the transaction token, and a group ID, wherein the group ID is associated with a plurality of merchants.

14. The system of claim 13 , wherein the steps further comprise:

receiving, by the server of the payment management system, the transaction token from at least one point of sale terminal of the merchant;

validating, by the server of the payment management system, the merchant ID against the merchant logs, wherein the validating ensures the merchant is configured for tokenization;

decrypting, by the server of the payment management system, the transaction token;

comparing, by the server of the payment management system, the group ID with the merchant ID in the merchant logs;

providing, by the server of the payment management system, the primary account number to a payment system;

receiving, by the server of the payment management system, a second response from the payment system; and

transmitting, by the server of the payment management system, the second response to the at least one point of sale terminal of the merchant.

15. The system of claim 9 , wherein the transaction token is one of: a single use token and a recurring token.

16. The system of claim 9 , wherein the transaction token is generated in response to receiving, by the server of the payment management system, a token request from the point of sale terminal of the merchant.

17. A non-transitory computer readable medium for payment management of mobile payments, the non-transitory computer readable medium storing instructions which, when executed by one or more processors, cause the one or more processors to perform steps comprising:

receiving, by a server of a payment management system connected to an electronic network, a unique code and a merchant ID from a point of sale terminal of a merchant, the unique code encoding a tokenized primary account number and an account issuer payment token, wherein:

the unique code has been generated by a payment application installed in a mobile device of a user, the payment application enabling the user of the mobile device to pay for a transaction; and

the unique code is received from the point of sale terminal of the merchant upon the unique code being presented, by the mobile device of the user, to the point of sale terminal of the merchant;

transmitting, by the server of the payment management system, the unique code to a processing device of an account issuer, wherein the unique code is authenticated by the processing device of the account issuer;

receiving, by the server of the payment management system, a primary account number from the processing device of the account issuer, wherein the primary account number has been retrieved from an account database upon successful authentication of the unique code by the processing device of the account issuer;

validating, by the server of the payment management system, the merchant ID against merchant logs;

upon successful validation of the merchant ID, generating, by the server of the payment management system, a transaction token based on the primary account number;

transmitting, by the server of the payment management system, the transaction token to the point of sale terminal of the merchant; and

completing, by the server of the payment management system, a transaction based at least in part on the transaction token that has been received from the point of sale terminal of the merchant.

18. The non-transitory computer readable medium of claim 17 , wherein the steps further comprise:

receiving, by the server of the payment management system, a transaction total from the point of sale terminal of the merchant;

transmitting, by the server of the payment management system, the primary account number, the transaction total, and the merchant ID to a payment system;

receiving, by the server of the payment management system, a response from the payment system; and

transmitting, by the server of the payment management system, the response to the point of sale terminal of the merchant.

19. The non-transitory computer readable medium of claim 18 , wherein the response is transmitted to the point of sale terminal of the merchant with the transaction token.

20. The non-transitory computer readable medium of claim 17 , wherein the transaction token is generated in response to receiving, by the server of the payment management system, a token request from the point of sale terminal of the merchant.

Assignments (7)
RELEASE OF SECURITY INTERESTS RECORDED AT REEL/FRAMES 066626/0655, 066625/0426, 066625/0347, AND 066625/0276 Recorded Jan 12, 2026
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: WORLDPAY, LLC; WORLDPAY ISO AND ECOMMERCE, LLC; PAYMETRIC, LLC; WORLDPAY US, LLC
Reel/Frame 074314/0622 →
RELEASE OF SECURITY INTEREST IN INTELLECTUAL PROPERTY RECORDED AT R/F 066624/0719 Recorded Jan 12, 2026
From: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
To: WORLDPAY, LLC
Reel/Frame 074315/0412 →
SECURITY INTEREST Recorded Feb 19, 2024
From: WORLDPAY, LLC
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 066624/0719 →
SECURITY INTEREST Recorded Feb 19, 2024
From: WORLDPAY, LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
Reel/Frame 066626/0655 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 3, 2019
From: PRIEST, TRAVIS LEE; OURADA, DANIEL J.; OZVAT, MATTHEW D.; MURPHY, DANIEL J.; NAYFACK, NICHOLAS G.; WATTS, CHARLES E.
To: MERCURY PAYMENT SYSTEMS, LLC
Reel/Frame 050255/0648 →
CHANGE OF NAME Recorded Sep 3, 2019
From: VANTIV, LLC
To: WORLDPAY, LLC
Reel/Frame 050255/0667 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 3, 2019
From: MERCURY PAYMENT SYSTEMS, LLC
To: VANTIV, LLC
Reel/Frame 050249/0616 →
Continuity (3)
Continuation 14046912 · Oct 4, 2013
Continuation In Part 13563534 · Jul 31, 2012
Related Publication 20190385146A1 · Dec 19, 2019