IP Library Granted Patent US 12,536,536
Granted Patent B2
US 12,536,536 · App. 17/643,922 · Granted Jan 27, 2026

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/4014G06Q20/10G06Q20/40H04L63/00H04L67/02
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,536,536
App. No.
17/643,922
Granted
Jan 27, 2026
Kind
B2
Abstract

Technologies for managing payment authorization request messaging for payment transactions include a transaction management controller for receiving a transaction amount for a payment transaction from a business management engine and payment card data for the payment transaction from a point of interaction device. 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 the business management engine. Other embodiments are described and claimed.

Claims (57)

1 . A computer-implemented method for managing payment authorization request messaging for payment transactions, the method comprising:

receiving, by a transaction management controller from a business management engine that is communicatively isolated from a point of interaction device, a transaction amount for insertion into a payment authorization request message to a payment network to be provided to a payment processing server of an issuer processor;

receiving, by the transaction management controller and from a remote configuration device that is configured to manage payment processing features of the transaction management controller, a first feature modification message for managing payment processing for payment transactions, wherein the point of interaction device is configured to receive, from the remote configuration device, a second feature modification message for managing payment processing for payment transactions;

requesting, by the transaction management controller according to the first feature modification message and from the point of interaction device according to the second feature modification message, (i) payment card data and one or more selected payment options for the payment authorization request message, the one or more selected payment options being selected from among a plurality of payment selection options displayed on the point of interaction device during the payment transaction based on instructions from the transaction management controller, wherein the point of interaction device initiates payment transactions, and (ii) modification of a set of local features for the point of interaction device that are remotely modifiable by the transaction management controller, as directed by the remote configuration device, wherein the set of local features for the point of interaction device includes one or more of a PIN entry feature, a transaction store and forward feature, a signature prompt feature, a customized display screen feature, or a scrolling receipt feature;

receiving, by the transaction management controller and from the point of interaction device, the requested payment card data, including the requested one or more selected payment options, for insertion into the payment authorization request message;

inserting, by the transaction management controller, the payment card data received from the point of interaction device and the transaction amount into the payment authorization request message;

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

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, the payment authorization response message for generation of a receipt.

2 . The method of claim 1 , further comprising:

managing, by the transaction management controller, selection options of the point of interaction device for the payment transaction; and

receiving, by the transaction management controller and from the point of interaction device, selected options for the payment transaction.

3 . The method of claim 1 , further comprising:

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

managing, by the transaction management controller, display of the product scan data and corresponding price data on the point of interaction device.

4 . The method of claim 1 , wherein the first feature modification message includes configuration data to modify the feature of the transaction management controller.

5 . The method of claim 4 , further comprising:

modifying the feature of the transaction management controller by toggling on or off the feature of the transaction management controller based at least in part on the configuration data of the first feature modification message.

6 . The method of claim 1 , wherein transmitting the payment authorization request message to a payment network comprises transmitting the payment authorization request message to a payment gateway communicatively coupled to the payment network; and

wherein receiving the payment authorization response message from the payment network comprises receiving the payment authorization response message from the payment gateway communicatively coupled to the payment network.

7 . One or more non-transitory machine-readable storage media comprising a plurality of instructions stored thereon that in response to being executed by a transaction management controller, cause the transaction management controller to:

receive, from a business management engine that is communicatively isolated from a point of interaction device, a transaction amount for insertion into a payment authorization request message to a payment network to be provided to a payment processing server of an issuer processor;

receive, by the transaction management controller and from a remote configuration device that is configured to manage payment processing features of the transaction management controller, a first feature modification message for managing payment processing for payment transactions, wherein the point of interaction device is configured to receive, from the remote configuration device, a second feature modification message for managing payment processing for payment transactions;

request, according to the first feature modification message and from the point of interaction device according to the second feature modification message, (i) payment card data and one or more selected payment options for the payment authorization request message, the one or more selected payment options being selected from among a plurality of payment selection options displayed on the point of interaction device during the payment transaction based on instructions from the transaction management controller, wherein the point of interaction device initiates payment transactions, and (ii) modification of a set of local features for the point of interaction device that are remotely modifiable by the transaction management controller, as directed by the remote configuration device, wherein the set of local features for the point of interaction device includes one or more of a PIN entry feature, a transaction store and forward feature, a signature prompt feature, a customized display screen feature, or a scrolling receipt feature;

receive, from the point of interaction device, the requested payment card data, including the requested one or more selected payment options, for insertion into the payment authorization request message;

insert the payment card data received from the point of interaction device and the transaction amount into the payment authorization request message;

transmit the payment authorization request message to a payment network;

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

transmit the payment authorization response message for generation of a receipt.

8 . The one or more non-transitory machine-readable storage media of claim 7 , wherein the plurality of instructions further cause the transaction management controller to:

manage selection options of the point of interaction device for the payment transaction; and

receive, from the point of interaction device, selected options for the payment transaction.

9 . The one or more non-transitory machine-readable storage media of claim 7 , wherein the plurality of instructions further cause the transaction management controller to:

receive product scan data and corresponding price data for a purchase transaction; and

manage display of the product scan data and corresponding price data on the point of interaction device.

10 . The one or more non-transitory machine-readable storage media of claim 7 , wherein the first feature modification message includes configuration data to modify the feature of the transaction management controller.

11 . The one or more non-transitory machine-readable storage media of claim 10 , wherein the plurality of instructions further cause the transaction management controller to modify the feature of the transaction management controller by toggling on or off the feature of the transaction management controller based at least in part on the configuration data of the first feature modification message.

12 . A system for managing payment authorization request messaging for payment transactions, the system comprising:

