IP Library › Granted Patent US 12,511,646
Granted Patent B2
US 12,511,646 · App. 18/455,230 · Granted Dec 30, 2025

System and method for managing loyalty program accounts

Inventors: Alexander Christian Raphael Venditti (Caledon, CA); Jenny Wai Ching Fung-Peloso (Toronto, CA); Jennifer Marie deLagran (Gloucester, CA)
Assignee: The Toronto-Dominion Bank
G06Q20/3676G06Q20/387G06Q30/0229
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,511,646
App. No.
18/455,230
Granted
Dec 30, 2025
Kind
B2
Abstract

A system and method are provided for managing loyalty program accounts. The method includes providing, from the device, access to a loyalty wallet application. The method also includes storing loyalty account information for a plurality of loyalty accounts in the loyalty wallet application and integrating a loyalty tracking application, operable from the device, with at least one transaction channel accessed via the device. The method also includes receiving transaction data from the at least one transaction channel; detecting, from the transaction data, that a transaction yet to be executed is eligible for a loyalty reward associated with one or more of the plurality of loyalty accounts; and modifying the transaction to use corresponding loyalty account information to obtain the loyalty reward. The method also includes enabling the modified transaction to be completed to obtain the loyalty reward. Notifications may be determined and sent using a machine learning system.

Claims (49)

1 . A device for managing loyalty rewards, the device comprising:

a processor; and

a memory coupled to the processor, the memory storing computer executable instructions that when executed by the processor cause the processor to:

gather, using an add-in integrated with a transaction channel, transaction data associated with a transaction being conducted by the device via the transaction channel;

receive, from the add-in, the transaction data at a loyalty management engine interposed between the device and one or more loyalty system;

compare, at the loyalty management engine, the transaction data with information about the one or more loyalty systems, that to determine whether the transaction is eligible for a loyalty reward if completed via a different transaction channel with which the add-in is integrated;

in response to detecting eligibility via the different transaction channel,

interrupt the transaction being conducted via the transaction channel;

redirect the transaction to the different transaction channel, and modify the transaction using loyalty account information that is eligible to obtain the loyalty reward;

generate a prompt for confirmation of the transaction via the different transaction channel; and

in response to detecting confirmation of the prompt, enable the transaction to be completed with the different transaction channel to obtain the loyalty reward.

2 . The device of claim 1 , wherein the transaction is modified by automatically adding the loyalty account information eligible to obtain the loyalty reward to the transaction.

3 . The device of claim 1 , wherein the transaction is interrupted by the add-in.

4 . The device of claim 1 , wherein the computer executable instructions further cause the processor to:

enable at least one loyalty alert to be executed based on at least one alert criterion.

5 . The device of claim 4 , wherein the at least one alert criterion specifies whether to monitor the transaction data based on i) a transaction type and/or ii) the transaction channel.

6 . The device of claim 4 , wherein the at least one alert criterion specifies to display the prompt when the transaction is one of: being executed, is about to be executed or, has been executed.

7 . The device of claim 1 , wherein the prompt is displayed in an e-commerce checkout window prior to completing the transaction.

8 . The device of claim 1 , wherein the prompt comprises at least one of options to cancel the transaction or redirect the transaction to the different transaction channel.

9 . The device of claim 1 , wherein the device is in communication with a loyalty platform providing at least one function of a loyalty tracking application and/or at least one function of a loyalty wallet application.

10 . The device of claim 9 , wherein the loyalty platform is integrated with an enterprise system to link a first loyalty program associated with the at least one transaction channel, the first loyalty program being associated with the enterprise system, with at least one second loyalty program associated with the different transaction channel, the second loyalty program being associated a loyalty partner system.

11 . The device of claim 1 , wherein the computer executable instructions further cause the processor to:

determine a notification to be sent to a client device conducting the transaction via the different transaction channel, using a machine learning system trained to determine when to send notifications and alerts.

12 . A method of managing loyalty rewards, the method executed by a device and comprising:

gathering, using an add-in integrated with a transaction channel, transaction data associated with a transaction being conducted by the device via the transaction channel;

receiving, from the add-in, the transaction data at a loyalty management engine interposed between the device and one or more loyalty system;

comparing, at the loyalty management engine, the transaction data with information about the one or more loyalty systems to determine whether the transaction is eligible for a loyalty reward if completed via a different transaction channel with which the add-in is integrated;

in response to detecting eligibility via the different transaction channel,

interrupting the transaction being conducted via the transaction channel;

