IP Library Granted Patent US 12,632,845
Granted Patent B2
US 12,632,845 · App. 18/645,622 · Granted May 19, 2026

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,632,845
App. No.
18/645,622
Granted
May 19, 2026
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 (59)

1 . A computer-implemented method for managing an authorization request, comprising:

receiving, by a transaction management controller and a business management engine, data associated with a transaction initiated by a point-of-interaction device of a merchant-specific environment;

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

incorporating, by the transaction management controller, the card data received by the card reader and the data received by the business management engine into the authorization request;

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

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

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

2 . The computer-implemented method of claim 1 , further comprising:

receiving, by the transaction management controller and from the business management engine, scrolling receipt data for the transaction, wherein the scrolling receipt data includes product scan data and corresponding price data, or a combination thereof; and

managing, by the transaction management controller, display of the scrolling receipt data on the point-of-interaction device.

3 . The computer-implemented method of claim 1 , further comprising:

instructing, by the transaction management controller to the point-of-interaction device, to capture a signature data for the transaction;

receiving, by the transaction management controller and from the point-of-interaction device, the signature data; and

modifying, by the transaction management controller, the authorization response to include a byte array of the signature data.

4 . The computer-implemented method of claim 1 , wherein the business management engine and the transaction management controller are communicatively coupled to reduce complexities in configuring, coding, certifying, or initializing the business management engine.

5 . The computer-implemented method of claim 1 , wherein the business management engine generates a receipt of the transaction, via a communicatively coupled receipt printer, upon receiving the authorization response from the transaction management controller.

6 . The computer-implemented method of claim 1 , wherein the payment network includes a payment gateway that is communicatively coupled and configured to facilitate the transaction management controller in processing the transaction, and wherein the payment network is configured to communicate with an issuer processor based on the authorization request to generate the authorization response message.

7 . The computer-implemented method of claim 1 , further comprising:

determining, by the transaction management controller, the authorization request for the transaction is not received from the point-of-interaction device within a pre-determined time threshold.

8 . The computer-implemented method of claim 1 , further comprising:

receiving, by the transaction management controller, a feature modification message from a configuration device, wherein the feature modification message includes one or more instructions to add or modify a local processing feature of the transaction management controller.

9 . The computer-implemented method of claim 8 , wherein modifying or adding the feature of the transaction management controller includes enabling or disabling the feature of the transaction management controller based, at least in part, on the one or more instructions of the feature modification message.

10 . The computer-implemented method of claim 1 , further comprising:

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

11 . A system for managing an authorization request, comprising:

one or more processors; and

a non-transitory computer readable medium storing instructions that, when executed by the one or more processors, cause the one or more processors to perform a method comprising:

receiving, by a transaction management controller and a business management engine, data associated with a transaction initiated by a point-of-interaction device of a merchant-specific environment;

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

incorporating, by the transaction management controller, the card data received by the card reader and the data received by the business management engine into the authorization request;

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

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

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

12 . The system of claim 11 , further comprising:

receiving, by the transaction management controller and from the business management engine, scrolling receipt data for the transaction, wherein the scrolling receipt data includes product scan data and corresponding price data, or a combination thereof; and

managing, by the transaction management controller, display of the scrolling receipt data on the point-of-interaction device.

13 . The system of claim 11 , further comprising:

instructing, by the transaction management controller to the point-of-interaction device, to capture a signature data for the transaction;

receiving, by the transaction management controller and from the point-of-interaction device, the signature data; and

modifying, by the transaction management controller, the authorization response to include a byte array of the signature data.

14 . The system of claim 11 , wherein the business management engine and the transaction management controller are communicatively coupled to reduce complexities in configuring, coding, certifying, or initializing the business management engine.

15 . The system of claim 11 , wherein the business management engine generates a receipt of the transaction, via a communicatively coupled receipt printer, upon receiving the authorization response from the transaction management controller.

16 . The system of claim 11 , wherein the payment network includes a payment gateway that is communicatively coupled and configured to facilitate the transaction management controller in processing the transaction, and wherein the payment network is configured to communicate with an issuer processor based on the authorization request to generate the authorization response message.

17 . The system of claim 11 , further comprising:

receiving, by the transaction management controller, a feature modification message from a configuration device, wherein the feature modification message includes one or more instructions to add or modify a local processing feature of the transaction management controller, wherein modifying or adding the feature of the transaction management controller includes enabling or disabling the feature of the transaction management controller based, at least in part, on the one or more instructions of the feature modification message.

18 . A non-transitory computer-readable medium storing instructions for managing an authorization request, the instructions, when executed by one or more processors, causing the one or more processors to perform operations comprising:

receiving, by a transaction management controller and a business management engine, data associated with a transaction initiated by a point-of-interaction device of a merchant-specific environment;

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

incorporating, by the transaction management controller, the card data received by the card reader and the data received by the business management engine into the authorization request;

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

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

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

19 . The non-transitory computer-readable medium of claim 18 , further comprising:

receiving, by the transaction management controller and from the business management engine, scrolling receipt data for the transaction, wherein the scrolling receipt data includes product scan data and corresponding price data, or a combination thereof; and

managing, by the transaction management controller, display of the scrolling receipt data on the point-of-interaction device.

20 . The non-transitory computer-readable medium of claim 18 , further comprising:

instructing, by the transaction management controller to the point-of-interaction device, to capture a signature data for the transaction;

receiving, by the transaction management controller and from the point-of-interaction device, the signature data; and

modifying, by the transaction management controller, the authorization response to include a byte array of the signature data.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 25, 2024
From: BERGEON, FRANCOIS B.; BRYANT, SCOT A.; CHRISTENSEN, COY A.
To: VANTIV, LLC
Reel/Frame 067223/0728 →
CHANGE OF NAME Recorded Apr 25, 2024
From: VANTIV, LLC
To: WORLDPAY, LLC
Reel/Frame 067224/0225 →
Continuity (4)
Continuation 18060132 · Nov 30, 2022
Continuation 16818604 · Mar 13, 2020
Continuation 14976384 · Dec 21, 2015
Related Publication 20240311787A1 · Sep 19, 2024
References Cited (16)
US 5992570A · Walter et al. · 1999 [cited by applicant]
US 10192216B2 · Hammad · 2019 [cited by applicant]
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 20140074637A1 · Hammad · 2014 [cited by applicant]
US 20150012388A1 · Kim et al. · 2015 [cited by applicant]
US 20150058145A1 · Luciani · 2015 [cited by examiner]
US 20150081462A1 · Ozvat · 2015 [cited by examiner]
US 20160063496A1 · Royyuru et al. · 2016 [cited by applicant]
US 20160125449A1 · Beatty et al. · 2016 [cited by applicant]
US 20160196557A1 · Davis et al. · 2016 [cited by applicant]
US 20160364723A1 · Reese et al. · 2016 [cited by applicant]
US 20200111074A1 · Chau · 2020 [cited by examiner]
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]
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]