IP Library › Granted Patent US 12,572,936
Granted Patent B2
US 12,572,936 · App. 18/644,939 · Granted Mar 10, 2026

QR code payor tracking and repeat payment prevention

Inventors: Jacqueline Nicole Tero (Brooklyn, NY); Keegan Franklin (Tucson, AZ); Patrick Babcock (Boston, MA)
Assignee: Capital One Services, LLC
G06Q20/401G06Q20/227G06Q20/3223G06Q20/3276G06Q20/389
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,572,936
App. No.
18/644,939
Granted
Mar 10, 2026
Kind
B2
Abstract

A computer implemented method, system, and non-transitory computer-readable device usable in a mobile transaction environment. A customer scans a purchasing code (e.g., a quick-response (QR) code) using, for example, a mobile device. The QR code is encoded with a payment configuration ID and a merchant account token associated with bank account information for the merchant. Historical purchases for the customer, are analyzed in real time to alert a customer of potential duplicate purchases through a UI on the mobile device. The user may complete or cancel the current transaction by interacting with the UI.

Claims (67)

1 . A computer-implemented method comprising:

receiving, by one or more computing devices and from a mobile device payment app, a purchase request for a product comprising a payment configuration ID and a device ID, wherein the purchase request is initiated by a customer scanning a purchasing code using the mobile device and wherein the purchasing code is encoded with the payment configuration ID and a merchant account token associated with bank account information for the merchant,

tracking a corresponding purchase, wherein the purchase request by the mobile device payment app originates outside a payment system of the merchant, the tracking comprising:

retrieving, from a database and based on the device ID, historical purchases for the customer, wherein the historical purchases comprise purchase information for one or more purchases and wherein the one or more purchases include a purchase request time within a predetermined time period threshold;

determining, based on a comparison of the payment configuration ID of the purchase request and purchase configuration IDs corresponding to the historical purchases, that the purchase request may be a repeat purchase request, wherein the repeat purchase request is based on the customer rescanning the purchasing code within the predetermined time period threshold; and

sending, to the mobile device, a warning message prompting the customer to confirm that the purchase request is not a repeat purchase request, wherein:

the warning message is displayed via a user interface (UI) on the mobile device;

the UI includes a confirmation button and a cancel button that, when selected, voids the purchase request.

2 . The computer-implemented method of claim 1 , wherein selection of the confirmation button causes the mobile device to send an updated purchase request to one or more computing devices, wherein the updated purchase request includes a repeat request status indicating that the updated purchase request is not a repeat request.

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

receiving, from the mobile device, the updated purchase request;

storing, in the database, purchase information comprising a purchase request time, the payment configuration ID, and the device ID;

sending, to the mobile device, product information for the product based on the payment configuration ID;

receiving, from a payment platform, a payment confirmation indicating that a purchase payment has been successfully completed by the customer, wherein the payment confirmation comprises a platform identifier identifying the payment platform and transaction data for the purchase, including the payment configuration ID, the device ID, and a customer token for the customer; and

sending, to the payment platform, receipt data for the purchase generated based on the transaction data and a receipt code that encodes the receipt data.

4 . The computer-implemented method of claim 3 , wherein the payment platform is a digital payment platform and wherein the payment platform is selected by the customer from a plurality of payment platforms.

5 . The computer-implemented method of claim 4 , wherein selection of the payment platform causes the mobile device to launch the mobile device payment app corresponding to the payment platform.

6 . The computer-implemented method of claim 3 , wherein the payment confirmation further comprises contact information for the customer.

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

retrieving purchase data from the database, wherein the purchase data includes transaction details, device IDs, and customer tokens;

analyzing the retrieved purchase data to identify unique customers, based on device IDs and customer tokens associated with the purchase data; and

aggregating purchase history for identified customers to generate customer behavior profiles.

8 . The computer-implemented method of claim 7 , wherein the customer behavior profiles are utilized to derive insights into one or more of purchasing patterns, preferences, and demographic trends associated with the unique customers.

9 . The computer-implemented method of claim 7 , wherein a machine learning algorithm is utilized to process the purchase data, wherein the machine learning algorithms are configured to learn from the aggregated purchase histories, customer behaviors, and preferences to improve identification of unique customers.

10 . A system, comprising:

a memory; and

at least one processor coupled to the memory and configured to:

