IP Library Granted Patent US 11,682,010
Granted Patent B2
US 11,682,010 · App. 17/337,701 · Granted Jun 20, 2023

Systems and methods for executing real-time reconciliation and notification of electronic transactions

Inventors: William J. Wied (Austin, TX); Aman S. Cheema (Warwickshire, GB); Manuela Dragan (Westfield, NJ); Stephen E. Dinan (Austin, TX)
Assignee: Fidelity Information Services, LLC
G06Q20/389G06F16/2308G06F16/2452G06Q20/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 11,682,010
App. No.
17/337,701
Granted
Jun 20, 2023
Kind
B2
Abstract

Systems and methods of executing a real-time electronic transaction by a real-time transaction system are disclosed. One the method includes receiving, by a reconciliation system, a transaction update associated with a transaction request from a transaction network. The reconciliation system may authenticate the transaction update by communicating with an authentication system. The reconciliation system may translate the transaction update into at least another format. The reconciliation system may transmit the transaction update to a notification handler. The reconciliation system may receive transaction data associated with the transaction update from a transaction query system. The reconciliation system may transmit the transaction update to a transaction requestor associated with the transaction data.

Claims (56)

1. A method of executing a real-time electronic transaction by a real-time transaction system, the method comprising:

receiving, by a reconciliation system, a transaction update associated with a transaction request from a transaction network;

authenticating, by the reconciliation system, the transaction update by communicating with an authentication system;

translating, by the reconciliation system, the transaction update into at least another format that is suitable for normalization;

encrypting, by the reconciliation system, data elements of the transaction request, wherein an encryption key for the encrypted data elements is deleted from an encryption key cache upon exceeding a pre-determined time threshold and is replaced with a newly generated encryption key;

transmitting, by the reconciliation system, the transaction update to a notification handler;

receiving, by the reconciliation system, transaction data associated with the transaction update from a transaction query system; and

transmitting, by the reconciliation system, the transaction update to a transaction requestor associated with the transaction data.

2. The method of claim 1 , further comprising:

determining an optimal path for executing the transaction request based, at least in part, on temporal data, transaction data, user preference information, or a combination thereof; and

routing, by the reconciliation system, via the optimal path the transaction update to a matching transaction network notification system for translating the transaction update into a generic non-scheme specific format.

3. The method of claim 1 , wherein the transaction update is received, by the reconciliation system, via at least one of an Application Programing Interface (API) call or a Secure File Transfer Protocol (SFTP) message.

4. The method of claim 1 , further comprising:

transmitting, by the reconciliation system, the transaction update to an account ledger system, an auditing system, and/or a transaction system via one or more transaction event-topic streams.

5. The method of claim 1 , wherein the transaction update is transmitted to the transaction requestor via at least one of an Application Programing Interface (API) post or a Secure File Transfer Protocol (SFTP) message.

6. The method of claim 1 , further comprising:

generating, by the real-time transaction system, one or more interfaces including information associated with one or more statuses of the transaction request based on the transaction update.

7. The method of claim 1 , wherein the transaction update associated with the transaction request is received in real-time when the transaction network generates one or more updates associated with the transaction request.

8. A real-time transaction system comprising:

one or more computer readable media storing instructions for executing a real-time electronic transaction; and

one or more processors configured to execute the instructions to perform operations comprising:

receiving, by a reconciliation system, a transaction update associated with a transaction request from a transaction network;

authenticating, by the reconciliation system, the transaction update by communicating with an authentication system;

translating, by the reconciliation system, the transaction update into at least another format that is suitable for normalization;

encrypting, by the reconciliation system, data elements of the transaction request, wherein an encryption key for the encrypted data elements is deleted from an encryption key cache upon exceeding a pre-determined time threshold and is replaced with a newly generated encryption key;

transmitting, by the reconciliation system, the transaction update to a notification handler;

receiving, by the reconciliation system, transaction data associated with the transaction update from a transaction query system; and

