IP Library Granted Patent US 12,373,834
Granted Patent B2
US 12,373,834 · App. 17/176,668 · Granted Jul 29, 2025

Parallel transaction pre-authorization platform

Inventors: Wesley Perkins (Henrico, VA); Venkata Satya Sriram Kalyan Namuduri (Glen Allen, VA); David Ross (Richmond, VA); Andrew Coulson (Washington, DC); Hunter Roberts (Henrico, VA)
Assignee: Capital One Services, LLC
G06Q20/4014G06Q20/0855G06Q20/10G06Q20/3226G06Q20/4015
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 12,373,834
App. No.
17/176,668
Granted
Jul 29, 2025
Kind
B2
Abstract

Methods, systems, and apparatuses are described herein for the direct sharing and use of transaction data separately from transaction authorization processes. Transaction metadata associated with a transaction may be received and validated. Authorization information corresponding to the transaction may be received. The degree to which the transaction metadata is tested may be based on a predicted time of receipt of the authorization information. The transaction metadata and authorization information may be correlated. A computing device may determine whether to authorize the financial transaction based on the authorization information and the correlated transaction metadata. All or portions of the transaction metadata may be provided to one or more users after the transaction has been authorized or denied.

Claims (46)

1. A computer-implemented method for pre-authorizing a payment card transaction requested by a user, the method comprising:

receiving, by a computing device and from a merchant device, an indication of the payment card transaction, wherein the indication of the payment card transaction indicates that the user initiated the payment card transaction by providing payment card information to the merchant device;

receiving, by the computing device, via a first application programming interface (API), and from the merchant device, supplemental transaction metadata associated with the payment card transaction;

sending, by the computing device, a request for authorization of the payment card transaction to a user device;

based on receiving a response to the request for authorization of the payment card transaction, determining, by the computing device, whether to preauthorize the payment card transaction by testing the supplemental transaction metadata based on one or more criteria;

sending, by the computing device and to the merchant device, an indication of whether the payment card transaction is preauthorized, wherein the indication comprises at least one result from the testing of the supplemental transaction metadata based on the one or more criteria, and wherein the indication comprises instructions that, when executed by the merchant device, cause the merchant device to provide the payment card information to a payment processing service;

receiving, by the computing device, after sending the indication of whether the payment card transaction is preauthorized, via a second interface different from the first API, and from the payment processing service, payment card authorization information corresponding to the payment card transaction, wherein the payment card authorization information comprises data that indicates whether the payment processing service approved the payment card transaction; and

based on determining that the payment card transaction was preauthorized and based on the payment card authorization information, sending, by the computing device, an indication of whether the payment card transaction is authorized.

2. The method of claim 1 , wherein sending the request for authorization of the payment card transaction to the user device comprises sending, to the user device, an authorization code, and wherein the response to the request for authorization comprises the authorization code.

3. The method of claim 1 , wherein the response to the request for authorization comprises a unique credential associated with the user.

4. The method of claim 1 , wherein sending the request for authorization of the payment card transaction to the user device comprises initiating a video or voice call to the user device.

5. The method of claim 1 , wherein sending the indication of whether the payment card transaction is preauthorized comprises:

sending, to the merchant device, a likelihood that the payment card transaction will be rejected.

6. The method of claim 1 , wherein determining whether to preauthorize the payment card transaction comprises:

selecting a portion of one or more data elements of the supplemental transaction metadata to test using the one or more criteria.

7. The method of claim 1 , wherein the merchant device is configured to send the payment card information to the payment processing service in response to the indication of whether the payment card transaction is preauthorized.

8. The method of claim 1 , wherein receiving the indication of the payment card transaction comprises receiving an indication of a timestamp corresponding to the payment card transaction, and wherein determining whether to preauthorize the payment card transaction is based on determining whether the timestamp corresponds to an authorized period of time.

9. The method of claim 1 , wherein the payment card transaction is associated with a location, and wherein determining whether to preauthorize the payment card transaction is based on the location.

10. The method of claim 1 , wherein determining whether to preauthorize the payment card transaction is based on an identity of the user.

11. The method of claim 1 , wherein the payment card authorization information indicates whether the payment card information was approved by the payment processing service.

