IP Library Granted Patent US 12,327,231
Granted Patent B2
US 12,327,231 · App. 18/239,065 · Granted Jun 10, 2025

Systems, methods, and devices for secure generation and processing of data sets representing pre-funded payments

Inventors: Edison U. Ortiz (Orlando, FL); Terry W. Lee (Toronto, CA); Marko Pavlovic (Toronto, CA); Arnold Badal-Badalian (Toronto, CA)
Assignee: ROYAL BANK OF CANADA
G06Q20/28G06Q20/20G06Q20/3221G06Q20/3223G06Q20/3278G06Q20/351G06Q20/36G06Q20/367G06Q20/3672G06Q20/385G06Q20/387G06Q20/40H04L63/0428G06Q2220/00H04L2209/56H04L2209/80
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,327,231
App. No.
18/239,065
Granted
Jun 10, 2025
Kind
B2
Abstract

Systems, devices, methods, and non-transient machine-interpretable programming and/or other instruction products for the generation, transfer, storage, and other processing of secure data sets used in electronic payment transactions, including particularly the secure creation, administration, manipulation, processing, and storage of electronic data useful in processing of pre-funded, pre-paid, and/or otherwise pre-authorized payment transactions. Devices and methods in accordance with the disclosure can be used to create pre-funded payment token data sets, the token data sets comprising secure data items or records representing negotiable monetary or other economic value, and to share them between network communication devices such as smart phones, home or business desktop computers, etc., for use in purchases and other transactions.

Claims (58)

1. A user device comprising:

at least one data processor; and

at least one persistent memory, the at least one persistent memory comprising secure data storage media and stored, machine-interpretable instructions adapted to configure the at least one data processor to:

access in the secure data storage media data representing at least a negotiable pre-funded token data set associated with a ledger account of a token administration system;

generate a secure negotiable pre-funded token transfer data set;

modify the pre-funded token transfer data set used to generate the pre-funded token to include:

data representing the same or another negotiable pre-funded payment authorization; and

verification data for use in the authorization of a pre-funded token transfer recipient to access the pre-funded token; and

route the secure negotiable pre-funded token transfer data set to a network address associated with the token administration system.

2. The user device of claim 1 , wherein the ledger account is associated with at least one of:

a credit card account;

a debit account; or

a loyalty program account.

3. The user device of claim 1 , wherein the at least one data processor is configured to:

generate the secure negotiable pre-funded token transfer data set; and

wherein routing the secure negotiable pre-funded token transfer data set to the network address associated with the pre-funded token transfer recipient is conditioned upon the data indicating that the pre-funded negotiable amount is transferable.

4. The user device of claim 1 , wherein the secure negotiable pre-funded token transfer data set comprises at least one gift personalization data set comprising data representing at least one of:

at least one image; or

at least one text message.

5. The user device of claim 1 , wherein the machine-interpretable instructions are adapted to configure the at least one data processor to:

route to a network address associated with the pre-funded token transfer recipient a pre-funded token delivery notification data set, the pre-funded token delivery notification data set comprising at least data useful for causing a display of a second data communication device to display a notification of receipt of a negotiable pre-funded token data set.

6. The user device of claim 5 , wherein the pre-funded token delivery notification data set comprises at least one gift personalization data set comprising data representing at least one of:

at least one image; or

at least one text message.

7. The user device of claim 1 , wherein the secure negotiable pre-funded token transfer data set comprises data configured to cause a device associated with the network address associated with the pre-funded token transfer recipient to initiate a recipient verification process.

8. The user device of claim 1 , wherein the machine-interpretable instructions are adapted to configure the at least one data processor to generate a plurality of secure negotiable pre-funded token transfer data sets, each secure negotiable pre-funded token transfer data set comprising data identifying at least one network address associated with a pre-funded token transfer recipient and data representing the negotiable pre-funded payment authorization and at least one negotiable pre-funded token transfer amount, a sum of the plurality of negotiable pre-funded token transfer amounts being less than or equal to the pre-funded negotiable amount.

9. The user device of claim 8 , wherein at least one of:

the machine-interpretable instructions are adapted to configure the at least one data processor to route at least one of the plurality of secure negotiable pre-funded token transfer data sets to the at least one network address; or

each of the plurality of secure negotiable pre-funded token transfer data sets comprises data identifying a network address associated with a different pre-funded token transfer recipient.

10. The user device of claim 1 , wherein routing the secure negotiable pre-funded token transfer data set to a network address associated with the pre-funded token transfer recipient excludes routing via a third party payment processor.

11. A computer-implemented method comprising:

accessing in the secure data storage media data representing at least a negotiable pre-funded token data set associated with a ledger account of a token administration system;

generating a secure negotiable pre-funded token transfer data set;

modifying the pre-funded token transfer data set used to generate the pre-funded token to include:

data representing the same or another negotiable pre-funded payment authorization; and

verification data for use in the authorization of the recipient to access the pre-funded token; and

