Message handling at a mobile gateway for managing data structures and sub-structures

• US 10,332,119 B2
• Filed: 09/18/2015
• Issued: 06/25/2019
• Est. Priority Date: 09/18/2014
• Status: Active Grant

• Current Assignee: First Data Corporation (Fiserv Incorporated)
• Original Assignee: First Data Corporation (Fiserv Incorporated)
• Inventors: Desai, Jigar, Pavlik, Francis, Sanchez, Scott, Francis, Scott, Luxford, Deneen, Russo, Eva, Wiggins, Phillip, Borenstein, Matthew
• Primary Examiner(s): Milef, Elda G
• Application Number:
  US14/859,149
• Publication Number:
  US 20160086160A1
• Time in Patent Office: 1,376 Days
• CPC Class Codes: G06Q 20/3223 Realising banking transactions through M-devices
• CPC Class Codes: G06Q 20/405 Establishing or using transaction specific rules
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03

Abstract

Users of mobile devices communicate through a mobile gateway to a transaction processing system. The transaction processing system manages accounts, such as debit card accounts, for the users. The accounts include a main account for each user and sub accounts that are linked or related to the main account. Funds may be transferred between a main account and its linked sub accounts, including automatic funds transfer when a transaction (e.g., a payroll deposit from an employer or a debit transaction at a specified retailer) is made against the main account and meets certain parameters established by a user. Access to linked sub accounts is made through use of internal account IDs, rather than the account number of the main account.

Claims

1. A method for managing transactions conducted at a mobile device, comprising:

creating, at a memory device in a transaction processing system, multiple data structures associated with the mobile device user, the data structures including a first data structure representing a main account of the user and a second data structure representing a sub account of the user,

the first data structure including at least;

(1) a first internal account ID identifying the main account, (2) a separate primary account number (PAN) identifying the main account that is provided to the user for accessing the main account, (3) a second internal account ID identifying the sub account, and (4) main account ledger data,

the second data structure including at least (1) the second internal account ID identifying the sub account, and (2) sub account ledger data, the sub account accessed by the second internal account ID and not known to the user, with the sub account thereby not being accessible to the user when accessing the main account,

the first internal account ID and the second internal account ID used to link the main account and the sub account and used in performing an automatic funds transfer transaction;

at a processor in the transaction processing system, managing an automatic funds transfer transaction from the main account to the sub account, by;

receiving, from the mobile device associated with the user, a request to automatically transfer funds from the main account to the sub account, after a specified triggering transaction has been posted to the main account, wherein transactions posted to the main account each have an associated transaction type code;

determining, from the request, a predetermined transaction type associated with the specified triggering transaction;

thereafter, evaluating a transaction message received at the transaction processing system for each transaction posted to the main account, to identify a transaction type code associated with the predetermined transaction type;

upon receiving a transaction at the main account having the predetermined transaction type associated with the specified triggering transaction, based at least in part on the identified transaction type code, immediately performing the automatic funds transfer from the main account to the sub account, rather than at the end of a day, using the first and second data structures; and

sending notification to the user that the automatic funds transfer from the main account to the sub account has occurred.

2. The method of claim 1, wherein the main account comprises a debit card account.

3. The method of claim 1, wherein the main account comprises a stored value account.

4. The method of claim 1, wherein the specified triggering transaction comprises a deposit transaction.

5. The method of claim 4, wherein the deposit transaction comprises a payroll deposit transaction.

6. The method of claim 5, where an ACH message is sent to the transaction processing system for purposes of conducting the payroll deposit transaction, and wherein the specified triggering transaction is determined from review of the ACH message.

7. The method of claim 1, wherein the specified triggering transaction comprises a debit transaction.

8. The method of claim 7, wherein a debit transaction authorization message is sent to the transaction processing system for purposes of conducting the debit transaction, and wherein the specified triggering transaction is determined from review of the debit transaction authorization message.

9. The method of claim 8, wherein the specified triggering transaction is further determined based at least in part on a merchant ID in the debit transaction authorization message.

10. The method of claim 1, wherein the request to automatically transfer funds from the main account to the sub account includes a specified transaction type code, and wherein the predetermined transaction type associated with the specified triggering transaction is based at least in part on the specified transaction type code.

11. The method of claim 10, wherein the predetermined transaction type associated with the specified triggering transaction is further based on a predetermined amount of the specified triggering transaction, wherein the predetermined amount is one of a specified monetary amount, a minimum monetary amount, a maximum monetary amount, or a range of monetary amounts.

12. A transaction processing system for managing transactions conducted at a mobile device, comprising:

a processor; and

a memory, the memory storing instructions that are executable by the processor to;

create, at a memory device in a transaction processing system, multiple data structures associated with the mobile device user, the data structures including a first data structure representing a main account of the user and a second data structure representing a sub account of the user,

the first data structure including at least;

(1) a first internal account ID identifying the main account, (2) a separate primary account number (PAN) identifying the main account that is provided to the user for accessing the main account, (3) a second internal account ID identifying the sub account, and (4) main account ledger data,

the second data structure including at least (1) the second internal account ID identifying the sub account, and (2) sub account ledger data, the sub account accessed by the second internal account ID and not known to the user, with the sub account thereby not being accessible to the user when accessing the main account,

the first internal account ID and the second internal account ID used to link the main account and the sub account and used in performing an automatic funds transfer transaction;

manage an automatic funds transfer transaction from the main account to the sub account, by;

receiving, from the mobile device associated with the user, a request to automatically transfer funds from the main account to the sub account, after a specified triggering transaction has been posted to the main account, wherein transactions posted to the main account each have an associated transaction type code;

determining, from the request, a predetermined transaction type associated with the specified triggering transaction;

thereafter, evaluating a transaction message received at the transaction processing system for each transaction posted to the main account, to identify a transaction type code associated with the predetermined transaction type;

upon receiving a transaction at the main account having the predetermined transaction type associated with the specified triggering transaction, based at least in part on the identified transaction type code, immediately performing the automatic funds transfer from the main account to the sub account, rather than at the end of a day, using the first and second data structures; and

sending notification to the user that the automatic funds transfer from the main account to the sub account has occurred.

13. The system of claim 12, wherein the main account comprises a debit card account.

14. The system of claim 12, wherein the main account comprises a stored value account.

15. The system of claim 12, wherein the specified triggering transaction comprises a deposit transaction.

16. The system of claim 15, wherein the deposit transaction comprises a payroll deposit transaction.

17. The system of claim 16, where an ACH message is sent to the transaction processing system for purposes of conducting the payroll deposit transaction, and wherein the specified triggering transaction is determined from review of the ACH message.

18. The system of claim 12, wherein the specified triggering transaction comprises a debit transaction.

19. The system of claim 18, wherein a debit transaction authorization message is sent to the transaction processing system for purposes of conducting the debit transaction, and wherein the specified triggering transaction is determined from review of the debit transaction authorization message.

20. The system of claim 19, wherein the specified triggering transaction is further determined based at least in part on a merchant ID in the debit transaction authorization message.

21. The system of claim 12, wherein the request to automatically transfer funds from the main account to the sub account includes a specified transaction type code, and wherein the predetermined transaction type associated with the specified triggering transaction is based at least in part on the specified transaction type code.

22. The system of claim 21, wherein the predetermined transaction type associated with the specified triggering transaction is further based on a predetermined amount of the specified triggering transaction, wherein the predetermined amount is one of a specified monetary amount, a minimum monetary amount, a maximum monetary amount, or a range of monetary amounts.