12. A data share computing device configured to pre-authorize a payment card transaction requested by a user, the data share computing device comprising:

one or more processors; and

memory storing instructions that, when executed by the one or more processors, cause the data share computing device to:

receive, from a merchant device, an indication of the payment card transaction, wherein the indication of the payment card transaction indicates that the user initiated the payment card transaction by providing payment card information to the merchant device;

receive, from the merchant device and via a first application programming interface (API), supplemental transaction metadata associated with the payment card transaction;

send a request for authorization of the payment card transaction to a user device;

based on receiving a response to the request for authorization of the payment card transaction, determine whether to preauthorize the payment card transaction by testing the supplemental transaction metadata based on one or more criteria;

send, to the merchant device, an indication of whether the payment card transaction is preauthorized, wherein the indication comprises at least one result from the testing of the supplemental transaction metadata based on the one or more criteria, and wherein the indication comprises second instructions that, when executed by the merchant device, cause the merchant device to provide, to a payment processing service, the payment card information;

receive, after sending the indication of whether the payment card transaction is preauthorized, via a second interface different from the first API, and from a payment processing service, payment card authorization information corresponding to the payment card transaction, wherein the payment card authorization information comprises data that indicates whether the payment processing service approved the payment card transaction; and

based on determining that the payment card transaction was preauthorized and based on the payment card authorization information, send an indication of whether the payment card transaction is authorized.

13. The data share computing device of claim 12 , wherein the instructions, when executed by the one or more processors, cause the data share computing device to send the request for authorization of the payment card transaction to the user device by causing the data share computing device to send, to the user device, an authorization code, and wherein the response to the request for authorization comprises the authorization code.

14. The data share computing device of claim 12 , wherein the response to the request for authorization comprises a unique credential associated with the user.

15. The data share computing device of claim 12 , wherein the instructions, when executed by the one or more processors, cause the data share computing device to send the request for authorization of the payment card transaction to the user device by initiating a video or voice call to the user device.

16. The data share computing device of claim 12 , wherein the instructions, when executed by the one or more processors, cause the data share computing device to send the indication of whether the payment card transaction is preauthorized by causing the data share computing device to:

send, to the merchant device, a likelihood that the payment card transaction will be rejected.

17. One or more non-transitory computer-readable media storing instructions that, when executed by one or more processors, cause a computing device to pre-authorize a payment card transaction requested by a user by causing the computing device to perform steps comprising:

receiving, by the computing device and from a merchant device, an indication of the payment card transaction, wherein the indication of the payment card transaction indicates that the user initiated the payment card transaction by providing payment card information to the merchant device;

receiving, by the computing device, via a first application programming interface (API), and from the merchant device, supplemental transaction metadata associated with the payment card transaction;

sending, by the computing device, a request for authorization of the payment card transaction to a user device;

based on receiving a response to the request for authorization of the payment card transaction, determining, by the computing device, whether to preauthorize the payment card transaction by testing the supplemental transaction metadata based on one or more criteria;

sending, by the computing device and to the merchant device, an indication of whether the payment card transaction is preauthorized, wherein the indication comprises at least one result from the testing of the supplemental transaction metadata based on the one or more criteria, and wherein the indication comprises second instructions that, when executed by the merchant device, cause the merchant device to provide, to a payment processing service, the payment card information;

receiving, by the computing device, after sending the indication of whether the payment card transaction is preauthorized, via a second interface different from the first API, and from a payment processing service, payment card authorization information corresponding to the payment card transaction, wherein the payment card authorization information comprises data that indicates whether the payment processing service approved the payment card transaction; and

based on determining that the payment card transaction was preauthorized and based on the payment card authorization information, sending, by the computing device, an indication of whether the payment card transaction is authorized.

18. The computer-readable media of claim 17 , wherein the instructions, when executed by the one or more processors, cause the computing device to send the request for authorization of the payment card transaction to the user device by causing the computing device to send, to the user device, an authorization code, and wherein the response to the request for authorization comprises the authorization code.

19. The computer-readable media of claim 17 , wherein the response to the request for authorization comprises a unique credential associated with the user.

