# US 12,008,632 B2 · Methods and systems for recovering a failed payment processing request

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 12,008,632 B2
- Document ID: US12008632B2
- Status: Granted
- Kind: B2
- Application number: 17/397,584
- Filed: 2021-08-09
- Published: 2022-03-03
- Granted: 2024-06-11
- Earliest claimed: 2020-09-03
- Assignees: Mastercard International Incorporated
- Applicants: Mastercard International Incorporated
- Inventors: Abhay Mandloi; Rajeev Kumar; Aravindan Ramamoorthy
- Web page: https://patentgrep.com/patent/US12008632B2

## CPC

- G06Q 30/0641: {utilising user interfaces specially adapted for shopping}
- G06F 11/0757: {by exceeding a time limit, i.e. time-out, e.g. watchdogs}
- G06F 11/1474: in transactions (updating of structured data in databases G06F16/23)
- G06Q 20/02: involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
- G06Q 20/12: specially adapted for electronic shopping systems
- G06Q 20/24: Credit schemes, i.e. "pay after"
- G06Q 20/34: using cards, e.g. integrated circuit [IC] cards or magnetic cards
- G06Q 20/401: {Transaction verification}
- G06Q 20/4012: {Verifying personal identification numbers [PIN]}
- G06Q 20/4016: {involving fraud or risk level assessment in transaction processing}
- G06Q 20/407: {Cancellation of a transaction}
- G06Q 20/42: Confirmation, e.g. check or permission by the legal debtor of payment
- G06F 2201/805: Real-time
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Embodiments provide methods and systems for recovering a failed payment processing request. Method includes receiving, by a server system associated with a payment network, a transaction recovery request signal initiated from a User Interface (UI) of a merchant application running on a user device for recovering a payment transaction failed due to a disconnection between the server system and a merchant server. The request signal includes a unique ID associated with the payment transaction. The method includes electronically retrieving a corresponding transaction information stored against the unique ID. The transaction information includes a transaction status. The unique ID is sent in advance by the merchant server along with a transaction amount. The method includes identifying the transaction status as an approved payment transaction. The method includes sending a confirmation notification signal including the transaction status to the merchant server. The merchant server is configured to complete the payment transaction.

## Claims

### Claim 1

A computer-implemented method, the method comprising:
receiving, by a payment network server system from a merchant server, a payment transaction request and a first unique Identifier (ID) associated with the payment transaction request, the payment transaction request including transaction information associated with a payment transaction, the transaction information including a transaction amount;
storing, by the server, the first unique ID and the transaction information in a database;
receiving, by the server system from the merchant server, a transaction recovery request signal initiated from a User Interface (UI) of a merchant application running on a user device, the transaction recovery request signal comprising a second unique Identifier (ID) associated with the payment transaction, the payment transaction having failed due to a disconnection between the server system and the merchant server;
determining, by the server system, that the second unique ID matches the first unique ID stored in the database;
based on the match, electronically retrieving, by the server system, the transaction information stored against the first unique ID, wherein the transaction information comprises a transaction status of the payment transaction;
identifying, by the server system, the transaction status of the payment transaction as an approved payment transaction; and
sending, by the server system, a confirmation notification signal comprising the transaction status of the payment transaction as the approved payment transaction to the merchant server, wherein the merchant server completes the payment transaction failed due to the disconnection between the server system and the merchant server based on the confirmation notification signal received from the server system.

### Claim 2 (depends on 1)

The method as claimed in claim 1, wherein the server system is one of a payment gateway server and an acquirer server.

### Claim 3 (depends on 2)

The method as claimed in claim 2, the method further comprising:
receiving a recovery code from an issuer server; and
storing the recovery code against the corresponding transaction information of the payment transaction.

### Claim 4 (depends on 3)

The method as claimed in claim 3, further comprising:
receiving the recovery code entered on the UI of the merchant application to initiate the transaction recovery request signal, wherein the recovery code is sent to the user device via a notification message signal along with the transaction status of the payment transaction by the issuer server.

### Claim 5 (depends on 3)

The method as claimed in claim 3, wherein the payment transaction is approved based on performing by the issuer server, each of:
a successful authentication of a user,
a successful authorization of a user account,
a debiting of the transaction amount from the user account, and
sending a transaction status notification signal comprising the transaction status of the payment transaction as the approved payment transaction.

### Claim 6 (depends on 2)

The method as claimed in claim 2, wherein each of the first and second unique ID is a combination of a Primary Account Number (PAN), a transaction date, a transaction time, and the transaction amount.

### Claim 7 (depends on 2)

The method as claimed in claim 2, wherein the first unique ID is dynamically generated by the merchant server for the payment transaction based on one or more attributes.

### Claim 8 (depends on 2)

The method as claimed in claim 2, wherein each of the first and second unique ID is discarded upon completion of the payment transaction.

