Method and system for retry processing of controlled payment transactions

Patent metadata

Field	Value
Publication number	US-2016203484-A1
Application number	US-201514594582-A
Country	US
Kind code	A1
Filing date	Jan 12, 2015
Priority date	Jan 12, 2015
Publication date	Jul 14, 2016
Grant date	—

Abstract

A method for retrying processing of a controlled payment transaction includes: storing, in a first database, account profiles, each including data related to a transaction account including an account identifier and account controls; storing, in a second database, the account profiles stored in the first database, wherein data in each account profile in the second database corresponds to data in the corresponding account profile in the first database; receiving an authorization request for a transaction, the request including a specific account identifier and transaction data; determining an approval or denial of the transaction based on the account controls included in a profile in the second database including the specific account identifier and the transaction data if an attempt to determine approval or denial based on the account controls included in a corresponding account profile in the first database fails; and processing the payment transaction based on the determination.

First claim

What is claimed is:

1 . A method for retrying processing of a controlled payment number transaction, comprising:
storing, in a first database, a plurality of account profiles, wherein each account profile includes data related to a transaction account including at least an account identifier and one or more account controls; storing, in a second database, each of the plurality of account profiles stored in the first database, wherein data included in each account profile stored in the second database corresponds to data included in the corresponding account profile in the first database, and wherein the second database is a read-only database; receiving, by a receiving device, an authorization request for a payment transaction, wherein the authorization request includes at least a specific account identifier and transaction data; determining, by a processing device, an approval or denial of the payment transaction based on at least the one or more account controls included in an account profile stored in the second database where the included account identifier corresponds to the specific account identifier and the transaction data included in the received authorization request if an attempt, by the processing device, to determine approval or denial of the payment transaction based on the one or more account controls included in a corresponding account profile stored in the first database where the included account identifier corresponds to the specific account identifier fails; and processing, by the processing device, the payment transaction based on the determined approval or denial.

2 . The method of claim 1 , wherein processing the payment transaction includes transmitting, by a transmitting device, (i) an authorization response indicating denial of the transaction as a response to the received authorization request if the payment transaction is determined to be denied, or (ii) the authorization request to a financial institution associated with the transaction account related to the account profile where the included account identifier corresponds to the specific account identifier if the payment transaction is determined to be approved.

3 . The method of claim 1 , further comprising:
updating, in the first database, data included in the account profile where the included account identifier corresponds to the specific account identifier based on the transaction data included in the received authorization request.

4 . The method of claim 3 , wherein the data included in the account profile is updated if the payment transaction is determined to be approved.

5 . The method of claim 1 , further comprising:
storing, in a memory, a transaction processing queue, wherein the transaction processing queue includes one or more pending authorization requests for which processing is required and a determination associated with each of the one or more pending authorization requests.

6 . The method of claim 5 , wherein processing the payment transaction includes storing, in the memory, the received authorization request and the corresponding determination of approval or denial at a top of the transaction processing queue.

7 . The method of claim 5 , further comprising:
updating, for each authorization request included in the stored transaction processing queue, data included in an account profile in the first database where the included account identifier corresponds to an account identifier included in the respective authorization request based on the transaction data included in the respective authorization request.

8 . The method of claim 5 , further comprising:
storing, in the memory, a priority transaction queue, wherein the priority transaction queue is configured to store pending authorization requests for which processing is required and a determination associated with each respective pending authorization request, wherein the processing device is configured to process pending authorization requests stored in the priority transaction queue before processing pending authorization requests stored in the transaction processing queue.

9 . The method of claim 8 , wherein processing the payment transaction includes storing, in the memory, the received authorization request and the corresponding determination of approval or denial in the priority transaction queue.

10 . The method of claim 1 , wherein the attempt to determine approval or denial of the payment transaction fails if the processing device is unable to determine approval or denial of the payment transaction within a predetermined amount of time.

11 . The method of claim 1 , wherein the attempt to determine approval or denial of the payment transaction based on the one or more account controls included in a corresponding account profile stored in the first database is performed by a second processing device.

12 . A system for retrying processing of a controlled payment number transaction, comprising:
a first database configured to store a plurality of account profiles, wherein each account profile includes data related to a transaction account including at least an account identifier and one or more account controls; a second database configured to store each of the plurality of account profiles stored in the first database, wherein data included in each account profile stored in the second database corresponds to data included in the corresponding account profile in the first database, and wherein the second database is a read-only database; a receiving device configured to receive an authorization request for a payment transaction, wherein the authorization request includes at least a specific account identifier and transaction data; and a processing device configured to
determine an approval or denial of the payment transaction based on at least the one or more account controls included in an account profile stored in the second database where the included account identifier corresponds to the specific account identifier and the transaction data included in the received authorization request if an attempt, by the processing device, to determine approval or denial of the payment transaction based on the one or more account controls included in a corresponding account profile stored in the first database where the included account identifier corresponds to the specific account identifier fails, and
process the payment transaction based on the determined approval or denial.

13 . The system of claim 12 , further comprising:
a transmitting device, wherein processing the payment transaction includes transmitting, by a transmitting device, (i) an authorization response indicating denial of the transaction as a response to the received authorization request if the payment transaction is determined to be denied, or (ii) the authorization request to a financial institution associated with the transaction account related to the account profile where the included account identifier corresponds to the specific account identifier if the payment transaction is determined to be approved.

14 . The system of claim 12 , wherein the processing device is further configured to update, in the first database, data included in the account profile where the included account identifier corresponds to the specific account identifier based on the transaction data included in the received authorization request.

15 . The system of claim 14 , wherein the data included in the account profile is updated if the payment transaction is determined to be approved.

16 . The system of claim 12 , further comprising:
a memory configured

Assignees

• Mastercard International Inc

Inventors

• Blinov Mikhail
• Coburn Gregory

Classifications

• G06Q20/405 Primary

  Establishing or using transaction specific rules · CPC title

• G06Q20/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 title

• G06Q20/14 Primary

  specially adapted for billing systems · CPC title

• G06F16/00 Primary

  Information retrieval; Database structures therefor; File system structures therefor · CPC title

• G06Q20/16

  Payments settled via telecommunication systems · CPC title