IP Library Granted Patent US 11,657,395
Granted Patent B2
US 11,657,395 · App. 17/446,227 · Granted May 23, 2023

Dynamically 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/40
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 11,657,395
App. No.
17/446,227
Granted
May 23, 2023
Kind
B2
Abstract

Technologies for managing payment authorization request messaging for payment transactions include a transaction management controller. The transaction management controller receives a transaction amount for a payment transaction from a business management engine and a payment transaction type from a point of interaction device. The transaction management controller initializes a transaction processing module that corresponds to the received payment transaction type. The transaction processing module defines payment processing parameters for processing payment transactions of the payment transaction type. One or more of the payment processing parameters are modified based on configuration data received from a remote configuration device. The transaction management controller processes the payment transaction as a function of the payment processing parameters. Other embodiments are described and claimed.

Claims (64)

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

receiving, by a transaction management controller and from a point of interaction device, a payment vehicle type corresponding to a payment vehicle associated with a payment transaction;

initializing, by the transaction management controller, a payment vehicle type-specific transaction processing module that corresponds to the received payment vehicle type, wherein the payment vehicle type-specific transaction processing module defines transaction processing parameters for processing payment transactions based on the received payment vehicle type by prescribing at least one of supported language settings, transaction gratuity features, transaction store and forward features, lane identification features, and lane initialization settings;

receiving, by the transaction management controller, a parameter modification message from a remote configuration device, the parameter modification message comprising configuration data to modify one or more of the transaction processing parameters defined by the initialized payment vehicle type-specific transaction processing module; and

processing, by the transaction management controller, the payment transaction as a function of the transaction processing parameters of the initialized payment vehicle type-specific transaction processing module.

2. The method of claim 1 , wherein processing the payment transaction comprises:

transmitting, by the transaction management controller and to a payment network, a payment authorization request message based on the transaction processing parameters of the initialized payment vehicle type-specific transaction processing module;

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 a business management engine, the payment authorization response message based on the transaction processing parameters of the initialized payment vehicle type-specific transaction processing module.

3. The method of claim 1 , further comprising retrieving, by the transaction management controller, the payment vehicle type-specific transaction processing module that corresponds to the received payment vehicle type, wherein the retrieved payment vehicle type-specific transaction processing module is one of a plurality of payment vehicle type-specific transaction processing modules retrievable by the transaction management controller.

4. The method of claim 3 , wherein retrieving the payment vehicle type-specific transaction processing module comprises retrieving the payment vehicle type-specific transaction processing module from one of a local storage device of the transaction management controller or a remote storage device.

5. The method of claim 1 , wherein the received payment vehicle type comprises one of a first payment vehicle type and a second payment vehicle type, and wherein the payment vehicle type-specific transaction processing module comprises one of a first payment vehicle type-specific transaction processing module that corresponds to the first payment vehicle type and a second payment vehicle type-specific transaction processing module that corresponds to the second payment vehicle type; and further comprising:

determining, by the transaction management controller, whether the received payment vehicle type is the first payment vehicle type or the second vehicle type;

wherein initializing the payment vehicle type-specific transaction processing module that corresponds to the received payment vehicle type comprises (i) initializing only the first payment vehicle type-specific transaction processing module based on a determination that the received payment vehicle type is the first payment vehicle type and (ii) initializing only the second payment vehicle type-specific transaction processing module based on a determination that the received payment vehicle type is the second payment vehicle type.

6. 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.

7. The method of claim 1 , wherein the configuration data to modify the one or more transaction processing parameters comprises configuration data to toggle on or toggle off the one or more transaction processing parameters of the initialized payment vehicle type-specific transaction processing module.

8. 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, a transaction amount for a payment transaction, the transaction amount for insertion by the transaction management controller into a payment authorization request message;

request, from a point of interaction device, a payment vehicle type corresponding to a payment vehicle associated with the payment transaction, wherein the point of interaction device is communicatively isolated from the business management engine;

receive, from the point of interaction device, the payment vehicle type;

initialize a payment vehicle type-specific transaction processing module that corresponds to the received payment vehicle type, wherein the payment vehicle type-specific transaction processing module defines transaction processing parameters for processing payment transactions based on the received payment vehicle type by prescribing at least one of supported language settings, transaction gratuity features, transaction store and forward features, lane identification features, and lane initialization settings;

receive a parameter modification message from a remote configuration device, the parameter modification message comprising configuration data to modify one or more of the transaction processing parameters defined by the initialized payment vehicle type-specific transaction processing module; and

process the payment transaction as a function of the transaction processing parameters of the initialized payment vehicle type-specific transaction processing module.

9. The one or more non-transitory machine-readable storage media of claim 8 , wherein to process the payment transaction comprises to:

request, from the point of interaction device, payment vehicle data for the payment authorization request message based on the transaction processing parameters of the initialized payment vehicle type-specific transaction processing module;

receive, from the point of interaction device, the requested payment vehicle data for insertion by the transaction management controller into the payment authorization request message;

insert the payment vehicle data received from the point of interaction device and the transaction amount received from the business management engine into the payment authorization request message;

transmit, to a payment network, the payment authorization request message based on the transaction processing parameters of the initialized payment vehicle type-specific transaction processing module;

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

transmit, to the business management engine, the payment authorization response message based on the transaction processing parameters of the initialized payment vehicle type-specific transaction processing module.