a transaction management controller comprising a processor executing instructions stored in memory, wherein the instructions cause the processor to:

receive, from a business management engine that is communicatively isolated from a point of interaction device, a transaction amount for insertion into a payment authorization request message to a payment network to be provided to a payment processing server of an issuer processor;

receive, by the transaction management controller and from a remote configuration device that is configured to manage payment processing features of the transaction management controller, a first feature modification message for managing payment processing for payment transactions, wherein the point of interaction device is configured to receive, from the remote configuration device, a second feature modification message for managing payment processing for payment transactions;

request, according to the first feature modification message and from the point of interaction device according to the second feature modification message, (i) payment card data and one or more selected payment options for the payment authorization request message, the one or more selected payment options being selected from among a plurality of payment selection options displayed on the point of interaction device during the payment transaction based on instructions from the transaction management controller, wherein the point of interaction device initiates payment transactions, and (ii) modification of a set of local features for the point of interaction device that are remotely modifiable by the transaction management controller, as directed by the remote configuration device, wherein the set of local features for the point of interaction device includes one or more of a PIN entry feature, a transaction store and forward feature, a signature prompt feature, a customized display screen feature, or a scrolling receipt feature;

receive, from the point of interaction device, the requested payment card data, including the requested one or more selected payment options, for insertion into the payment authorization request message;

insert the payment card data received from the point of interaction device and the transaction amount into the payment authorization request message;

transmit the payment authorization request message to a payment network;

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

transmit the payment authorization response message for generation of a receipt.

13 . The system of claim 12 , wherein the instructions of the transaction management controller further cause the processor to:

manage selection options of the point of interaction device for the payment transaction; and

receive, from the point of interaction device, selected options for the payment transaction.

14 . The system of claim 12 , wherein the instructions of the transaction management controller further cause the processor to:

receive product scan data and corresponding price data for a purchase transaction; and

manage display of the product scan data and corresponding price data on the point of interaction device.

15 . The system of claim 12 , wherein the first feature modification message includes configuration data to modify the feature of the transaction management controller.

16 . The system of claim 15 , wherein the instructions of the transaction management controller further cause the processor to modify the feature of the transaction management controller by toggling on or off the feature of the transaction management controller based at least in part on the configuration data of the first feature modification message.

17 . The system of claim 12 , wherein to transmit the payment authorization request message to a payment network comprises to transmit the payment authorization request message to a payment gateway communicatively coupled to the payment network; and

wherein to receive the payment authorization response message from the payment network comprises to receive the payment authorization response message from the payment gateway communicatively coupled to the payment network.

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 Dec 13, 2021
From: BERGEON, FRANCOIS B; BRYANT, SCOT A; CHRISTENSEN, COY A
To: VANTIV, LLC
Reel/Frame 058375/0286 →
CHANGE OF NAME Recorded Dec 13, 2021
From: VANTIV, LLC
To: WORLDPAY, LLC
Reel/Frame 058495/0760 →
Continuity (2)
Continuation 14755320 · Jun 30, 2015
Related Publication 20220101324A1 · Mar 31, 2022
References Cited (33)
US 5357563A · Hamilton et al. · 1994 [cited by applicant]
US 5870473A · Boesch et al. · 1999 [cited by applicant]
US 7219149B2 · Ofir et al. · 2007 [cited by applicant]
US 7552333B2 · Wheeler et al. · 2009 [cited by applicant]
US 7587196B2 · Hansen · 2009 [cited by applicant]
US 7904339B2 · Shah et al. · 2011 [cited by applicant]
US 8543461B2 · Mutha · 2013 [cited by applicant]
US 9305295B2 · Laracey · 2016 [cited by applicant]
US 9449320B1 · Walters et al. · 2016 [cited by applicant]
US 10261489B2 · Gandelsman · 2019 [cited by applicant]
US 10922675B2 · Savolainen · 2021 [cited by examiner]
US 20080189184A1 · Kubo · 2008 [cited by examiner]
US 20090319382A1 · Shah et al. · 2009 [cited by applicant]
US 20110055033A1 · Chen · 2011 [cited by examiner]
US 20110251892A1 · Laracey · 2011 [cited by applicant]
US 20120310756A1 · Agashe et al. · 2012 [cited by applicant]
US 20130132184A1 · Mutha · 2013 [cited by applicant]
US 20130166332A1 · Hammad · 2013 [cited by applicant]
US 20140019352A1 · Shrivastava · 2014 [cited by applicant]
US 20140129357A1 · Goodwin · 2014 [cited by applicant]
US 20140180924A1 · Ozvat · 2014 [cited by examiner]
US 20140207682A1 · Wolfond et al. · 2014 [cited by applicant]
US 20150012420A1 · Kim et al. · 2015 [cited by applicant]
US 20150081462A1 · Ozvat et al. · 2015 [cited by applicant]
US 20160034872A1 · Hendrick et al. · 2016 [cited by applicant]
US 20160034876A1 · Speiser et al. · 2016 [cited by applicant]
US 20160125449A1 · Beatty et al. · 2016 [cited by applicant]
US 20160277380A1 · Wagner et al. · 2016 [cited by applicant]
US 20160292660A1 · Yu et al. · 2016 [cited by applicant]
US 20170011375A1 · Takasu · 2017 [cited by examiner]
US 20200265399A1 · Sweitzer · 2020 [cited by examiner]
WO WO2015095738A1 · 2015 [cited by examiner]
Author Unknown, LivePOS Features, 2015, retrieved from LivePOS.com http://web.archive.org/web20150228112651/ http://www.livepos.com:80/links/features.aspx (Year: 2015). [cited by applicant]