redirecting the transaction to the different transaction channel, and modifying the transaction using loyalty account information that is eligible to obtain the loyalty reward;

generating a prompt to obtain confirmation for the transaction via the different transaction channel; and

in response to detecting confirmation of the prompt, enabling the transaction to be completed with the different transaction channel to obtain the loyalty reward.

13 . The method of claim 12 , wherein the transaction is interrupted by the add-in.

14 . The method of claim 12 , wherein the transaction is modified by automatically adding the loyalty account information eligible to obtain the loyalty reward to the transaction.

15 . The method of claim 12 , further comprising:

enabling at least one loyalty alert to be executed based on at least one alert criterion.

16 . The method of claim 15 , wherein the at least one alert criterion specifies whether to monitor the transaction data based on i) a transaction type and/or ii) the transaction channel.

17 . The method of claim 15 , wherein the at least one alert criterion specifies to display the prompt when the transaction is one of: being executed, is about to be executed or, has been executed.

18 . The method of claim 12 , wherein the device is in communication with a loyalty platform providing at least one function of a loyalty tracking application and/or at least one function of a loyalty wallet application.

19 . The method of claim 18 , wherein the loyalty platform is integrated with an enterprise system to link a first loyalty program associated with the transaction channel, the first loyalty program being associated with the enterprise system with at least one second loyalty program associated with the different transaction channel, the second loyalty program being associated a loyalty partner system.

20 . A non-transitory computer readable medium for managing loyalty program accounts, the computer readable medium comprising computer executable instructions for:

gathering, using an add-in integrated with a transaction channel, transaction data associated with a transaction being conducted by the device via the transaction channel;

receiving, from the add-in, the transaction data at a loyalty management engine interposed between the device and one or more loyalty system;

comparing, at the loyalty management engine, the transaction data with information about the one or more loyalty systems to determine whether the transaction is eligible for a loyalty reward if completed via a different transaction channel with which the add-in is integrated;

in response to detecting eligibility via the different transaction channel,

interrupting the transaction being conducted via the transaction channel;

redirecting the transaction to the different transaction channel, and modifying the transaction using loyalty account information that is eligible to obtain the loyalty reward;

generating a prompt to obtain confirmation for the transaction via the different transaction channel; and

