IP Library › Granted Patent US 11,797,991
Granted Patent B2
US 11,797,991 · App. 17/365,266 · Granted Oct 24, 2023

Systems and methods for secure transaction reversal

Inventors: Viveka Vardhan Ravi (Stamford, CT); Tushar Divecha (Stamford, CT); Deborah Bernert (Stamford, CT); Jonathan M. Schmidt (Stamford, CT); Ashok Uppalapati (Stamford, CT); Ajay Yadav (Stamford, CT); Craig Urbansky (Stamford, CT)
Assignee: SYNCHRONY BANK
G06Q20/401
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,797,991
App. No.
17/365,266
Granted
Oct 24, 2023
Kind
B2
Abstract

Examples describe data security for communication systems. One example includes validating a merchant system using merchant data and generating a set of merchant credentials. The set of merchant credentials is then used in authentication to facilitate a secure transaction, which involves automatically generating transaction data with a tokenized client account number associated with the secure transaction. A refund request associated with the secure transaction is received with the set of merchant credentials that are used for automatically authenticating the merchant system. The example then involves accessing a database that includes the transaction data for automatically facilitating settlement of a refund payment using the authenticated merchant system and the transaction data.

Claims (69)

1. A computer-implemented method for improved security in a communication system, the method comprising:

processing merchant data using one or more processors of an account security system to validate a merchant system using the merchant data;

generating, by the account security system, a set of merchant credentials, wherein the set of merchant credentials includes a parent merchant identifier and a child merchant identifier;

wherein a child merchant system associated with the child merchant identifier operates under a parent structure with harmonized transaction and refund operations with a parent merchant system associated with the parent merchant identifier;

receiving, by the account security system, sensitive client data including a client account number, wherein the sensitive client data is received as part of a secure transaction between the merchant system and a client device;

automatically generating transaction data using the account security system, wherein the transaction data includes a tokenized client account number associated with the secure transaction, wherein the tokenized client account number isolates the merchant system from the client account number;

receiving, at a batch reversal system of the account security system, a refund request associated with the secure transaction, wherein the refund request includes the set of merchant credentials;

automatically authenticating the merchant system using the parent merchant identifier at a parent account layer of the account security system;

processing the refund request using a prefill service to format a database communication;

accessing, by a refund application programming interface (API) of the account security system using the database communication, a database that includes the transaction data;

aggregating the refund request with a plurality of refund requests using the batch reversal system at a child account layer of the account security system;

scheduling batch processing for the plurality of refund requests for a scheduled time when spare resources of the account security system are available; and

automatically facilitating settlement of a refund payment to the child merchant system by the batch reversal system at the child account layer of the account security system using the merchant system authentication and the transaction data in a repeated automatic looped process at the scheduled time for the plurality of refund requests, wherein the child merchant identifier is used without the parent merchant identifier to facilitate the refund payment after the merchant system authentication using the parent merchant identifier.

2. The computer-implemented method of claim 1 , wherein the refund request is associated with a plurality of transactions for the merchant system.

3. The computer-implemented method of claim 1 , wherein the refund request includes two or more of a channel identifier, a merchant number, a transaction amount, a description value, a security code, an address, and a partner code for each transaction of a plurality of transactions associated with the refund request.

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

generating a prefill communication for a refund settlement request using the transaction data from the database in response to the refund request; and

transmitting the prefill communication to a refund settlement system.

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

accessing second transaction data in response to the refund request; and

facilitating a second refund payment for the second transaction data with the refund payment in a batch multi-refund process in response to the refund request.

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

matching the tokenized account number to the client account number using the database of the account security system; and

performing a bank identification number (BIN) range service check to confirm that the client account number has not been compromised.

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

filtering the database communication as formatted by the prefill service using a gateway system to perform a formatting check on data of the refund request;

receiving the database communication at an eligibility service of the account security system via the refund API; and

processing, by the eligibility service of the account security system, the database communication to determine a refund eligibility associated with the child merchant system.

8. The computer-implemented method of claim 1 , wherein the refund request includes a hypertext transport protocol (HTTP) post communication.

9. The computer-implemented method of claim 1 , wherein the refund request includes a hypertext transport protocol (HTTP) get communication.

10. An account security system for providing improved communication security, the account security system comprising:

a memory; and

one or more processors coupled to the memory and configured to perform operations including:

processing merchant data using the one or more processors of the account security system to validate a merchant system using the merchant data;

generating, by the account security system, a set of merchant credentials, wherein the set of merchant credentials includes a parent merchant identifier and a child merchant identifier, wherein a child merchant system associated with the child merchant identifier operates under a parent structure with harmonized transaction and refund operations with a parent merchant system associated with the parent merchant identifier;

