SYSTEMS AND METHODS FOR REAL-TIME ACCOUNT ACCESS

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 None
App. No.: 19/537,721

External Links

USPTO Patent Center↗ Full Patent PDF↗

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 (35)

1 .- 60 . (canceled)

61 . A method for generating a transaction request, comprising:

receiving a customer credential, wherein the customer credential includes a unique customer identifier and do not include an account number or a card number;

generating a second identifier based on the unique customer identifier;

generating the transaction request, wherein the transaction request includes a data structure configurable to be in a first mode or a second mode and comprising information relating to a transaction, including the generated second identifier; and

submitting the generated transaction request for processing, wherein the generated second identifier is used to determine routing information for the transaction request and to route the transaction request to an accounting computer system based on the determined routing information.

62 . The method of claim 61 , wherein the customer credential includes a pseudo-identifier that resolves to an account number when referenced in a database.

63 . The method of claim 61 , wherein the customer credential includes at least one of an email address, a phone number, a username, or a social network identity.

64 . The method of claim 61 , wherein the generated second identifier is a coded value based on the customer credential.

65 . The method of claim 61 , wherein the generated second identifier is an encrypted value based on the customer credential.

66 . The method of claim 61 , wherein the generated transaction request further includes a transaction type, a transaction date, and a transaction amount.

67 . The method of claim 61 , wherein the transaction request includes the data structure received from a customer device, a merchant device, or a financial institution.

68 . A system for generating a transaction request, 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 a customer credential, wherein the customer credential includes a unique customer identifier and do not include an account number or a card number;

generating a second identifier based on the unique customer identifier;

69 . The system of claim 68 , wherein the customer credential includes a pseudo-identifier that resolves to an account number when referenced in a database.

70 . The system of claim 68 , wherein the customer credential includes at least one of an email address, a phone number, a username, or a social network identity.

71 . The system of claim 68 , wherein the generated second identifier is a coded value based on the customer credential.

72 . The system of claim 68 , wherein the generated second identifier is an encrypted value based on the customer credential.

73 . The system of claim 68 , wherein the generated transaction request further includes a transaction type, a transaction date, and a transaction amount.

74 . The system of claim 68 , wherein the transaction request includes the data structure received from a customer device, a merchant device, or a financial institution.

75 . A non-transitory computer-readable medium comprising instructions that when executed by at least one processor cause the at least one processor to perform a method comprising:

receiving a customer credential, wherein the customer credential includes a unique customer identifier and do not include an account number or a card number;

generating a second identifier based on the unique customer identifier;

generating a transaction request, wherein the transaction request includes a data structure configurable to be in a first mode or a second mode and comprising information relating to a transaction, including the generated second identifier; and

76 . The non-transitory computer-readable medium of claim 75 , wherein the customer credential includes a pseudo-identifier that resolves to an account number when referenced in a database.

77 . The non-transitory computer-readable medium of claim 75 , wherein the customer credential includes at least one of an email address, a phone number, a username, or a social network identity.

78 . The non-transitory computer-readable medium of claim 75 , wherein the generated second identifier is a coded value based on the customer credential.

79 . The non-transitory computer-readable medium of claim 75 , wherein the generated second identifier is an encrypted value based on the customer credential.

80 . The non-transitory computer-readable medium of claim 75 , wherein the generated transaction request further includes a transaction type, a transaction date, and a transaction amount.