20. The computer-readable media of claim 17 , wherein the instructions, when executed by the one or more processors, cause the computing device to send the request for authorization of the payment card transaction to the user device by initiating a video or voice call to the user device.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 16, 2021
From: PERKINS, WESLEY; SRIRAM KALYAN NAMUDURI, VENKATA SATYA; ROSS, DAVID; COULSON, ANDREW; ROBERTS, HUNTER
To: CAPITAL ONE SERVICES, LLC
Reel/Frame 055275/0273 →
Continuity (1)
Related Publication 20220261809A1 · Aug 18, 2022
References Cited (95)
US 6254000B1 · Degen et al. · 2001 [cited by applicant]
US 7962424B1 · Colosso et al. · 2011 [cited by applicant]
US 8352315B2 · Faith et al. · 2013 [cited by applicant]
US 8606714B1 · Cameo et al. · 2013 [cited by applicant]
US 8694347B2 · Kennis et al. · 2014 [cited by applicant]
US 8820633B2 · Bishop et al. · 2014 [cited by applicant]
US 8898762B2 · Kang · 2014 [cited by applicant]
US 9031877B1 · Santhana et al. · 2015 [cited by applicant]
US 9117230B2 · Joao · 2015 [cited by applicant]
US 9195985B2 · Domenica et al. · 2015 [cited by applicant]
US 9596237B2 · Law et al. · 2017 [cited by applicant]
US 9680946B2 · Angeles · 2017 [cited by applicant]
US 9697508B1 · Ramalingam · 2017 [cited by applicant]
US 10108963B2 · Weiner et al. · 2018 [cited by applicant]
US 10423959B2 · Douglas · 2019 [cited by examiner]
US 10482467B1 · Samitt · 2019 [cited by examiner]
US 11270311B1 · Jass · 2022 [cited by examiner]
US 11470091B2 · McCarter et al. · 2022 [cited by applicant]
US 20010051919A1 · Mason · 2001 [cited by applicant]
US 20020091634A1 · Eubanks · 2002 [cited by applicant]
US 20030023550A1 · Lee · 2003 [cited by applicant]
US 20030040990A1 · Lee et al. · 2003 [cited by applicant]
US 20030065616A1 · O'Donnell · 2003 [cited by applicant]
US 20040210531A1 · Barron et al. · 2004 [cited by applicant]
US 20050144130A1 · Staniar et al. · 2005 [cited by applicant]
US 20050283437A1 · McRae et al. · 2005 [cited by applicant]
US 20070022058A1 · Labrou · 2007 [cited by examiner]
US 20070083459A1 · Eubanks · 2007 [cited by applicant]
US 20070100745A1 · Keiser et al. · 2007 [cited by applicant]
US 20070219900A1 · MacGuire · 2007 [cited by applicant]
US 20070282674A1 · Gomes et al. · 2007 [cited by applicant]
US 20070288641A1 · Lee et al. · 2007 [cited by applicant]
US 20080263582A1 · Okamoto et al. · 2008 [cited by applicant]
US 20080270293A1 · Fortune et al. · 2008 [cited by applicant]
US 20090063276A1 · Ekechukwu · 2009 [cited by applicant]
US 20090106151A1 · Nelsen et al. · 2009 [cited by applicant]
US 20090222369A1 · Zoldi et al. · 2009 [cited by applicant]
US 20110022517A1 · Hammad · 2011 [cited by applicant]
US 20110066493A1 · Faith et al. · 2011 [cited by applicant]
US 20110302011A1 · Yoder et al. · 2011 [cited by applicant]
US 20120221468A1 · Kumnick et al. · 2012 [cited by applicant]
US 20120239574A1 · Smith et al. · 2012 [cited by applicant]
US 20130024339A1 · Choudhuri et al. · 2013 [cited by applicant]
US 20130124417A1 · Spears et al. · 2013 [cited by applicant]
US 20130232069A1 · Leyva et al. · 2013 [cited by applicant]
US 20140046846A1 · Dogin · 2014 [cited by examiner]
US 20140074675A1 · Calman et al. · 2014 [cited by applicant]
US 20140188728A1 · Dheer et al. · 2014 [cited by applicant]
US 20140258118A1 · Scott et al. · 2014 [cited by applicant]
US 20140258119A1 · Canis et al. · 2014 [cited by applicant]
US 20150073981A1 · Adjaoute · 2015 [cited by applicant]
US 20150081462A1 · Ozvat et al. · 2015 [cited by applicant]
US 20150170148A1 · Priebatsch · 2015 [cited by applicant]
US 20150302464A1 · Iannace et al. · 2015 [cited by applicant]
US 20150332237A1 · Aaron et al. · 2015 [cited by applicant]
US 20150348167A1 · McDermott · 2015 [cited by applicant]
US 20150379514A1 · Poole · 2015 [cited by examiner]
US 20160034932A1 · Sion et al. · 2016 [cited by applicant]
US 20160086185A1 · Adjaoute · 2016 [cited by applicant]
US 20160180466A1 · Caldwell · 2016 [cited by applicant]
US 20160328710A1 · Britton et al. · 2016 [cited by applicant]
US 20180096350A1 · Groarke et al. · 2018 [cited by applicant]
US 20180158044A1 · Beck · 2018 [cited by examiner]
US 20180218345A1 · Spratt · 2018 [cited by examiner]
US 20180374152A1 · Dominguez · 2018 [cited by applicant]
US 20190188579A1 · Manoharan et al. · 2019 [cited by applicant]
US 20190370812A1 · Kandasamy et al. · 2019 [cited by applicant]
US 20190392440A1 · Ederle et al. · 2019 [cited by applicant]
US 20200058030A1 · Adjaoute · 2020 [cited by applicant]
US 20200104843A1 · Bhasin · 2020 [cited by applicant]
US 20200134628A1 · Jia et al. · 2020 [cited by applicant]
US 20200160286A1 · Vukich et al. · 2020 [cited by applicant]
US 20200193438A1 · Cohn et al. · 2020 [cited by applicant]
US 20200211020A1 · Allbright et al. · 2020 [cited by applicant]
US 20200311734A1 · Mardikar et al. · 2020 [cited by applicant]
US 20200322350A1 · McCarter et al. · 2020 [cited by applicant]
US 20200334679A1 · Sandepudi et al. · 2020 [cited by applicant]
US 20200356980A1 · Singh · 2020 [cited by examiner]
US 20200372509A1 · Phalnikar · 2020 [cited by applicant]
US 20200380523A1 · Agrawal et al. · 2020 [cited by applicant]
US 20220027915A1 · Cameron · 2022 [cited by examiner]
US 20230289808A1 · Kolchin · 2023 [cited by applicant]
CN 108566641A · 2018 [cited by applicant]
WO 2005077066A2 · 2005 [cited by applicant]
WO 2005101713A2 · 2005 [cited by applicant]
WO 2018035024A1 · 2018 [cited by applicant]
WO 2019137050A1 · 2019 [cited by applicant]
Apr. 1, 2021—(US) Non-Final Office Action—U.S. Appl. No. 17/176,642. [cited by applicant]
Hsu et al., “An Online Fraud-Resistant Technology for Credit Card E-Transactions,” Kao Yuan University, Dept. of Engineering, 2009 (Year: 2009). [cited by applicant]
Rimpal R. Popat, “A Survey on Credit Card Fraud Detection using Machine Learning,” 2nd International Conference on Trends in Electronics and Informatics, IEEE Conference, 2018 (Year: 2018). [cited by applicant]
Jul. 22, 2021—Notice of Allowance—U.S. Appl. No. 17/176,642. [cited by applicant]
Apr. 29, 2022—(WO) International Search Report & Written Opinion—App. No. PCT/US2022/016485. [cited by applicant]
Mar. 1, 2017, J. Brindtha, K.R. Hithaeishini, R. Komala, G. Abirami, U. Aru, Identification and Detecting of Attacker in a Purchase Portal Using Honeywords, IEEE, Web 389-393. [cited by applicant]
Jun. 18, 2024—(EP) Exam Report—App No. 22706488.8. [cited by applicant]
Pavithra, “Credit Card Processing and Payment Systems” International Journal of Modern Engineering Research, 2249-6645, vol. 7, Issue 2, 2017. [cited by applicant]