receiving, by the account security system, sensitive client data including a client account number, wherein the sensitive client data is received as part of a secure transaction between the merchant system and a client device;

automatically generating transaction data using the account security system, wherein the transaction data includes a tokenized client account number associated with the secure transaction, wherein the tokenized client account number isolates the merchant system from the client account number;

receiving, at a batch reversal system of the account security system, a refund request associated with the secure transaction, wherein the refund request includes the set of merchant credentials;

automatically authenticating the merchant system using the parent merchant identifier at a parent account layer of the account security system;

processing the refund request using a prefill service to format a database communication;

accessing, by a refund application programming interface (API) of the account security system using the database communication, a database that includes the transaction data;

aggregating the refund request with a plurality of refund requests using the batch reversal system at a child account layer of the account security system;

scheduling batch processing for the plurality of refund requests for a scheduled time when spare resources of the account security system are available; and

automatically facilitating settlement of a refund payment to the child merchant system by the batch reversal system at the child account layer of the account security system using the merchant system authentication and the transaction data in a repeated automatic looped process at the scheduled time for the plurality of refund requests, wherein the child merchant identifier is used without the parent merchant identifier to facilitate the refund payment after the merchant system authentication using the parent merchant identifier.

11. The system of claim 10 , wherein the refund request is associated with a plurality of transactions for the merchant system.

12. The system of claim 10 , wherein the refund request includes two or more of a channel identifier, a merchant number, a transaction amount, a description value, a security code, an address, and a partner code for each transaction of a plurality of transactions associated with the refund request.

13. The system of claim 10 , wherein the one or more processors further perform operations comprising:

generating a prefill communication for a refund settlement request using the transaction data from the database in response to the refund request; and

transmitting the prefill communication to a refund settlement system.

14. The system of claim 10 , wherein the one or more processors further perform operations comprising:

accessing second transaction data in response to the refund request; and

facilitating a second refund payment for the second transaction data with the refund payment in a batch multi-refund process in response to the refund request.

15. A non-transitory computer readable medium comprising instructions that, when executed by one or more processors of an account security system-device, cause the account security system to perform operations comprising:

validating processing merchant data using the one or more processors of the account security system to validate a merchant system using the merchant data;

generating, by the account security system, a set of merchant credentials, wherein the set of merchant credentials includes a parent merchant identifier and a child merchant identifier, wherein a child merchant system associated with the child merchant identifier operates under a parent structure with harmonized transaction and refund operations with a parent merchant system associated with the parent merchant identifier;

receiving, by the account security system, sensitive client data including a client account number, wherein the sensitive client data is received as part of a secure transaction between the merchant system and a client device;

automatically generating transaction data using the account security system, wherein the transaction data includes a tokenized client account number associated with the secure transaction, wherein the tokenized client account number isolates the merchant system from the client account number;

receiving, at a batch reversal system of the account security system, a refund request associated with the secure transaction, wherein the refund request includes the set of merchant credentials;

automatically authenticating the merchant system using the parent merchant identifier at a parent account layer of the account security system;

processing the refund request using a prefill service to format a database communication;

accessing, by a refund application programming interface (API) of the account security system using the database communication, a database that includes the transaction data;

aggregating the refund request with a plurality of refund requests using the batch reversal system at a child account layer of the account security system;

scheduling batch processing for the plurality of refund requests for a scheduled time when spare resources of the account security system are available; and

automatically facilitating settlement of a refund payment to the child merchant system by the batch reversal system at the child account layer of the account security system using the merchant system authentication and the transaction data in a repeated automatic looped process at the scheduled time for the plurality of refund requests, wherein the child merchant identifier is used without the parent merchant identifier to facilitate the refund payment after the merchant system authentication using the parent merchant identifier.

16. The non-transitory medium of claim 15 , wherein the refund request is associated with a plurality of transactions for the merchant system.

17. The non-transitory medium of claim 15 , wherein the refund request includes two or more of a channel identifier, a merchant number, a transaction amount, a description value, a security code, an address, and a partner code for each transaction of a plurality of transactions associated with the refund request.

18. The non-transitory medium of claim 15 , wherein the instructions cause the one or more processors to perform operations further comprising:

generating a prefill communication for a refund settlement request using the transaction data from the database in response to the refund request; and

transmitting the prefill communication to a refund settlement system.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 2, 2022
From: RAVI, VIVEKA VARDHAN; DIVECHA, TUSHAR; BERNERT, DEBORAH; SCHMIDT, JONATHAN M.; UPPALAPATI, ASHOK; YADAV, AJAY; URBANSKY, CRAIG
To: SYNCHRONY BANK
Reel/Frame 059147/0395 →
Continuity (2)
Provisional Application 63047233 · Jul 1, 2020
Related Publication 20220005034A1 · Jan 6, 2022