IP Library Granted Patent US 12,205,095
Granted Patent B2
US 12,205,095 · App. 17/955,685 · Granted Jan 21, 2025

Cloud-based configurable transaction management controller and method thereof

Inventors: Francois B. Bergeon (Scottsdale, AZ); Scot A. Bryant (Chandler, AZ); Coy A. Christensen (Scottsdale, AZ)
Assignee: Worldpay, LLC
G06Q20/202G06Q20/204G06Q20/208G06Q20/3825G06Q20/401
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 12,205,095
App. No.
17/955,685
Granted
Jan 21, 2025
Kind
B2
Abstract

Technologies for remotely managing payment authorization request messaging for payment transactions include a transaction management controller of one environment and a point of interaction device of another environment. The transaction management controller receives a transaction amount for a payment transaction from a business management engine. The payment transaction is based on a purchase transaction initiated by a merchant computing device of the other environment. The transaction management controller also receives payment card data from the point of interaction device, which is communicatively isolated from the merchant computing device and the business management engine. The transaction management controller inserts the transaction amount and the payment card data into a payment authorization request message, which is transmitted to a payment network. A payment authorization response message is received from the payment network and transmitted by the transaction management controller to the business management engine. Other embodiments are described and claimed.

Claims (55)

1. A method for remotely managing payment authorization request messaging for payment transactions, the method comprising:

receiving, by a transaction management controller and from a business management engine, a transaction amount for a payment transaction, the payment transaction based on a purchase transaction initiated by a point-of-sale (POS) device of a merchant-specific environment, and the transaction amount for insertion by the transaction management controller into a payment authorization request message;

requesting, by the transaction management controller and from a card reader of the merchant-specific environment, payment card data for the payment authorization request message, wherein the business management engine and the POS device are communicatively isolated from the card reader;

receiving, by the transaction management controller and from the card reader, the requested payment card data for insertion by the transaction management controller into the payment authorization request message;

inserting, by the transaction management controller, the payment card data received from the card reader and the transaction amount received from the business management engine into the payment authorization request message;

transmitting, by the transaction management controller and to a payment network, the payment authorization request message;

receiving, by the transaction management controller and from the payment network, a payment authorization response message for the payment authorization request message; and

transmitting, by the transaction management controller and to the business management engine, the payment authorization response message.

2. The method of claim 1 , further comprising:

dynamically controlling remotely, during processing of the payment transaction, by a processor of the transaction management controller located remotely from the merchant-specific environment, an interactive functionality of the card reader of the merchant-specific environment to display one or more user interface elements for specifying payment transaction processing options additional to one or more original payment transaction processing options present on the card reader.

3. The method of claim 1 , wherein the authorization request message and the authorization response message comprise Hypertext Transfer Protocol messages.

4. The method of claim 1 , further comprising:

receiving, by the transaction management controller and from the business management engine, product scan data and corresponding price data for the purchase transaction; and

managing, by the transaction management controller, display of the product scan data and corresponding price data on the card reader.

5. The method of claim 1 , further comprising:

receiving, by the transaction management controller, a feature modification message from a configuration device.

6. The method of claim 5 , wherein the feature modification message comprises configuration data to at least one of modify or add a feature of the card reader.

7. The method of claim 6 , wherein to at least one of modify or add the feature of the card reader comprises to toggle on or toggle off the feature of the card reader based at least in part on the configuration data of the feature modification message, and wherein the feature corresponds to a driver configuration of the card reader.

8. A transaction management controller comprising:

a memory configured to store instructions; and

a processor configured to execute the instructions to perform operations comprising:

receiving, from a business management engine, a transaction amount for a payment transaction, the payment transaction based on a purchase transaction initiated by a point-of-sale (POS) device of a merchant-specific environment, and the transaction amount for insertion by the transaction management controller into a payment authorization request message;

requesting, from a card reader of the merchant-specific environment, payment card data for the payment authorization request message, wherein the business management engine and the POS device are communicatively isolated from the card reader;

receiving, from the card reader, the requested payment card data for insertion by the transaction management controller into the payment authorization request message;

inserting the payment card data received from the card reader and the transaction amount received from the business management engine into the payment authorization request message;

transmitting, to a payment network, the payment authorization request message;

receiving, from the payment network, a payment authorization response message for the payment authorization request message; and

transmitting, to the business management engine, the payment authorization response message.

9. The transaction management controller of claim 8 , wherein the operations further comprise:

dynamically controlling remotely, during processing of the payment transaction, by the processor of the transaction management controller located remotely from the merchant-specific environment, an interactive functionality of the card reader of the merchant-specific environment to display one or more user interface elements for specifying payment transaction processing options additional to one or more original payment transaction processing options present on the card reader.

