Loyalty point distributions using a decentralized loyalty ID

Patent metadata

Field	Value
Publication number	US-12561712-B2
Application number	US-202217857471-A
Country	US
Kind code	B2
Filing date	Jul 5, 2022
Priority date	Oct 9, 2017
Publication date	Feb 24, 2026
Grant date	Feb 24, 2026

Abstract

A blockchain-based loyalty point distribution system may be configured to provide decentralized loyalty IDs. In one example, a system comprising a computing device that is configured to determine that a reward event has been initiated by a user and invoke executable code to display a user interface for selecting a loyalty provider for storing the reward event. The loyalty provider for storing the reward event is identified and the executable code is invoked to display a login page for the selected loyalty provider. A loyalty ID is determined and a customer reward to be written to a blockchain based at least in part on a public key.

First claim

Therefore, the following is claimed:

1 . A method, comprising:
determining, by a processor, that a reward event has been initiated by a user based at least in part on a completion of a behavioral event or a transactional event; invoking, by the processor, executable code to display a user interface for selecting a loyalty provider for storing the reward event in response to determining the reward event has been initiated; identifying, by the processor, a selected loyalty provider for storing the reward event based at least in part on a selection of a user interface element for the loyalty provider; invoking, by the processor, the executable code to display a login page for the selected loyalty provider within the user interface based at least in part on fetching the login page for the selected loyalty provider from a provider system and by loading the login page within the user interface; determining, by the processor, a decentralized ID based at least in part on a customer login credential received via the login page, the decentralized ID being determined by submitting a query to a loyalty provider database using the customer login credential, the decentralized ID comprising a public key associated with the user; and causing, by the processor, a customer reward to be written to a blockchain based at least in part on the public key, wherein the customer reward is written to a private or a semi-private ledger associated with the user by a loyalty ID and maintained by the blockchain, and wherein a smart contract is executed to validate the customer reward by comparing the decentralized ID to the loyalty ID associated with the private or the semi-private ledger.

2 . The method of claim 1 , wherein invoking the executable code to display the login page for the selected loyalty provider further comprising:
causing, by the processor, the executable code to fetch the login page from a loyalty provider system associated with the selected loyalty provider.

3 . The method of claim 1 , wherein the executable code configured to reference an HTML page or a software library associated with a loyalty provider system for displaying the login page for the selected loyalty provider.

4 . The method of claim 1 , wherein the customer reward comprises the reward event, a partner ID associated with the loyalty provider, and the decentralized ID.

5 . The method of claim 1 , further comprising:
validating, by the processor, the customer login credential by transmitting the customer login credential to a loyalty provider system; and receiving, by the processor, a login cookie for the executable code from the loyalty provider system a transaction request, wherein the transaction request comprises a loyalty point payment request.

6 . The method of claim 1 , wherein causing the customer reward to be written to the blockchain further comprises executing a smart contract to write the customer reward to the private or the semi-private ledger of the blockchain.

7 . The method of claim 1 , wherein causing the customer reward to be written to the blockchain further comprises
executing the smart contract to write the customer reward to the private or the semi-private ledger of the blockchain in response to validating the customer reward.

8 . A system, comprising:
a computing device that includes a processor; a memory configured to communicate with the processor; and machine-readable instructions stored in the memory that, when executed by the processor, cause the computing device to at least: determine that a reward event has been initiated by a user based at least in part on a completion of a behavioral event or a transactional event; invoke executable code to display a user interface for selecting a loyalty provider for storing the reward event in response to determining the reward event has been initiated; identify a selected loyalty provider for storing the reward event based at least in part on a selection of a user interface element for the loyalty provider; invoke the executable code to display a login page for the selected loyalty provider within the user interface based at least in part on fetching the login page for the selected loyalty provider from a provider system and by loading the login page within the user interface; determine a decentralized ID based at least in part on a customer login credential received via the login page, the decentralized ID being determined by submitting a query to a loyalty provider database using the customer login credential, the decentralized ID comprising a public key associated with the user; and cause a customer reward to be written to a blockchain based at least in part on the public key, wherein the customer reward comprises the reward event, a partner ID associated with the loyalty provider, and the decentralized ID, wherein the customer reward is written to a private or a semi-private ledger associated with the user by a loyalty ID and maintained by the blockchain, and wherein a smart contract is executed to validate the customer reward by comparing the decentralized ID to the loyalty ID associated with the private or the semi-private ledger.

9 . The system of claim 8 , wherein invoking the executable code to display the login page for the selected loyalty provider further comprises:
causing the executable code to fetch the login page from a loyalty provider system associated with the loyalty provider.

10 . The system of claim 8 , wherein the executable code configured to reference a software library associated with a loyalty provider system for displaying the login page for the selected loyalty provider.

11 . The system of claim 8 , wherein the customer reward comprises the reward event, a partner ID associated with the loyalty provider, and the decentralized ID.

12 . The system of claim 8 , wherein the machine-readable instructions, when executed by the processor, cause the computing device to at least:
validate the customer login credential by transmitting the customer login credential to a loyalty provider system; and receive a login cookie for the executable code from the loyalty provider system a transaction request, wherein the transaction request comprises a loyalty point payment request.

13 . The system of claim 8 , wherein causing the customer reward to be written to the blockchain further comprises executing a smart contract to write the customer reward to the private or the semi-private ledger of the blockchain.

14 . The system of claim 8 , wherein causing the customer reward to be written to the blockchain further causes the computing device to at least
cause the smart contract to write the customer reward to the private or the semi-private ledger of the blockchain in response to validating the customer reward.

15 . A non-transitory computer readable medium having machine-readable instructions executable by a processor of a computing device, wherein the machine-readable instructions, when executed by the processor, cause the computing device to at least:
determine that a reward event has been initiated by a user based at least in part on a completion of a behavioral event or a transactional event; invoke executable code to display a user interface for selecting a loyalty provider for storing the reward event in response to determining the reward event has been initiated; identify a selected loyalty provider for storing the reward event based at least in part on a selection of a user interface element for the loyalty provider; invoke the executable code to display a login page for the selected loyalty provider within the user inter

Assignees

• American Express Travel Related Services Co Inc

Inventors

• Chan Calvin
• Cracchiolo Christopher
• Ferenczi Andras
• Baal Thomas Andrew Martin

Classifications

• H04L9/50

  using hash chains, e.g. blockchains or hash trees · CPC title

• H04L9/3239

  involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD · CPC title

• H04L2209/56

  Financial cryptography, e.g. electronic payment or e-cash · CPC title

• H04L9/3297

  involving time stamps, e.g. generation of time stamps · CPC title

• G06Q30/0236

  Incentive or reward received by requiring registration or ID from user · CPC title