IP Library Granted Patent US 12,243,038
Granted Patent B2
US 12,243,038 · App. 18/470,371 · Granted Mar 4, 2025

Smart card NFC secure money transfer

Inventors: Tyler Locke (Washington, DC); Kevin Kelly (Austin, TX); David Wurmfeld (Fairfax, VA)
Assignee: CAPITAL ONE SERVICES, LLC
G06Q20/204G06F21/34G06Q20/20G06Q20/3221G06Q20/3223G06Q20/3226G06Q20/3278G06Q20/341G06Q20/346G06Q20/352G06Q20/382G06Q30/06G07F7/084G07F7/0846G07F7/0866G07F7/1008H04B5/72
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,243,038
App. No.
18/470,371
Granted
Mar 4, 2025
Kind
B2
Abstract

A secure method of real time money transferring between account holders utilizes Near Field Communication (NFC) technologies, dynamic transaction cards, and a mobile application to facilitate a seamless mobile transfer of funds. The dynamic transaction card of the customer requesting to make the transfer of funds may be placed in contact with the second recipient dynamic transaction card of the customer receiving the funds transfer to establish an NFC connection. The dynamic transaction card requesting the transfer may receive, via the NFC antenna on the card, the recipient customer account information stored on a passive NFC tag. The dynamic transaction card requesting the transfer may transmit the recipient account information to a mobile application, which may transmit the recipient account information to an account provider system for facilitating the funds transfer.

Claims (40)

1. A user device, comprising:

one or more processors; and

a memory in communication with the one or more processors and storing instructions that, when executed by the one or more processors, are configured to cause the user device to:

receive a request to transfer funds from a first account associated with a first dynamic transaction card to a second recipient account associated with a second recipient dynamic transaction card;

transmit, via a short-range wireless communication network protocol, the request to the first dynamic transaction card;

receive second recipient account information associated with the second recipient dynamic transaction card;

retrieve a private key from the first dynamic transaction card;

encrypt the second recipient account information using the private key to create a second recipient account information token; and

transmit the second recipient account information token to an account provider system over a wireless communication protocol to facilitate the transfer of the funds from the first account to the second recipient account when the second recipient account information token has not expired.

2. The user device of claim 1 , wherein the user device comprises a mobile device.

3. The user device of claim 1 , wherein the short-range wireless communication network comprises a Bluetooth™ or Bluetooth™ Low Energy (BLE) network.

4. The user device of claim 1 , wherein encrypting the second recipient account information uses at least one encryption technique of a cryptographic key, a hash algorithm, a digital signature, and a checksum.

5. The user device of claim 1 , wherein the account provider system is further configured to receive a message notifying the account provider system that a funds transfer has occurred from the first account to the second recipient account.

6. The user device of claim 5 , wherein the account provider system is further configured to update an account balance of the first account based on the message.

7. The user device of claim 1 , wherein a destination application programming interface (API) is configured to provide a confirmation to the account provider system that a funds transfer has been completed between the first account and the second recipient account.

8. The user device of claim 1 , wherein the encryption is conducted via an application programming interface (API).

9. The user device of claim 1 , wherein the request is received via a secure mobile application.

10. The user device of claim 9 , wherein the second recipient account information token is transmitted to the account provider system via the secure mobile application.

11. A method, comprising:

receiving a request to transfer funds from a first account associated with a first dynamic transaction card to a second recipient account associated with a second recipient dynamic transaction card;

transmitting, via a short-range wireless communication network protocol, the request to the first dynamic transaction card;

receiving second recipient account information associated with the second recipient dynamic transaction card;

retrieving a private key from the first dynamic transaction card;

encrypting the second recipient account information using the private key to create a second recipient account information token; and

transmitting the second recipient account information token to an account provider system over a wireless communication network protocol to facilitate the transfer of the funds from the first account to the second recipient account when the second recipient account information token has not expired.

12. The method of claim 11 , wherein the short-range wireless communication network comprises a Bluetooth™ or Bluetooth™ Low Energy (BLE) network.

13. The method of claim 11 , wherein encrypting the second recipient account information uses at least one encryption technique of a cryptographic key, a hash algorithm, a digital signature, and a checksum.