10. The transaction management controller of claim 8 , wherein the authorization request message and the authorization response message comprise Hypertext Transfer Protocol messages.

11. The transaction management controller of claim 8 , wherein the operations further comprise:

receiving, from the business management engine, product scan data and corresponding price data for the purchase transaction; and

managing display of the product scan data and corresponding price data on the card reader.

12. The transaction management controller of claim 8 , wherein the operations further comprise:

receiving, by the transaction management controller, a feature modification message from a configuration device.

13. The transaction management controller of claim 12 , wherein the feature modification message comprises configuration data to at least one of modify or add a feature of the card reader.

14. The transaction management controller of claim 13 , wherein to at least one of modify or add the feature of the card reader comprises to toggle on or toggle off the feature of the card reader based at least in part on the configuration data of the feature modification message, and wherein the feature corresponds to a driver configuration of the card reader.

15. A non-transitory computer-readable medium storing instructions that, when executed by a processor of a transaction management controller, cause the transaction management controller to perform operations comprising:

receiving, from a business management engine, a transaction amount for a payment transaction, the payment transaction based on a purchase transaction initiated by a point-of-sale (POS) device of a merchant-specific environment, and the transaction amount for insertion by the transaction management controller into a payment authorization request message;

requesting, from a card reader of the merchant-specific environment, payment card data for the payment authorization request message, wherein the business management engine and the POS device are communicatively isolated from the card reader;

receiving, from the card reader, the requested payment card data for insertion by the transaction management controller into the payment authorization request message;

inserting the payment card data received from the card reader and the transaction amount received from the business management engine into the payment authorization request message;

transmitting, to a payment network, the payment authorization request message;

receiving, from the payment network, a payment authorization response message for the payment authorization request message; and

transmitting, to the business management engine, the payment authorization response message.

16. The non-transitory computer-readable medium of claim 15 , wherein the operations further comprise:

dynamically controlling remotely, during processing of the payment transaction, by a processor of the transaction management controller located remotely from the merchant-specific environment, an interactive functionality of the card reader of the merchant-specific environment to display one or more user interface elements for specifying payment transaction processing options additional to one or more original payment transaction processing options present on the card reader.

17. The non-transitory computer-readable medium of claim 15 , wherein the authorization request message and the authorization response message comprise Hypertext Transfer Protocol messages.

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

receiving, from the business management engine, product scan data and corresponding price data for the purchase transaction; and

managing display of the product scan data and corresponding price data on the card reader.

19. The non-transitory computer-readable medium of claim 15 , wherein the operations further comprise:

receiving, by the transaction management controller, a feature modification message from a configuration device.

20. The non-transitory computer-readable medium of claim 19 , wherein the feature modification message comprises configuration data to at least one of modify or add a feature of the card reader, wherein to at least one of modify or add the feature of the card reader comprises to toggle on or toggle off the feature of the card reader based at least in part on the configuration data of the feature modification message, and wherein the feature corresponds to a driver configuration of the card reader.

Assignments (6)
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 Oct 5, 2022
From: BERGEON, FRANCOIS B; BRYANT, SCOT A; CHRISTENSEN, COY A
To: VANTIV, LLC
Reel/Frame 061321/0392 →
CHANGE OF NAME Recorded Oct 5, 2022
From: VANTIV, LLC
To: WORLDPAY, LLC
Reel/Frame 061612/0450 →
Continuity (2)
Continuation 14976384 · Dec 21, 2015
Related Publication 20230016290A1 · Jan 19, 2023
References Cited (9)
US 20040044575A1 · Bakker · 2004 [cited by examiner]
US 20090319382A1 · Shah et al. · 2009 [cited by applicant]
US 20130185152A1 · Aaron et al. · 2013 [cited by applicant]
US 20150081462A1 · Ozvat · 2015 [cited by examiner]
US 20160063496A1 · Royyuru et al. · 2016 [cited by applicant]
US 20160196557A1 · Davis et al. · 2016 [cited by applicant]
US 20200111074A1 · Chau · 2020 [cited by examiner]
Greenman, “Micros/Oracle EMV Chip Solution is Here!”, Dec. 2016, https://www.skurlas.com/oracle-news/micros/oracle-emv-chip-solution-is-here (Year: 2016). [cited by examiner]
Shoenecker, Gerry, “EMV Payments: Changes at the Point of Sale”, Feb. 2014, https://www.securetechalliance.org/secure/events/20140205/workshop/TUE_1015_04Schoenecker_SCA_EMV_Impacts_at_the_POS_02_2014.pdf (Year: 2014). [cited by examiner]