10. The one or more non-transitory machine-readable storage media of claim 8 , wherein the plurality of instructions further cause the transaction management controller to retrieve the payment vehicle type-specific transaction processing module that corresponds to the received payment vehicle type, wherein the retrieved payment vehicle type-specific transaction processing module is one of a plurality of payment vehicle type-specific transaction processing modules retrievable by the transaction management controller.

11. The one or more non-transitory machine-readable storage media of claim 10 , wherein to retrieve the payment vehicle type-specific transaction processing module comprises to retrieve the payment vehicle type-specific transaction processing module from one of a local storage device of the transaction management controller or a remote storage device.

12. The one or more non-transitory machine-readable storage media of claim 8 , wherein the received payment vehicle type comprises one of a first payment vehicle type and a second payment vehicle type, and wherein the payment vehicle type-specific transaction processing module comprises one of a first payment vehicle type-specific transaction processing module that corresponds to the first payment vehicle type and a second payment vehicle type-specific transaction processing module that corresponds to the second payment vehicle type;

wherein the plurality of instructions further cause the transaction management controller to determine whether the received payment vehicle type is the first payment vehicle type or the second payment vehicle type; and

wherein to initialize the payment vehicle type-specific transaction processing module that corresponds to the received payment vehicle type comprises to (i) initialize only the first payment vehicle type-specific transaction processing module based on a determination that the received payment vehicle type is the first payment vehicle type and (ii) initialize only the second payment vehicle type-specific transaction processing module based on a determination that the received payment vehicle type is the second payment vehicle type.

13. The one or more non-transitory machine-readable storage media of claim 8 , 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.

14. The one or more non-transitory machine-readable storage media of claim 8 , wherein the configuration data to modify the one or more transaction processing parameters comprises configuration data to toggle on or toggle off the one or more transaction processing parameters of the initialized payment vehicle type-specific transaction processing module.

15. 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, a transaction amount for a payment transaction, the transaction amount for insertion by the transaction management controller into a payment authorization request message;

request, from a point of interaction device, a payment vehicle type corresponding to a payment vehicle associated with the payment transaction, wherein the point of interaction device is communicatively isolated from the business management engine;

receive, from the point of interaction device, the payment vehicle type;

initialize a payment vehicle type-specific transaction processing module that corresponds to the received payment vehicle type, wherein the payment vehicle type-specific transaction processing module defines transaction processing parameters for processing payment transactions based on the received payment vehicle type by prescribing at least one of supported language settings, transaction gratuity features, transaction store and forward features, lane identification features, and lane initialization settings;

receive a parameter modification message from a remote configuration device, the parameter modification message comprising configuration data to modify one or more of the transaction processing parameters defined by the initialized payment vehicle type-specific transaction processing module; and

process the payment transaction as a function of the transaction processing parameters of the initialized payment vehicle type-specific transaction processing module.

16. The system of claim 15 , wherein to process the payment transaction comprises to:

request, from the point of interaction device, payment vehicle data for the payment authorization request message based on the transaction processing parameters of the initialized payment vehicle type-specific transaction processing module;

receive, from the point of interaction device, the requested payment vehicle data for insertion by the transaction management controller into the payment authorization request message;

insert the payment vehicle data received from the point of interaction device and the transaction amount received from the business management engine into the payment authorization request message;

transmit, to a payment network, the payment authorization request message based on the transaction processing parameters of the initialized payment vehicle type-specific transaction processing module;

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

transmit, to the business management engine, the payment authorization response message based on the transaction processing parameters of the initialized payment vehicle type-specific transaction processing module.

17. The system of claim 15 , wherein the instructions of the transaction management controller further cause the processor to retrieve the payment vehicle type-specific transaction processing module that corresponds to the received payment vehicle type, wherein the retrieved payment vehicle type-specific transaction processing module is one of a plurality of payment vehicle type-specific transaction processing modules retrievable by the transaction management controller.

18. The system of claim 15 , wherein the received payment vehicle type comprises one of a first payment vehicle type and a second payment vehicle type, and wherein the payment vehicle type-specific transaction processing module comprises one of a first payment vehicle type-specific transaction processing module that corresponds to the first payment vehicle type and a second payment vehicle type-specific transaction processing module that corresponds to the second payment vehicle type;

wherein the instructions of the transaction management controller further cause the processor to determine whether the received payment vehicle type is the first payment vehicle type or the second payment vehicle type; and

wherein to initialize the payment vehicle type-specific transaction processing module that corresponds to the received payment vehicle type comprises to (i) initialize only the first payment vehicle type-specific transaction processing module based on a determination that the received payment vehicle type is the first payment vehicle type and (ii) initialize only the second payment vehicle type-specific transaction processing module based on a determination that the received payment vehicle type is the second payment vehicle type.

19. The system of claim 15 , 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.

20. The system of claim 15 , wherein the configuration data to modify the one or more transaction processing parameters comprises configuration data to toggle on or toggle off the one or more transaction processing parameters of the initialized payment vehicle type-specific transaction processing module.

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 Aug 27, 2021
From: BERGEON, FRANCOIS B.; BRYANT, SCOT A.; CHRISTENSEN, COY A.
To: VANTIV, LLC
Reel/Frame 057311/0378 →
CHANGE OF NAME Recorded Aug 27, 2021
From: VANTIV, LLC
To: WORLDPAY, LLC
Reel/Frame 057367/0739 →
Continuity (2)
Continuation 14990938 · Jan 8, 2016
Related Publication 20210390538A1 · Dec 16, 2021