transmitting, by the reconciliation system, the transaction update to a transaction requestor associated with the transaction data.

9. The system of claim 8 , the operations further comprising:

determining an optimal path for executing the transaction request based, at least in part, on temporal data, transaction data, user preference information, or a combination thereof; and

routing, by the reconciliation system, via the optimal path the transaction update to a matching transaction network notification system for translating the transaction update into a generic non-scheme specific format.

10. The system of claim 8 , wherein the transaction update is received, by the reconciliation system, via at least one of an Application Programing Interface (API) call or a Secure File Transfer Protocol (SFTP) message.

11. The system of claim 8 , the operations further comprising:

transmitting, by the reconciliation system, the transaction update to an account ledger system, an auditing system, and/or a transaction system via one or more transaction event-topic streams.

12. The system of claim 8 , wherein the transaction update is transmitted to the transaction requestor via at least one of an Application Programing Interface (API) call or a Secure File Transfer Protocol (SFTP) message.

13. The system of claim 8 , the operations further comprising further comprising:

generating, by the real-time transaction system, one or more interfaces including information associated with one or more statuses of the transaction request based on the transaction update.

14. The system of claim 8 , wherein the transaction update associated with the transaction request is received in real-time when the transaction network generates one or more updates associated with the transaction request.

15. A non-transitory computer-readable medium storing instructions for executing a real-time transaction, the instructions, when executed by one or more processors, causing the one or more processors to perform operations comprising:

receiving, by a reconciliation system, a transaction update associated with a transaction request from a transaction network;

authenticating, by the reconciliation system, the transaction update by communicating with an authentication system;

translating, by the reconciliation system, the transaction update into at least another format that is suitable for normalization;

encrypting, by the reconciliation system, data elements of the transaction request, wherein an encryption key for the encrypted data elements is deleted from an encryption key cache upon exceeding a pre-determined time threshold and is replaced with a newly generated encryption key;

transmitting, by the reconciliation system, the transaction update to a notification handler;

receiving, by the reconciliation system, transaction data associated with the transaction update from a transaction query system; and

transmitting, by the reconciliation system, the transaction update to a transaction requestor associated with the transaction data.

16. The computer-readable medium of claim 15 , the operations further comprising:

determining an optimal path for executing the transaction request based, at least in part, on temporal data, transaction data, user preference information, or a combination thereof; and

routing, by the reconciliation system, via the optimal path the transaction update to a matching transaction network notification system for translating the transaction update into a generic non-scheme specific format.

17. The computer-readable medium of claim 15 , wherein the transaction update is received, by the reconciliation system, via at least one of an Application Programing Interface (API) call or a Secure File Transfer Protocol (SFTP) message; and

wherein the transaction update is transmitted to the transaction requestor at least one of an Application Programing Interface (API) call or a Secure File Transfer Protocol (SFTP) message.

18. The computer-readable medium of claim 15 , the operations further comprising:

transmitting, by the reconciliation system, the transaction update to an account ledger system, an auditing system, and/or a transaction system via one or more transaction event-topic streams.

19. The computer-readable medium of claim 15 , the operations further comprising further comprising:

generating, by the real-time transaction system, one or more interfaces including information associated with one or more statuses of the transaction request based on the transaction update.

20. The computer-readable medium of claim 15 , wherein the transaction update associated with the transaction request is received in real-time when the transaction network generates one or more updates associated with the transaction request.

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 Feb 5, 2024
From: FIDELITY INFORMATION SERVICES, LLC
To: WORLDPAY, LLC
Reel/Frame 066345/0536 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 3, 2021
From: WIED, WILLIAM J.; CHEEMA, AMAN S.; DRAGAN, MANUELA; DINAN, STEPHEN E.
To: FIDELITY INFORMATION SERVICES, LLC
Reel/Frame 056428/0075 →
Continuity (1)
Related Publication 20220391892A1 · Dec 8, 2022