Hacker-resistant balance monitoring

• US 8,886,570 B1
• Filed: 10/29/2013
• Issued: 11/11/2014
• Est. Priority Date: 10/29/2013
• Status: Expired due to Fees

• Current Assignee: Quisk, Inc.
• Original Assignee: Quisk, Inc.
• Inventors: Amancherla, Praveen
• Primary Examiner(s): OBEID, MAMON A
• Application Number:
  US14/066,674
• Time in Patent Office: 378 Days
• Field of Search: 705 64- 67, 235379-3825
• US Class Current: 705/67
• CPC Class Codes: G06Q 20/36 using electronic wallets or electronic money safes
• CPC Class Codes: G06Q 20/3676 Balancing accounts
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 20/4016 involving fraud or risk level assessment in transaction processing

Abstract

Methods of and systems for securely monitoring a balance of a payment account include storing, in a first database, ledger data and storing, in a second database, wallet data. Wallet data includes a wallet balance value for the payment account. When a transaction is initiated using the payment account, an access operation is performed on the wallet table. Illicit or improper modifications can be detected by deriving a ledger comparison value from the ledger data and comparing the derived ledger comparison value to a wallet comparison value from the wallet data.

Claims

1. A computer-implemented method of securely monitoring a balance of a payment account, comprising:

storing by a request processor, in a ledger table in a first database, ledger data, the first database being stored on a non-transitory computer-readable storage medium;

storing by the request processor, in a wallet table in a second database, wallet data that includes a wallet balance value for the payment account, the second database being stored in a cache with a cache data rate that is higher than a storage media data rate of the storage medium;

during a detection operation, detecting by the request processor that at least one of the ledger table and the wallet table has been improperly modified by an illicit event occurrence, the detecting including;

deriving by the request processor a ledger comparison value from the ledger data;

comparing by the request processor the derived ledger comparison value to a wallet comparison value from the wallet data; and

in response to the comparing, reconciling by the request processor the wallet data in the wallet table with the ledger data in the ledger table; and

during a transaction operation using the payment account, performing by the request processor an access operation on the wallet table with the reconciled wallet data;

wherein the access operation is a balance check operation that reads the wallet balance value from the reconciled wallet data in the wallet table; and

wherein during the transaction operation, the transaction is initiated and approved without performing any access operations on the reconciled ledger data in the ledger table.

2. The computer-implemented method of claim 1, further comprising:

maintaining the ledger data solely in a protected memory space for a duration of the detecting step; and

erasing the ledger data from the protected memory space when the detecting step is complete.

3. The computer-implemented method of claim 1, further comprising:

mirroring the wallet data across a number of wallet data storage locations, the number of wallet data storage locations being greater than a number of ledger data storage locations.

4. The computer-implemented method of claim 1, further comprising

performing the following steps:

updating by the request processor the wallet table based on the transaction, and

updating by the request processor the ledger table based on the transaction.

5. The computer-implemented method of claim 1, wherein

the ledger data includes transaction information of completed transactions, and

the wallet comparison value is the wallet balance value.

6. The computer-implemented method of claim 5, wherein the deriving step includes (i) reading an old balance from the ledger table, (ii) summing existing credits and existing debits of new transactions with the old balance to obtain a new balance, and (iii) using the new balance as the derived ledger comparison value.

7. The computer-implemented method of claim 1, further comprising:

setting a wallet data flag on the wallet data, the wallet data flag restricting a set of access operations that can be performed on the wallet data.

8. The computer-implemented method of claim 1, further comprising:

accounting the ledger data with a financial institution at a first predetermined period.

9. The computer-implemented method of claim 8, wherein the comparing step is performed at a second predetermined period that is determined as a function of the first predetermined period.

10. The computer-implemented method of claim 9, wherein at least one of the first predetermined period and the second predetermined period is configurable by an account administrator.