receive, from a mobile device payment app, a purchase request for a product comprising a payment configuration ID and a device ID, wherein the purchase request is initiated by a customer scanning a purchasing code using the mobile device and wherein the purchasing code is encoded with the payment configuration ID and a merchant account token associated with bank account information for the merchant;

track a corresponding purchase, wherein the purchase request by the mobile device payment app originates outside a payment system of the merchant, the tracking comprising:

retrieve, from a database and based on the device ID, historical purchases for the customer, wherein the historical purchases comprise purchase information for one or more purchases and wherein the one or more purchases include a purchase request time within a predetermined time period threshold;

determine, based on a comparison of the payment configuration ID of the purchase request and purchase configuration IDs corresponding to the historical purchases, that the purchase request may be a repeat purchase request, wherein the repeat purchase request is based on the customer rescanning the purchasing code within the predetermined time period threshold; and

send, to the mobile device, a warning message prompting the customer to confirm that the purchase request is not a repeat purchase request, wherein:

the warning message is displayed via a user interface (UI) on the mobile device;

the UI includes a confirmation button and a cancel button that, when selected, voids the purchase request.

11 . The system of claim 10 , wherein selection of the confirmation button causes the mobile device to send an updated purchase request to one or more computing devices, wherein the updated purchase request includes a repeat request status indicating that the updated purchase request is not a repeat request.

12 . The system of claim 11 , wherein the at least one processor is further configured to:

receive, from the mobile device, the updated purchase request;

store, in the database, purchase information comprising a purchase request time, the payment configuration ID, and the device ID;

send, to the mobile device, product information for the product based on the payment configuration ID;

receive, from a payment platform, a payment confirmation indicating that a purchase payment has been successfully completed by the customer, wherein the payment confirmation comprises a platform identifier identifying the payment platform and transaction data for the purchase, including the payment configuration ID, the device ID, and a customer token for the customer; and

send, to the payment platform, receipt data for the purchase generated based on the transaction data and a receipt code that encodes the receipt data.

13 . The system of claim 12 , wherein the at least one processor is further configured to:

retrieve purchase data from the database, wherein the purchase data includes transaction details, device IDs, and customer tokens;

analyze the retrieved purchase data to identify unique customers, based on device IDs and customer tokens associated with the purchase data; and

aggregate purchase history for identified customers to generate customer behavior profiles.

14 . The system of claim 13 , wherein the customer behavior profiles are utilized to derive insights into one or more of purchasing patterns, preferences, and demographic trends associated with the unique customers.

15 . The system method of claim 13 , wherein a machine learning algorithm is utilized to process the purchase data, wherein the machine learning algorithms are configured to learn from the aggregated purchase histories, customer behaviors, and preferences to improve identification of unique customers.

16 . A non-transitory computer-readable device having instructions stored thereon that, when executed by at least one computing device, cause the at least one computing device to perform operations comprising:

receiving, from a mobile device payment app, a purchase request for a product comprising a payment configuration ID and a device ID, wherein the purchase request is initiated by a customer scanning a purchasing code using the mobile device and wherein the purchasing code is encoded with the payment configuration ID and a merchant account token associated with bank account information for the merchant;

tracking a corresponding purchase, wherein the purchase request by the mobile device payment app originates outside a payment system of the merchant, the tracking comprising:

retrieving, from a database and based on the device ID, historical purchases for the customer, wherein the historical purchases comprise purchase information for one or more purchases and wherein the one or more purchases include a purchase request time within a predetermined time period threshold;

determining, based on a comparison of the payment configuration ID of the purchase request and purchase configuration IDs corresponding to the historical purchases, that the purchase request may be a repeat purchase request, wherein the repeat purchase request is based on the customer rescanning the purchasing code within the predetermined time period threshold; and

sending, to the mobile device, a warning message prompting the customer to confirm that the purchase request is not a repeat purchase request, wherein:

the warning message is displayed via a user interface (UI) on the mobile device;

the UI includes a confirmation button and a cancel button that, when selected, voids the purchase request.

17 . The non-transitory computer-readable device of claim 16 , wherein selection of the confirmation button causes the mobile device to send an updated purchase request to one or more computing devices, wherein the updated purchase request includes a repeat request status indicating that the updated purchase request is not a repeat request.