in response to detecting confirmation of the prompt, enabling the transaction to be completed with the different transaction channel to obtain the loyalty reward.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 24, 2023
From: VENDITTI, ALEXANDER CHRISTIAN RAPHAEL; FUNG-PELOSO, JENNY WAI CHING; DELAGRAN, JENNIFER MARIE
To: THE TORONTO-DOMINION BANK
Reel/Frame 064696/0322 →
Continuity (3)
Continuation 17547490 · Dec 10, 2021
Continuation In Part 17305528 · Jul 9, 2021
Related Publication 20230401569A1 · Dec 14, 2023
References Cited (78)
US 7398225B2 · Votmer et al. · 2008 [cited by applicant]
US 7578430B2 · Michelsen et al. · 2009 [cited by applicant]
US 8538827B1 · Dryer · 2013 [cited by examiner]
US 8660893B2 · Fordyce, III · 2014 [cited by applicant]
US 8725633B1 · Bauer et al. · 2014 [cited by applicant]
US 8732013B2 · Senghore et al. · 2014 [cited by applicant]
US 9990646B2 · Salmon et al. · 2018 [cited by applicant]
US 10198740B2 · Badger et al. · 2019 [cited by applicant]
US 10223707B2 · Granville, III · 2019 [cited by applicant]
US 10304075B2 · Walz et al. · 2019 [cited by applicant]
US 10467647B2 · Kim et al. · 2019 [cited by applicant]
US 10496979B2 · Taveau et al. · 2019 [cited by applicant]
US 10521820B1 · Jarvis et al. · 2019 [cited by applicant]
US 10535077B2 · Enriquez et al. · 2020 [cited by applicant]
US 10540675B2 · Tietzen et al. · 2020 [cited by applicant]
US 10740768B2 · Skowronek et al. · 2020 [cited by applicant]
US 10839366B2 · Venkatesan et al. · 2020 [cited by applicant]
US 10846746B2 · Windmueller · 2020 [cited by applicant]
US 10861041B2 · Tietzen et al. · 2020 [cited by applicant]
US 10867317B2 · Ladds et al. · 2020 [cited by applicant]
US 10878398B2 · Bloy et al. · 2020 [cited by applicant]
US 10878440B1 · Bermudez et al. · 2020 [cited by applicant]
US 10942913B1 · Khoyilar et al. · 2021 [cited by applicant]
US 20020082920A1 · Austin et al. · 2002 [cited by applicant]
US 20020123926A1 · Bushold et al. · 2002 [cited by applicant]
US 20030040964A1 · Lacek · 2003 [cited by applicant]
US 20030130895A1 · Antonucci · 2003 [cited by applicant]
US 20050071227A1 · Hammad et al. · 2005 [cited by applicant]
US 20050144071A1 · Monahan et al. · 2005 [cited by applicant]
US 20060253320A1 · Heywood · 2006 [cited by applicant]
US 20080133351A1 · White et al. · 2008 [cited by applicant]
US 20080210753A1 · Plozay · 2008 [cited by examiner]
US 20100082420A1 · Trifiletti et al. · 2010 [cited by applicant]
US 20100106570A1 · Radu et al. · 2010 [cited by applicant]
US 20120053987A1 · Satyavolu · 2012 [cited by applicant]
US 20120101881A1 · Taylor et al. · 2012 [cited by applicant]
US 20130036001A1 · Wegner et al. · 2013 [cited by applicant]
US 20130103484A1 · Mclaughlin · 2013 [cited by applicant]
US 20130124263A1 · Amaro et al. · 2013 [cited by applicant]
US 20130246151A1 · Raghavan · 2013 [cited by examiner]
US 20130325579A1 · Salmon et al. · 2013 [cited by applicant]
US 20140180826A1 · Boal · 2014 [cited by applicant]
US 20150149272A1 · Salmon et al. · 2015 [cited by applicant]
US 20150170180A1 · Itwaru · 2015 [cited by applicant]
US 20150235256A1 · Barsoum · 2015 [cited by examiner]
US 20150348083A1 · Brill · 2015 [cited by applicant]
US 20160048864A1 · Beer · 2016 [cited by applicant]
US 20160071140A1 · Sherman · 2016 [cited by applicant]
US 20160078466A1 · Markowitz · 2016 [cited by applicant]
US 20170024724A1 · Kwak · 2017 [cited by examiner]
US 20170024759A1 · Taneja et al. · 2017 [cited by applicant]
US 20170278125A1 · Tietzen et al. · 2017 [cited by applicant]
US 20180268401A1 · Ortiz · 2018 [cited by applicant]
US 20180276710A1 · Tietzen et al. · 2018 [cited by applicant]
US 20180293573A1 · Ortiz et al. · 2018 [cited by applicant]
US 20190108542A1 · Durvasula et al. · 2019 [cited by applicant]
US 20190180310A1 · Jones · 2019 [cited by applicant]
US 20190180311A1 · Chan et al. · 2019 [cited by applicant]
US 20190197575A1 · Ladds · 2019 [cited by applicant]
US 20200051112A1 · Nelson et al. · 2020 [cited by applicant]
US 20200082427A1 · Gleeson et al. · 2020 [cited by applicant]
US 20200104825A1 · Khan · 2020 [cited by examiner]
US 20200126107A9 · Shah et al. · 2020 [cited by applicant]
US 20200134657A1 · Darmo et al. · 2020 [cited by applicant]
US 20200234327A1 · Salloum · 2020 [cited by applicant]
US 20200242669A1 · Carroll et al. · 2020 [cited by applicant]
US 20200279288A1 · Song · 2020 [cited by applicant]
US 20210150560A1 · Gupta et al. · 2021 [cited by applicant]
US 20210166260A1 · Ho · 2021 [cited by applicant]
US 20210377260A1 · Phillips · 2021 [cited by applicant]
US 20220391938A1 · Sridhar · 2022 [cited by applicant]
KR 101945287 · 2018 [cited by applicant]
WO 2018174813A1 · 2018 [cited by applicant]
WO 2020167614A1 · 2020 [cited by applicant]
WO 2021067949A1 · 2021 [cited by applicant]
What Is the Rakuten Cash Back Button ?;Rakuten https://www.rakuten.com/help/article/what-is-the-rakuten-cash-back-button-360002116947https://www.rakuten.com/button.htm; Retrieved from the Internet Oct. 10, 2021. [cited by applicant]
U.S. Appl. No. 17/547,490, filed Dec. 10, 2021. [cited by applicant]
U.S. Appl. No. 17/305,528, filed Jul. 9, 2021. [cited by applicant]