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

Patent metadata

Field	Value
Publication number	US-10956913-B2
Application number	US-201916412032-A
Country	US
Kind code	B2
Filing date	May 14, 2019
Priority date	Sep 18, 2014
Publication date	Mar 23, 2021
Grant date	Mar 23, 2021

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.

First claim

The invention claimed is:

1. A method for managing transactions conducted at a mobile device, comprising:
storing, at a memory device in a transaction processing system, multiple data structures associated with a mobile device user, the data structures including a first data structure representing a main account of the mobile device user and a second data structure representing a sub account of the mobile device 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 mobile device 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 mobile device user, with the sub account thereby not being accessible to the mobile device user when accessing the main account, the first internal account ID and the second internal account ID linking the main account and the sub account in performing a funds transfer transaction between the main account and the sub account;
managing, by a processor in the transaction processing system, a funds transfer transaction from the main account to the sub account in response to a specified triggering transaction established by the mobile device user, wherein transactions posted to the main account each have an associated transaction type code, and wherein managing a funds transfer includes:
evaluating a transaction message received at the transaction processing system for each transaction posted to the main account, to identify a predetermined transaction type code associated with the specified triggering transaction established by the mobile device user; and
upon receiving a transaction at the main account having the predetermined transaction type code associated with the specified triggering transaction, immediately performing an 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.

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 for the predetermined transaction type code.

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 9 , wherein 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.

11. The method of claim 1 , further comprising:
receiving, from the mobile device associated with the user, a request to automatically transfer funds from the main account to the sub account, after the specified triggering transaction has been posted to the main account; and
determining, from the request, the predetermined transaction type code associated with the specified triggering transaction.

12. The method of claim 11 , wherein the request to automatically transfer funds from the main account to the sub account includes the specified transaction type code.

13. The method of claim 1 , further comprising sending notification to the user that the automatic funds transfer from the main account to the sub account has occurred.

14. 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:
store, at a memory device in a transaction processing system, multiple data structures associated with a mobile device user, the data structures including a first data structure representing a main account of the mobile device user and a second data structure representing a sub account of the mobile device 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 mobile device 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, with the second internal account ID 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 linking the main account and the sub account in performing a funds transfer transaction;
manage a funds transfer transaction from the main account to the sub account in response to a specified triggering transaction established by the mobile device user, wherein transactions posted to the main account each have an associated transaction type code, and wherein managing a funds transfer includes:
evaluating a transaction message received at the transaction processing system for each transaction posted to the main account, to identify a predetermined transaction type code associated with the specified triggering transaction established by the mobile device user; and
upon receiving a transaction at the main account having the predetermined transaction type code associated with the specified triggering transaction, immediately performing an 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.

15. The system of claim 14 , wherein the main account comprises a debit card account.

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

17. The system of claim 14 , wherein the specified triggering transaction comprises a deposit transaction.

18. The system of claim 17 , wherein the deposit transaction comprises a payroll deposit transaction.

19. The system of claim 14 , wherein the instructions are further executable by the processor to:
receive, from the mobile device associated with the user, a request to automatically transfer funds from the main account to the sub account, after the specified triggering transaction has been posted to the main account; and

Assignees

• First Data Corp

Inventors

• Desai Jigar
• Pavlik Francis
• Sanchez Scott
• Francis Scott
• Luxford Deneen
• Russo Eva
• Wiggins Phillip
• Borenstein Matthew

Classifications

• G06Q40/02

  Banking, e.g. interest calculation or account maintenance (credit or loans G06Q40/03) · CPC title

• G06Q20/3223

  Realising banking transactions through M-devices · CPC title

• G06Q20/405 Primary

  Establishing or using transaction specific rules · CPC title