IP Library Granted Patent US 10,445,720
Granted Patent B2
US 10,445,720 · App. 14/046,912 · Granted Oct 15, 2019

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); Nicholas G. Nayfack (Durango, CO); 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,445,720
App. No.
14/046,912
Granted
Oct 15, 2019
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 (70)

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, a transaction total, and a merchant ID from a point of sale terminal of a merchant, 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;

the unique code encodes a tokenized primary account number, an account issuer payment token, and an expiration date of the account issuer payment token; 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 and being scanned by the point of sale terminal of the merchant:

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

receiving, by the server of the payment management system connected to the electronic network, 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;

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

receiving, by the server of the payment management system connected to the electronic network, a response from the payment system; and

completing, by the server of the payment management system, the transaction based on the response.

2. The method of claim 1 , wherein the response from the payment system indicates that the primary account number may be encrypted and stored for later retrieval further comprising the steps of:

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

generating, by the server of the payment management system, a transaction token for the transaction, wherein the transaction token includes the primary account number, an expiration date of the transaction token, and a group ID; and

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

3. The method of claim 2 , wherein the transaction token is encrypted.

4. The method of claim 2 , wherein the group ID enables only particular merchants to redeem the transaction token.

5. The method of claim 4 , further comprising associating, by the server of the payment management system, a plurality of merchants to the group ID.

6. The method of claim 2 , 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 to the merchant ID in the merchant logs;

providing, by the server of the payment management system, the primary account number to the 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 point of sale terminal of the merchant.

7. The method of claim 1 , further comprising:

determining, by the server of the payment management system, by farming transaction logs, a consumer type and consumer patterns of the user of the mobile device;

receiving, by the server of the payment management system, location information and device information from the payment application installed in the mobile device of the user;

generating, by the server of the payment management system, predictions of purchasing behavior for the user of the mobile device based on the location information, the consumer type and the consumer patterns;

generating, by the server of the payment management system, value added services for the the user of the mobile device based on the predictions of purchasing behavior; and

transmitting, by the server of the payment management system, the value added services to the payment application installed in the mobile device of the user.

8. The method of claim 7 , wherein transmitting the value added services to the payment application installed in the mobile device of the user includes routing, by the server of the payment management system, the value added services to the processing device of the account issuer.

9. The method of claim 7 , wherein the consumer type is generated by clustering algorithms and the consumer patterns are generated by pattern recognition algorithms.

10. The method of claim 1 , further comprising transmitting, by the server of the payment management system, the response from the payment system to the point of sale terminal of the merchant and to the processing device of the account issuer.

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

a server of a payment management system connected to an electronic network and configured to:

receive a unique code, a transaction total, and a merchant ID from a point of sale terminal of a merchant, 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:

the unique code encodes a tokenized primary account number, an account issuer payment token, and an expiration date of the account issuer payment token; 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 and being scanned by the point of sale terminal of the merchant;

transmit the unique code to a processing device of an account issuer, wherein the unique code is received and authenticated by the processing device of the account issuer;

receive 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,

transmit the primary account number, the transaction total, and the merchant ID to a payment system;

receive a response from the payment system; and

complete the transaction based on the response.

12. The system of claim 11 , wherein the response from the payment system indicates that the primary account number may be encrypted and stored for later retrieval, and wherein the server of the payment management system is further configured to:

validate the merchant ID against merchant logs, wherein the validating ensures the merchant is configured for tokenization;

generate a transaction token for the transaction, wherein the transaction token includes the primary account number an expiration date of the transaction token, and a group ID; and

transmit the response and the transaction token to the point of sale terminal of the merchant.

13. The system of claim 12 , wherein the transaction token is encrypted.

14. The system of claim 12 , wherein the group ID enables only particular merchants to redeem the transaction token.

15. The system of claim 14 , wherein the server of the payment management system is further configured to associate a plurality of merchants to the group ID.

16. The system of claim 12 , wherein the server of the payment management system is further configured to:

receive the transaction token from at least one point of sale terminal of the merchant;

validate the merchant ID against the merchant logs, wherein the validating ensures the merchant is configured for tokenization;

decrypt the transaction token;

compare the group ID with the merchant ID in the merchant logs;

provide the primary account number to the payment system;

receive a second response from the payment system; and

transmit the second response to the point of sale terminal of the merchant.

17. The system of claim 11 , wherein the server of the payment management system is further configured to:

determine, by farming transaction logs, a consumer type and consumer patterns of the user of the mobile device;

receive location information and device information from the payment application installed in the mobile device of the user;

generate predictions of purchasing behavior for the user of the mobile device based on the location information, the consumer type and the consumer patterns;

generate value added services for the user of the mobile device based on the predictions of purchasing behavior; and

transmit the value added services to the payment application installed in the mobile device of the user.

18. The system of claim 17 , wherein transmitting the value added services to the payment application installed in the mobile device of the user includes routing, by the server of the payment management system, the value added services to the processing device of the account issuer.

19. The system of claim 17 , wherein the consumer type is generated by clustering algorithms and the consumer patterns are generated by pattern recognition algorithms.

20. The system of claim 11 , wherein the server of the payment management system is further configured to:

transmit the response from the payment system to the point of sale terminal of the merchant and to the processing device of the account issuer.

Assignments (10)
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 →
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 →
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 →
RELEASE OF SECURITY INTEREST IN PATENTS (RELEASES RF 33431/0198) Recorded Aug 1, 2019
From: MORGAN STANLEY SENIOR FUNDING, INC., AS SUCCESSOR-IN-INTEREST TO JPMORGAN CHASE BANK, N.A.
To: MERCURY PAYMENT SYSTEMS, LLC
Reel/Frame 049942/0453 →
CHANGE OF NAME Recorded Aug 6, 2018
From: VANTIV, LLC
To: WORLDPAY, LLC
Reel/Frame 046723/0234 →
NOTICE OF ASSIGNMENT OF SECURITY INTEREST IN PATENT COLLATERAL Recorded Oct 11, 2017
From: JPMORGAN CHASE BANK, N.A., AS RESIGNING AGENT
To: MORGAN STANLEY SENIOR FUNDING, INC., AS SUCCESSOR AGENT
Reel/Frame 044171/0602 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 14, 2017
From: MERCURY PAYMENT SYSTEMS, LLC
To: VANTIV, LLC
Reel/Frame 043007/0199 →
SECURITY INTEREST Recorded Jul 29, 2014
From: MERCURY PAYMENT SYSTEMS, LLC
To: JPMORGAN CHASE BANK, N.A., AS AGENT
Reel/Frame 033431/0198 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 7, 2014
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 031936/0027 →
Continuity (2)
Continuation In Part 13563534 · Jul 31, 2012
Related Publication 20140108261A1 · Apr 17, 2014