14. The method of claim 11 , wherein the account provider system is further configured to receive a message notifying the account provider system that a funds transfer has occurred from the first account to the second recipient account.

15. The method of claim 14 , wherein the account provider system is further configured to update an account balance of the first account based on the message.

16. The method of claim 11 , wherein a destination application programming interface (API) is configured to provide a confirmation to the account provider system that a funds transfer has been completed between the first account and the second recipient account.

17. A method comprising:

receiving request to transfer funds from a first account associated with a first dynamic transaction card to a second recipient account associated with a second recipient dynamic transaction card;

transmitting, via a short-range wireless communication network protocol, the request to the first dynamic transaction card;

receiving second recipient account information associated with the second recipient dynamic transaction card;

retrieving a private key from the first dynamic transaction card;

encrypting the second recipient account information using the private key to create a second recipient account information token; and

transmitting the second recipient account information token to an account provider system to facilitate the transfer of the funds from the first account to the second recipient account.

18. The method of claim 17 , wherein the account provider system is further configured to receive a message notifying the account provider system that a funds transfer has occurred from the first account to the second recipient account.

19. The method of claim 18 , wherein the account provider system is further configured to update an account balance of the first account based on the message.

20. The method of claim 17 , wherein a destination application programming interface (API) is configured to provide a confirmation to the account provider system that a funds transfer has been completed between the first account and the second recipient account.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 19, 2023
From: LOCKE, TYLER; KELLY, KEVIN; WURMFELD, DAVID
To: CAPITAL ONE SERVICES, LLC
Reel/Frame 064960/0481 →
Continuity (5)
Continuation 17402687 · Aug 16, 2021
Continuation 16450350 · Jun 24, 2019
Continuation 15663083 · Jul 28, 2017
Provisional Application 62440132 · Dec 29, 2016
Related Publication 20240029043A1 · Jan 25, 2024
References Cited (77)
US 7540408B2 · Levine et al. · 2009 [cited by applicant]
US 7885870B2 · Nam et al. · 2011 [cited by applicant]
US 8504450B2 · Shastry · 2013 [cited by applicant]
US 8510220B2 · Rackley, III et al. · 2013 [cited by applicant]
US 8612317B1 · Harman et al. · 2013 [cited by applicant]
US 8615445B2 · Dorsey et al. · 2013 [cited by applicant]
US 8630947B1 · Freund · 2014 [cited by applicant]
US 8694425B2 · O'Leary et al. · 2014 [cited by applicant]
US 8751314B2 · Fisher · 2014 [cited by applicant]
US 8762211B2 · Killian et al. · 2014 [cited by applicant]
US 8788418B2 · Spodak et al. · 2014 [cited by applicant]
US 8805379B2 · Brown et al. · 2014 [cited by applicant]
US 8805725B2 · Calman · 2014 [cited by applicant]
US 8805726B2 · Fisher · 2014 [cited by applicant]
US 8813182B2 · Griffin et al. · 2014 [cited by applicant]
US 8903737B2 · Cameron et al. · 2014 [cited by applicant]
US 8909553B2 · Abifaker · 2014 [cited by applicant]
US 8978975B2 · Barnett · 2015 [cited by applicant]
US 9009081B2 · Fisher · 2015 [cited by applicant]
US 9026459B2 · Fisher · 2015 [cited by applicant]
US 9105025B2 · Poole et al. · 2015 [cited by applicant]
US 9909879B2 · VonDerheide · 2018 [cited by examiner]
US 10664839B2 · Modi et al. · 2020 [cited by applicant]
US 11055692B1 · Bodalia · 2021 [cited by examiner]
US 11605078B1 · Adam · 2023 [cited by examiner]
US 11829999B2 · Collinge · 2023 [cited by examiner]
US 20040098350A1 · Labrou et al. · 2004 [cited by applicant]
US 20070295803A1 · Levine et al. · 2007 [cited by applicant]
US 20090143104A1 · Loh et al. · 2009 [cited by applicant]
US 20090164381A1 · Brown · 2009 [cited by examiner]
US 20090191811A1 · Griffin et al. · 2009 [cited by applicant]
US 20090192937A1 · Griffin et al. · 2009 [cited by applicant]
US 20110022424A1 · VonDerheide · 2011 [cited by applicant]
US 20110060684A1 · Jucht et al. · 2011 [cited by applicant]
US 20110178903A1 · Adams et al. · 2011 [cited by applicant]
US 20110238553A1 · Raj et al. · 2011 [cited by applicant]
US 20120031545A1 · Vaccaro et al. · 2012 [cited by applicant]
US 20120072350A1 · Goldthwaite et al. · 2012 [cited by applicant]
US 20120136786A1 · Romagnoli et al. · 2012 [cited by applicant]
US 20120310760A1 · Phillips et al. · 2012 [cited by applicant]
US 20130013499A1 · Kalgi · 2013 [cited by applicant]
US 20130030997A1 · Spodak et al. · 2013 [cited by applicant]
US 20130060618A1 · Baron et al. · 2013 [cited by applicant]
US 20130080229A1 · Fisher · 2013 [cited by applicant]
US 20130097078A1 · Wong · 2013 [cited by examiner]
US 20130134216A1 · Spodak et al. · 2013 [cited by applicant]
US 20130185167A1 · Mestre et al. · 2013 [cited by applicant]
US 20130204697A1 · Boal · 2013 [cited by applicant]
US 20130211929A1 · Itwaru · 2013 [cited by applicant]
US 20140081785A1 · Valadas Preto · 2014 [cited by applicant]
US 20140164154A1 · Ramaci · 2014 [cited by applicant]
US 20140372308A1 · Sheets · 2014 [cited by applicant]
US 20150032635A1 · Guise · 2015 [cited by applicant]
US 20150134540A1 · Law · 2015 [cited by applicant]
US 20150142671A1 · Dicker · 2015 [cited by examiner]
US 20150178693A1 · Solis · 2015 [cited by examiner]
US 20150186866A1 · Lund · 2015 [cited by applicant]
US 20150262165A1 · Fisher · 2015 [cited by applicant]
US 20150302413A1 · Dua · 2015 [cited by applicant]
US 20150379283A1 · Spodak et al. · 2015 [cited by applicant]
US 20160012465A1 · Sharp · 2016 [cited by examiner]
US 20160034877A1 · Poole et al. · 2016 [cited by applicant]
US 20160086171A1 · Rehe et al. · 2016 [cited by applicant]
US 20160132862A1 · Poole et al. · 2016 [cited by applicant]
US 20160294727A1 · Varghese · 2016 [cited by examiner]
US 20180005227A1 · Sandeløv · 2018 [cited by examiner]
US 20210406923A1 · Cherry et al. · 2021 [cited by applicant]
US 20220019995A1 · Ngo · 2022 [cited by examiner]
US 20230316242A1 · Choy · 2023 [cited by examiner]
WO 2012154915A1 · 2012 [cited by applicant]
Sposito, “Dynamics Vows to Adapt in World Driven by Mobile”, American Banker 177.F326: 6, SourceMedia, Inc. Jul. 1 (Year: 2011). [cited by examiner]
Stroka, “Ensuring Business and Payments Security”, Automatic Merchandiser 61.4: 16-17, 20-21, Endeavor Business Media, August (Year: 2019). [cited by examiner]
Extended European Search Report for corresponding Application No. 17210992 mailed Apr. 5, 2018. [cited by applicant]
“EMV—Payment Tokenisation Specification Technical Framework,” Mar. 31, 2014, Retrieved from https:www.emvco.com/specifications.aspx?id=263. [cited by applicant]
Office Action in related EP Application No. 17210992.8, mailed Jan. 24, 2020. [cited by applicant]
Summers et al., “Emergence of immediate funds transfer as a general-purpose means of payment,” Federal Reserve Bank of Chicago, Economic Principles 10 (Year: 2011). [cited by applicant]
Valimo: Valimo selected by Gemalto as global authentication vendor—Global reseller agreement makes Mobile ID available to everyone, M2 Presswire, Coventry, ProQuest ID: 444156883, Sep. 9 (Year: 2009). [cited by applicant]