18 . The non-transitory computer-readable device of claim 17 , the operations further comprising:

receiving, from the mobile device, the updated purchase request;

storing, in the database, purchase information comprising a purchase request time, the payment configuration ID, and the device ID;

sending, to the mobile device, product information for the product based on the payment configuration ID;

receiving, from a payment platform, a payment confirmation indicating that a purchase payment has been successfully completed by the customer, wherein the payment confirmation comprises a platform identifier identifying the payment platform and transaction data for the purchase, including the payment configuration ID, the device ID, and a customer token for the customer; and

sending, to the payment platform, receipt data for the purchase generated based on the transaction data and a receipt code that encodes the receipt data.

19 . The non-transitory computer-readable device of claim 18 , the operations further comprising:

retrieving purchase data from the database, wherein the purchase data includes transaction details, device IDs, and customer tokens;

analyzing the retrieved purchase data to identify unique customers, based on device IDs and customer tokens associated with the purchase data; and

aggregating purchase history for identified customers to generate customer behavior profiles.

20 . The non-transitory computer-readable device of claim 19 , wherein a machine learning algorithm is utilized to process the purchase data, wherein the machine learning algorithms are configured to learn from the aggregated purchase histories, customer behaviors, and preferences to improve identification of unique customers.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 25, 2024
From: TERO, JACQUELINE NICOLE; FRANKLIN, KEEGAN; BABCOCK, PATRICK
To: CAPITAL ONE SERVICES, LLC
Reel/Frame 067219/0969 →
Continuity (1)
Related Publication 20250335911A1 · Oct 30, 2025
References Cited (179)
US 5515451A · Tsuji et al. · 1996 [cited by applicant]
US 7391934B2 · Goodall et al. · 2008 [cited by applicant]
US 7421107B2 · Lugg · 2008 [cited by applicant]
US 7526117B2 · Foth et al. · 2009 [cited by applicant]
US 7587066B2 · Cordery et al. · 2009 [cited by applicant]
US 7698222B1 · Bueche · 2010 [cited by applicant]
US 7702588B2 · Gilder et al. · 2010 [cited by applicant]
US 7734545B1 · Fogliano et al. · 2010 [cited by applicant]
US 7818307B1 · Young et al. · 2010 [cited by applicant]
US 7856402B1 · Kay · 2010 [cited by applicant]
US 7905396B2 · Tidwell et al. · 2011 [cited by applicant]
US 7949587B1 · Morris et al. · 2011 [cited by applicant]
US 8027928B1 · Hecht, Jr. et al. · 2011 [cited by applicant]
US 8050997B1 · Nosek et al. · 2011 [cited by applicant]
US 8060442B1 · Hecht et al. · 2011 [cited by applicant]
US 8104676B2 · Ramachandran · 2012 [cited by applicant]
US 8213782B2 · Jelinek · 2012 [cited by applicant]
US 8271381B2 · O'Brien et al. · 2012 [cited by applicant]
US 8290876B1 · Powell · 2012 [cited by applicant]
US 8296230B2 · Davis et al. · 2012 [cited by applicant]
US 8300917B2 · Borgia et al. · 2012 [cited by applicant]
US 8332329B1 · Thiele · 2012 [cited by applicant]
US 8381969B1 · Miller · 2013 [cited by examiner]
US 8406500B2 · Najari et al. · 2013 [cited by applicant]
US 8464933B1 · Prasad et al. · 2013 [cited by applicant]
US 8582862B2 · Nepomniachtchi et al. · 2013 [cited by applicant]
US 8605982B2 · Jackson et al. · 2013 [cited by applicant]
US 8626661B2 · Gilder · 2014 [cited by applicant]
US 8632001B1 · Ramachandran et al. · 2014 [cited by applicant]
US 8638363B2 · King et al. · 2014 [cited by applicant]
US 8639105B2 · Ogino · 2014 [cited by applicant]
US 8708227B1 · Oakes, III et al. · 2014 [cited by applicant]
US 8745073B2 · Mulligan et al. · 2014 [cited by applicant]
US 8811711B2 · Calman et al. · 2014 [cited by applicant]
US 8885963B2 · Coleman · 2014 [cited by applicant]
US 8958605B2 · Amtrup et al. · 2015 [cited by applicant]
US 8959033B1 · Oakes, III et al. · 2015 [cited by applicant]
US 8983170B2 · Nepomniachtchi et al. · 2015 [cited by applicant]
US 8995012B2 · Heit et al. · 2015 [cited by applicant]
US 9064248B2 · Huff et al. · 2015 [cited by applicant]
US 9092447B1 · Anderson · 2015 [cited by examiner]
US 9324073B2 · Nepomniachtchi et al. · 2016 [cited by applicant]
US 9384392B2 · Weber et al. · 2016 [cited by applicant]
US 9483761B2 · Brendell et al. · 2016 [cited by applicant]
US 9558493B2 · Carrott · 2017 [cited by applicant]
US 9569756B1 · Bueche, Jr. et al. · 2017 [cited by applicant]
US 9640041B2 · Block et al. · 2017 [cited by applicant]
US 9652690B2 · Eid et al. · 2017 [cited by applicant]
US 9672510B2 · Roach et al. · 2017 [cited by applicant]
US 9679281B2 · Moshal · 2017 [cited by applicant]
US 9684920B2 · Kalgi et al. · 2017 [cited by applicant]
US 9721177B2 · Lee et al. · 2017 [cited by applicant]
US 9747509B2 · Eid et al. · 2017 [cited by applicant]
US 9779392B1 · Prasad et al. · 2017 [cited by applicant]
US 9807263B2 · Bala et al. · 2017 [cited by applicant]
US 9852406B2 · Doyle et al. · 2017 [cited by applicant]
US 9852409B2 · Artman et al. · 2017 [cited by applicant]
US 10026119B2 · Green et al. · 2018 [cited by applicant]
US 10192108B2 · Nepomniachtchi et al. · 2019 [cited by applicant]
US 10210522B1 · Medina, III et al. · 2019 [cited by applicant]
US 10217375B2 · Waldron et al. · 2019 [cited by applicant]
US 10402790B1 · Clark et al. · 2019 [cited by applicant]
US 10460381B1 · Pollack et al. · 2019 [cited by applicant]
US 10504185B1 · Buentello · 2019 [cited by applicant]
US 10552810B1 · Ethington et al. · 2020 [cited by applicant]
US 10635898B1 · Pribble et al. · 2020 [cited by applicant]
US 10692230B2 · Anderson et al. · 2020 [cited by applicant]
US 10699146B2 · Shustorovich et al. · 2020 [cited by applicant]
US 10706466B1 · Ethington et al. · 2020 [cited by applicant]
US 10762502B1 · Yoshida · 2020 [cited by examiner]
US 10762579B2 · Riechers et al. · 2020 [cited by applicant]
US 10769598B1 · Oakes, III et al. · 2020 [cited by applicant]
US 10789496B2 · Kotovich et al. · 2020 [cited by applicant]
US 10853771B2 · Enobakhare · 2020 [cited by applicant]
US 10855914B1 · Prasad et al. · 2020 [cited by applicant]
US 10909362B2 · Nepomniachtchi et al. · 2021 [cited by applicant]
US 11064111B1 · Prasad et al. · 2021 [cited by applicant]
US 11068867B1 · Tucker · 2021 [cited by applicant]
US 11126975B2 · Haldenby et al. · 2021 [cited by applicant]
US 11127008B1 · Buentello et al. · 2021 [cited by applicant]
US 11145169B2 · Pratten et al. · 2021 [cited by applicant]
US 11157731B2 · Nepomniachtchi et al. · 2021 [cited by applicant]
US 11159733B2 · Mukul · 2021 [cited by applicant]
US 11200550B1 · Singfield · 2021 [cited by applicant]
US 11210379B1 · Lindley et al. · 2021 [cited by applicant]
US 11216884B1 · Buentello · 2022 [cited by applicant]
US 11222313B2 · Doyle et al. · 2022 [cited by applicant]
US 11244302B2 · Ekpenyong et al. · 2022 [cited by applicant]
US 11244319B2 · Navarro et al. · 2022 [cited by applicant]
US 11282086B1 · Medina, III et al. · 2022 [cited by applicant]
US 11288661B2 · Hammad et al. · 2022 [cited by applicant]
US 11295377B1 · Ethington et al. · 2022 [cited by applicant]
US 11295378B1 · Voutour et al. · 2022 [cited by applicant]
US 11315217B2 · Ilic et al. · 2022 [cited by applicant]
US 11321709B1 · Kolchin · 2022 [cited by applicant]
US 11373150B1 · Bueche, Jr. et al. · 2022 [cited by applicant]
US 11449841B1 · Srinivasarangan et al. · 2022 [cited by applicant]
US 11516383B2 · Ilic et al. · 2022 [cited by applicant]
US 11531973B1 · Prasad et al. · 2022 [cited by applicant]
US 11539848B2 · Roach et al. · 2022 [cited by applicant]
US 11562332B1 · Oakes, III et al. · 2023 [cited by applicant]
US 11610294B2 · Dewitt et al. · 2023 [cited by applicant]
US 11640627B2 · Fotso et al. · 2023 [cited by applicant]
US 11676285B1 · Backlund et al. · 2023 [cited by applicant]
US 11682222B1 · Oakes, III et al. · 2023 [cited by applicant]
US 11694268B1 · Buentello · 2023 [cited by applicant]
US 11704627B2 · Gordon et al. · 2023 [cited by applicant]
US 11710210B1 · Medina, III · 2023 [cited by applicant]
US 11798253B2 · Pribble et al. · 2023 [cited by applicant]
US 11810382B2 · Laza et al. · 2023 [cited by applicant]
US 11829962B2 · Burnam et al. · 2023 [cited by applicant]
US 11900755B1 · Bueche, Jr. · 2024 [cited by applicant]
US 20050283444A1 · Ekberg · 2005 [cited by applicant]
US 20060036537A1 · Lawrence et al. · 2006 [cited by applicant]
US 20080140579A1 · Agarwal · 2008 [cited by applicant]
US 20090171839A1 · Rosano et al. · 2009 [cited by applicant]
US 20120040717A1 · Levy et al. · 2012 [cited by applicant]
US 20130013491A1 · Selway et al. · 2013 [cited by applicant]
US 20130054461A1 · Gupta et al. · 2013 [cited by applicant]
US 20130176473A1 · Ogino · 2013 [cited by applicant]
US 20130198069A1 · Latimer · 2013 [cited by applicant]
US 20130204783A1 · Klose et al. · 2013 [cited by applicant]
US 20140006224A1 · Grigg et al. · 2014 [cited by applicant]
US 20140074697A1 · Foster · 2014 [cited by applicant]
US 20140114852A1 · Rajagopal et al. · 2014 [cited by applicant]
US 20140122332A1 · Viera et al. · 2014 [cited by applicant]
US 20140236767A1 · Duggal et al. · 2014 [cited by applicant]
US 20150032626A1 · Dill et al. · 2015 [cited by applicant]
US 20150120564A1 · Smith et al. · 2015 [cited by applicant]
US 20170270508A1 · Roach et al. · 2017 [cited by applicant]
US 20170309108A1 · Sadovsky et al. · 2017 [cited by applicant]
US 20170336511A1 · Nerurkar · 2017 [cited by applicant]
US 20180103112A1 · Jones-McFadden · 2018 [cited by examiner]
US 20180260806A1 · Bhuma · 2018 [cited by examiner]
US 20190066089A1 · Miryala · 2019 [cited by examiner]
US 20200042955A1 · Widdows · 2020 [cited by applicant]
US 20200334647A1 · Malhotra et al. · 2020 [cited by applicant]
US 20200389600A1 · Capurso et al. · 2020 [cited by applicant]
US 20210035086A1 · Khan et al. · 2021 [cited by applicant]
US 20210174361A1 · Potireddy et al. · 2021 [cited by applicant]
US 20210360149A1 · Mukul · 2021 [cited by applicant]
US 20220245985A1 · Bhutani et al. · 2022 [cited by applicant]
US 20220277291A1 · Roongta et al. · 2022 [cited by applicant]
US 20220335393A1 · Gupta et al. · 2022 [cited by applicant]
US 20220343301A1 · Edwards et al. · 2022 [cited by applicant]
US 20220343398A1 · Han · 2022 [cited by applicant]
US 20220358575A1 · Smith · 2022 [cited by applicant]
US 20230060395A1 · Roach et al. · 2023 [cited by applicant]
US 20230060464A1 · Ceesay · 2023 [cited by applicant]
US 20230084370A1 · Bradford · 2023 [cited by applicant]
US 20230113752A1 · Jorlett · 2023 [cited by examiner]
US 20230120865A1 · Nascimento et al. · 2023 [cited by applicant]
US 20230133158A1 · Kolchin · 2023 [cited by applicant]
US 20230196319A1 · Ng et al. · 2023 [cited by applicant]
US 20230196706A1 · Scott · 2023 [cited by applicant]
US 20230209116A1 · Leung et al. · 2023 [cited by applicant]
US 20230281629A1 · Shevyrev et al. · 2023 [cited by applicant]
US 20230289808A1 · Kolchin · 2023 [cited by applicant]
US 20230351782A1 · Fitzgerald · 2023 [cited by applicant]
US 20240193612A1 · Roberts · 2024 [cited by examiner]
US 20250045767A1 · Ammatanda · 2025 [cited by examiner]
JP 2020021419A · 2020 [cited by applicant]
KR 2570769B1 · 2023 [cited by applicant]
WO 2023091068A1 · 2023 [cited by applicant]
Rose, Lydia M. “Modernizing check fraud detection with machine learning.” PhD dissertation. Utica College. 2018. [cited by applicant]
remotedepositcapture.com, “Ensenta Business Mobile with Multi-Check”, Available from the Internet at https://www.remotedepositcapture.com/RDC/media/RDC-Forum/Submitted-Sponsor-Brochures/EnsentaBusinessMobileMultiCheck-e… [cited by applicant]
Bills, Steve, “Automated Amount Scanning Is Trend in Remote-Deposit,” American Banker, New York, NY, Aug. 30, 2005, (4 pgs). [cited by applicant]
Dunga et al. “Electronic Booking and Payment Platforms for Inter-Campus E-Bikes”. Engineering Proceedings. Jul. 14, 2023. pp. 1-14. vol. 41, Issue 12. [cited by applicant]
Aletihadpayments. “Aani | Split the bill with your friends”. Oct. 16, 2023. Located via YouTube, free copy available at https://www.youtube.com/watch?v=_ wys 12-0KmE. [cited by applicant]
Katariya. “Mastering QR Code Payments: A Guide to Seamless and Effortless Transactions”. Jun. 12, 2023. Located via Google Web, free copy available at https://www.mooninvoice.com/blog/qr-code-payments/. [cited by applicant]
PayBy. “PayBy: Easily Split Bills of Group Expenses”. Retrieved from the Internet on Dec. 21, 2023. Located via Google Web, free copy available at https://www.payby.com/split-bills. [cited by applicant]
Natwest. “Request money from someone or split a bill”. Retrieved from the Internet on Dec. 21, 2023. Located via Google Web, free copy available at https://www.natwest.com/waystopay/payme.html. [cited by applicant]
Spoton. “QR Scan & Pay / Order & Pay | SpotOn Order”. Jul. 19, 2023. Located via Google Web, free copy available at https://help.spoton.com/space/SK/2457829381/QR+Scan+%26+Pay+%2F+Order+%26+Pay+%7C+SpotOn+Order. [cited by applicant]
Spoton. “QR Split Payment | SpotOn Order”. Jul. 19, 2023. Located via Google Web, free copy available at https://help.spoton.com/space/SK/2262565040/QR+Split+Payment+%7C+SpotOn+Order. [cited by applicant]
photo.stackexchange.com, “What of those EXIF values tell me more about my image's quality?” Jul. 8, 2017, Photography Stack Exchange, Located via Google Web, available at https://photo.stackexchange.com/questions/90730/… [cited by applicant]
Abraham, “MoiréPattern Detection using Wavelet Decomposition and Convolutional Neural Network,” Amadeus Software Labs Pvt. Ltd, IEEE (2018). [cited by applicant]
Yang, et al., “Doing More with Moire Pattern Detection in Digital Photos,” Journal of Latex Class Files, vol. 14, No. 8 (Aug. 2021). [cited by applicant]
Digital Check, “Money Orders Giving You Trouble? We've Got The Solution!” Oct. 1, 2008. Located via Google Web, available at https://www.digitalcheck.com/moneyorders-dcom/. [cited by applicant]
International Search Report and Written Opinion for International Application No. PCT/US2025/025611, mailed on Jul. 24, 2025, 13 pages. [cited by applicant]