### Claim 9 (depends on 2)

The method as claimed in claim 2, wherein the transaction information comprises the transaction amount, a transaction payment method information, the transaction status, and a login ID associated with a user of the merchant application.

### Claim 10

A server system in a payment network, the server system comprising:
a communication interface configured to:
receive, from a merchant server, a payment transaction request and a first unique Identifier (ID) associated with the payment transaction request, the payment transaction request including transaction information associated with a payment transaction, the transaction information including a transaction amount; and
receive, from the merchant server, a transaction recovery request signal initiated from a User Interface (UI) of a merchant application running on a user device, the transaction recovery request signal comprising a second unique Identifier (ID) associated with the payment transaction, the payment transaction having failed due to a disconnection between the server system and the merchant server;
a database;
a memory comprising executable instructions; and
a processor communicably coupled to the database and the communication interface, the processor configured to execute the instructions to cause the server system to at least:
store the first unique ID and the transaction information in a database;
determine that the second unique ID matches the first unique ID stored in the database;
based on the match, electronically retrieve the transaction information stored against the first unique ID, wherein the transaction information comprises a transaction status of the payment transaction;
identify the transaction status of the payment transaction as an approved payment transaction; and
send a confirmation notification signal comprising the transaction status of the payment transaction as the approved payment transaction to the merchant server, wherein the merchant server completes the payment transaction failed due to the disconnection between the server system and the merchant server based on the confirmation notification signal received from the server system.

### Claim 11 (depends on 10)

The server system as claimed in claim 10, wherein the server system is one of a payment gateway server and an acquirer server.

### Claim 12 (depends on 11)

The server system as claimed in claim 11, wherein the server system is further caused at least in part to:
receive a recovery code from an issuer server; and
store the recovery code against the corresponding transaction information of the payment transaction.

### Claim 13 (depends on 12)

The server system as claimed in claim 12, wherein the server system is further caused at least in part to:
receive the recovery code entered on the UI of the merchant application to initiate the transaction recovery request signal, wherein the recovery code is sent to the user device via a notification message signal along with the transaction status of the payment transaction by the issuer server.

### Claim 14 (depends on 12)

The server system as claimed in claim 12, wherein the payment transaction is approved based on performing by the issuer server, each of:
a successful authentication of a user,
a successful authorization of a user account,
a debiting of the transaction amount from the user account, and
sending a transaction status notification signal comprising the transaction status of the payment transaction as the approved payment transaction.

### Claim 15 (depends on 11)

The server system as claimed in claim 11, wherein each of the first and second unique ID is a combination of a Primary Account Number (PAN), a transaction date, a transaction time and the transaction amount.

### Claim 16 (depends on 11)

The server system as claimed in claim 11, wherein the first unique ID is dynamically generated by the merchant server for the payment transaction.

### Claim 17 (depends on 11)

The server system as claimed in claim 11, wherein each of the first and second unique ID is removed upon completion of the payment transaction.

### Claim 18 (depends on 11)

The server system as claimed in claim 11, wherein the transaction information comprises the transaction amount, a transaction payment method information, the transaction status, and a login ID associated with a user of the merchant application.

### Claim 19

A server system in a payment network, the server system comprising:
a communication module configured to:
electronically facilitate display of a User Interface (UI) of a merchant application on a user device;
receive a payment transaction request from the merchant application, the payment transaction request including transaction information associated with a payment transaction, the transaction information including a transaction amount, a transaction date, and a transaction time; and
receive, from the merchant application, a transaction recovery request signal initiated from the UI, the transaction recovery request signal comprising a second unique Identifier (ID) associated with the payment transaction, the payment transaction having failed due to a disconnection between the server system and a payment gateway server;
a memory comprising executable instructions; and
a processing module communicably coupled to the communication module and configured to execute the instructions to cause the server system to at least:
generate a first unique Identifier (ID) associated with the payment transaction request, the first unique ID comprising a combination of a Primary Account Number (PAN), the transaction date, the transaction time, and the transaction amount;
transmit the payment transaction request and the first unique ID associated with the payment transaction request to the payment gateway server;
add the first unique ID to the received transaction recovery request signal;
send the transaction recovery request signal comprising the first unique ID to the payment gateway server;
receive a confirmation notification signal comprising a transaction status of the payment transaction as an approved payment transaction from the payment gateway server, wherein the payment gateway server is configured to electronically retrieve a corresponding transaction information stored against the unique ID, the transaction information comprising the transaction status of the payment transaction; and
electronically completion of complete the payment transaction failed due to the disconnection between the server system and the payment gateway server by capturing the payment transaction, based on receiving the confirmation notification signal from the payment gateway server.

### Claim 20 (depends on 19)

The server system as claimed in claim 19, wherein the unique ID is dynamically generated and wherein the unique ID is removed upon the completion of the payment transaction.