routing the secure negotiable pre-funded token transfer data set to a network address associated with the token administration system.

12. The computer-implemented method of claim 11 , wherein the general ledger account is associated with at least one of:

a credit card account;

a debit account; or

a loyalty program account.

13. The computer-implemented method of claim 11 , comprising:

generating the secure negotiable pre-funded token transfer data set; and

wherein routing the secure negotiable pre-funded token transfer data set to the network address associated with the pre-funded token transfer recipient is conditioned upon the data indicating that the pre-funded negotiable amount is transferable.

14. The computer-implemented method of claim 11 , wherein the secure negotiable pre-funded token transfer data set comprises at least one gift personalization data set comprising data representing at least one of:

at least one image; or

at least one text message.

15. The computer-implemented method of claim 11 , comprising:

routing to a network address associated with the pre-funded token transfer recipient a pre-funded token delivery notification data set, the pre-funded token delivery notification data set comprising at least data useful for causing a display of a second data communication device to display a notification of receipt of a negotiable pre-funded token data set.

16. The computer-implemented method of claim 15 , wherein the pre-funded token delivery notification data set comprises at least one gift personalization data set comprising data representing at least one of:

at least one image; or

at least one text message.

17. The computer-implemented method of claim 11 , wherein the secure negotiable pre-funded token transfer data set comprises data configured to cause a device associated with the network address associated with the pre-funded token transfer recipient to initiate a recipient verification process.

18. The computer-implemented method of claim 11 , comprising generating a plurality of secure negotiable pre-funded token transfer data sets, each secure negotiable pre-funded token transfer data set comprising data identifying at least one network address associated with a pre-funded token transfer recipient and data representing the negotiable pre-funded payment authorization and at least one negotiable pre-funded token transfer amount, a sum of the plurality of negotiable pre-funded token transfer amounts being less than or equal to the pre-funded negotiable amount.

19. The computer-implemented method of claim 18 , wherein at least one of:

the comprising routing at least one of the plurality of secure negotiable pre-funded token transfer data sets to the at least one network address; or

each of the plurality of secure negotiable pre-funded token transfer data sets comprises data identifying a network address associated with a different pre-funded token transfer recipient.

20. The computer-implemented method of claim 11 , wherein routing the secure negotiable pre-funded token transfer data set to a network address associated with the pre-funded token transfer recipient excludes routing via a third party payment processor.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 7, 2025
From: ORTIZ, EDISON U.; W. LEE, TERRY; PAVLOVIC, MARKO; BADAL-BADALIAN, ARNOLD
To: ROYAL BANK OF CANADA
Reel/Frame 070750/0347 →
Continuity (30)
Continuation 17561638 · Dec 23, 2021
Continuation 15453193 · Mar 8, 2017
Continuation In Part 15201428 · Jul 2, 2016
Continuation In Part 15000685 · Jan 19, 2016
Continuation In Part 15000685 · Jan 19, 2016
Continuation In Part 14879913 · Oct 9, 2015
Continuation In Part 14869186 · Sep 29, 2015
Continuation In Part 14705477 · May 6, 2015
Continuation In Part 14705477 · May 6, 2015
Continuation 14287134 · May 26, 2014
Continuation 14056440 · Oct 17, 2013
Continuation 14056440 · Oct 17, 2013
Provisional Application 62305429 · Mar 8, 2016
Provisional Application 62200859 · Aug 4, 2015
Provisional Application 62188067 · Jul 2, 2015
Provisional Application 62118990 · Feb 20, 2015
Provisional Application 62105061 · Jan 19, 2015
Provisional Application 62089210 · Dec 8, 2014
Provisional Application 62084549 · Nov 25, 2014
Provisional Application 62078683 · Nov 12, 2014
Provisional Application 62065280 · Oct 17, 2014
Provisional Application 62062467 · Oct 10, 2014
Provisional Application 62058799 · Oct 2, 2014
Provisional Application 62056688 · Sep 29, 2014
Provisional Application 61863593 · Aug 8, 2013
Provisional Application 61833188 · Jun 10, 2013
Provisional Application 61825865 · May 21, 2013
Provisional Application 61811783 · Apr 14, 2013
Provisional Application 61715142 · Oct 17, 2012
Related Publication 20230401554A1 · Dec 14, 2023
References Cited (10)
US 8751294B2 · Bhattacharya · 2014 [cited by examiner]
US 9177313B1 · Silverman · 2015 [cited by examiner]
US 9269083B1 · Jarajapu · 2016 [cited by examiner]
US 20070256124A1 · Ih · 2007 [cited by examiner]
US 20110166992A1 · Dessert · 2011 [cited by examiner]
US 20130218657A1 · Salmon · 2013 [cited by examiner]
US 20130339188A1 · Mohamed · 2013 [cited by examiner]
US 20140074701A1 · Kingston · 2014 [cited by examiner]
US 20160371668A1 · Priebatsch · 2016 [cited by examiner]
US 20170323283A1 · Todasco · 2017 [cited by examiner]