IP Library Granted Patent US 11,562,334
Granted Patent B2
US 11,562,334 · App. 15/931,564 · Granted Jan 24, 2023

Systems and methods for real-time account access

Inventors: Neil Marcous (Bay Head, NJ); Robert Woodbury (Flemington, NJ); Peter Gordon (Sharon, MA)
Assignee: Fidelity Information Services, LLC
G06Q20/10G06Q20/12G06Q20/20G06Q20/385G06Q20/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,562,334
App. No.
15/931,564
Granted
Jan 24, 2023
Kind
B2
Abstract

Systems and methods for real-time account access, allowing access to accounts (such as deposit, credit, or debit accounts) through network processing infrastructures such as Electronic Funds Transfer (EFT). In some embodiments, consumers and/or merchants are able to effect transaction requests against accounts, using a pseudo-identifier or other identifier, and without the need to provide an account number or card number. In other embodiments, payment networks are able to route and process transaction requests against accounts, without having a card number or account number. In other embodiments, account processing systems are able to determine an appropriate account based on transaction requests that do not contain card numbers or account numbers.

Claims (53)

1. A method for processing payment transactions via a network comprising:

receiving an EFTPOS transaction request, the transaction request comprising a data structure, the data structure being in a native mode or a non-native mode;

locating, based on the data structure being in a non-native mode, a pseudo-identifier in the data structure, the pseudo-identifier containing a portion indicating that the pseudo-identifier is not an account number or a card number;

determining an accounting computer system based on the pseudo-identifier, the determining of the accounting computing system being based on the pseudo-identifier and an existence of the portion within the data structure;

routing the transaction request to the accounting computer system;

receiving a response from the accounting computer system, the response comprising information based on an account balance; and

determining whether to approve or deny the transaction request based on the response.

2. The method of claim 1 , the method further comprising selecting the accounting computer system based on information stored in a data store and the transaction request, wherein routing the transaction request to the accounting computer system is further based on the selecting of the accounting computer system.

3. The method of claim 1 , the method further comprising:

generating a notification based on the determination of whether to approve or deny the transaction request based on the response, the notification including information indicating whether the transaction request was approved or denied; and

transmitting the notification to at least one of a payment network or an acquirer processor associated with the request.

4. The method of claim 1 , wherein the pseudo-identifier comprises a limited use pseudo-identifier.

5. The method of claim 1 , wherein the pseudo-identifier comprises data indicating the pseudo-identifier does not comprise an account number or a card number.

6. The method of claim 1 , wherein the data structure comprises information signifying attributes of a transaction.

7. The method of claim 1 , wherein the transaction request is received from a payment network as part of a batch operation.

8. The method of claim 1 , wherein the transaction request is received from a payment system in an event triggered by the payment system receiving the transaction request from an acquirer system.

9. The method of claim 1 , wherein the information based on the account balance indicates that a transaction is authorized or is unauthorized.

10. The method of claim 1 , wherein the information based on the account balance comprises the account balance.

11. The method of claim 1 , the method further comprising reconciling a transaction based on the determining whether to approve or deny the transaction request.

12. The method of claim 1 , wherein the accounting computer system is associated with an issuer.

13. The method of claim 1 , wherein the data structure comprises information uniquely identifying a user.

14. The method of claim 1 , wherein the transaction request comprises at least one of:

a request for a current balance;

a request for whether at least one of an available balance or a ledger balance is more than, less than, or equal to an amount in the transaction request;

a request for an account health indicator; or

a request for information associated with a user.

15. The method of claim 1 , the method further comprising:

transmitting a notification to an acquirer system via a payment network, the notification including a request for further information.

16. The method of claim 1 , the method further comprising returning crediting a monetary amount to the account based on the transaction request.

17. The method of claim 1 , wherein receiving a transaction request comprising receiving the transaction request at an Electronic Fund Transfer (EFT) system.

18. The method of claim 1 , wherein the transaction request comprises digits of a magnetic ink character recognition.

19. A system for processing a payment transaction, comprising:

at least one processor; and

at least one memory containing instructions that, when executed by the at least one processor, cause the at least one processor to perform a method comprising:

receiving an EFTPOS transaction request, the transaction request comprising a data structure, the data structure being in a native mode or a non-native mode;

locating based on the data structure being in a non-native mode, a pseudo-identifier in the data structure, the pseudo-identifier containing a portion indicating that the pseudo-identifier is not an account number or a card number;

determining an accounting computer system based on the pseudo-identifier, the determining of the accounting computer system being based on the pseudo-identifier and an existence of the portion within the data structure;

routing the transaction request to the accounting computer system;

receiving a response from the accounting computer system; and

based on the response, performing one of:

approving the transaction;

denying the transaction; or

transmitting a request for further information associated with the transaction.

20. A method for processing payment transactions via a network comprising:

receiving an EFTPOS transaction request, the transaction request comprising a data structure, the data structure being in a native mode or a non-native mode;

locating based on the data structure being in a non-native mode, a pseudo-identifier in the data structure, the pseudo-identifier containing a portion indicating that the pseudo-identifier is not an account number or a card number;

determining an accounting computer system based on the pseudo-identifier, the determining of the accounting computer system being based on the pseudo-identifier and an existence of the portion within the data structure;

routing the transaction request to the accounting computer system;

receiving a response from the accounting computer system; and

based on the response, performing one of:

approving the transaction;

denying the transaction; or

transmitting a request for further information associated with the transaction.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 15, 2021
From: NYCE PAYMENTS NETWORK, LLC
To: FIDELITY INFORMATION SERVICES, LLC
Reel/Frame 057181/0088 →
MERGER Recorded Apr 14, 2021
From: PAYNET PAYMENTS NETWORK, LLC
To: NYCE PAYMENTS NETWORK, LLC
Reel/Frame 055914/0779 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 14, 2020
From: MARCOUS, NEIL; WOODBURY, ROBERT; GORDON, PETER
To: PAYNET PAYMENTS NETWORK, LLC
Reel/Frame 052663/0008 →
Continuity (4)
Continuation 16715818 · Dec 16, 2019
Continuation 13835452 · Mar 15, 2013
Provisional Application 61612897 · Mar 19, 2012
Related Publication 20200273004A1 · Aug 27, 2020