IP Library Granted Patent US 12699987
Granted Patent B2
US 12699987 · App. 16/690,636 · Granted Aug 4, 2026

Transaction system with account mapping

Inventors: Lauren Ledwell (Toronto, CA); Steven Noseworthy (Toronto, CA); Arnold Badal-Badalian (Toronto, CA)
Assignee: ROYAL BANK OF CANADA
G06Q20/3674G06N20/00G06Q20/227G06Q20/401G06Q20/42G06Q2220/00
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 12699987
App. No.
16/690,636
Granted
Aug 4, 2026
Kind
B2
Abstract

Processing a transaction includes receiving transaction data for a transaction performed at a merchant, the transaction data including a tokenized universal identifier, a merchant identifier, and a transaction variable; detokenizing the transaction data to determine a universal identifier; identifying multiple accounts associated with the universal identifier; selecting, from the multiple accounts, an account to assign to the transaction, based at least in part on the universal identifier, the merchant identifier, and the transaction variable; and sending account information associated with the selected account to a payment processor to authorize the transaction.

Claims (55)

1 . A computer-implemented method for tokenized inter-process data message routing based at least on for-token transformation conducted dynamically by a token service provider computing device during processing of a transaction authorization request data message for a transaction of funds between a cardholder's corresponding issuer host server and a merchant's corresponding acquirer host server, the method comprising:

generatings, by the token service provider computing device maintaining a centralized token vault data storage, tokenized universal identifier associated with one or more payment token data objects, each payment token data object having a surrogate value data field that replaces a primary account number (PAN) data field, the tokenized universal identifier configured for transmission across a near-field communication system to a merchant device electronically coupled to the acquirer host server, each payment token data object corresponding to an underlying individual verified payment token and the primary account number (PAN) data field issued by the issuer host server and each tokenized universal identifier being stored locally on a digital wallet residing on a user's mobile device;

persisting, by the token service provider computing device, a dynamically updatable merchant map data object comprising a plurality of electronic records associated with each merchant identified by a merchant identifier data field, each electronic record comprising a transaction characteristic variable data field and one or more corresponding merchant transaction preferences configured by the merchant, the one or more corresponding merchant transaction preferences indicating the merchant's preferred method of payment under one or more conditions in the transaction characteristic variable data field;

persisting, by the token service provider computing device, a machine-learning enabled mapping model trained on the dynamically updatable merchant map data object, the machine-learning enabled mapping model optimized and validated using the dynamically updatable merchant map data object;

inputting, by the token service provider computing device, historic transactions to the machine-learning enabled mapping model operating in classification mode to determine the merchant transaction preferences, the token service provider computing device updating the merchant transaction preferences for the dynamically updatable merchant map data object using an output of the machine-learning enabled mapping model;

receiving from the acquirer host server, by the token service provider via a communication network, the transaction authorization request data message comprising a transaction data for a transaction performed at the merchant device using the tokenized universal identifier transmitted across the near-field communication system, the transaction data comprising the tokenized universal identifier, the merchant identifier data field, and a transaction characteristic variable data field;

detokenizing, by the token service provider computing device, the tokenized universal identifier in the transaction authorization request data message, the token service provider computing device determining the one or more underlying payment token data objects based on a token-to-universal identifier mapping stored in the token vault database;

traversing, by the token service provider computing device, the merchant map data object maintained by the token service provider; and

retrieving the underlying merchant transaction preference matching the merchant identifier data field in the merchant map data object;

inputting, by the token service provider computing device, the transaction authorization request data message to the machine-learning enabled mapping model operating in inference mode, the machine-learning enabled mapping model determining one or more payment token data objects for the transaction based on the merchant transaction preferences and the transaction characteristic variable data field;

obtaining, by the token service provider computing device, from the centralized token vault data storage, the one or more corresponding primary account number (PAN) data fields corresponding to the selected one or more payment token data objects, and sending, via the communication network, one or more authorization data messages including the selected one or more payment tokens data objects to one or more corresponding remote payment processors to authorize the transaction;

transferring funds, between the issuer host server and the acquirer host server, according to an activity net balance determined by an aggregate of the one or more authorization data messages corresponding to each primary account number (PAN); and

receiving, by the token service provider computing device, a user input from the cardholder or the merchant representative of transaction miscategorization, the token service provider computing device updating the machine-learning enabled mapping model using the user input.

2 . The computer-implemented method of claim 1 , wherein the tokenized universal identifier (DPAN) is a unique identifier of a user.

3 . The computer-implemented method of claim 1 , wherein the selecting includes performing a lookup of a lookup table.

4 . The computer-implemented method of claim 1 , wherein the selecting includes performing a lookup on the electronic merchant map data object associated with the tokenized universal identifier (DPAN).

5 . The computer-implemented method of claim 1 , wherein the transaction characteristic variable data field includes a date of the transaction.

6 . The computer-implemented method of claim 1 , wherein the transaction characteristic variable data field includes a time of the transaction.

7 . The computer-implemented method of claim 1 , wherein the transaction characteristic variable data field includes a location of the transaction.

8 . The computer-implemented method of claim 1 , further comprising: categorizing the transaction based at least in part on the merchant identifier data field and wherein the selecting is based at least in part on the categorization of the transaction.

9 . The computer-implemented method of claim 1 , wherein the selecting is based at least in part on terms associated with each of the one or more corresponding underlying individual verified payment tokens.

10 . The computer-implemented method of claim 1 , wherein the selecting is based at least in part on costs associated with each of the one or more corresponding underlying individual verified payment tokens.

11 . The computer-implemented method of claim 1 , further comprising: receiving an authorization response from the remote payment processor and sending the authorization response to an acquiring financial institution.

12 . The computer-implemented method of claim 1 , wherein the selected account is tokenized.

13 . The computer-implemented method of claim 12 , further comprising: de-tokenizing the selected account prior to sending account information to the remote payment processor.

14 . The computer-implemented method of claim 1 , further comprising: upon none of the multiple accounts is associated with the universal identifier, the merchant identifier data field, and the transaction characteristic variable data field, selecting a default account.

15 . The computer-implemented method of claim 1 , wherein the selecting is based at least in part on learning a model based on historical transactions associated with the universal identifier data field.

16 . The computer-implemented method of claim 15 , further comprising: receiving a confirmation that a user approves the selected account.

17 . The computer-implemented method of claim 16 , further comprising: updating the model based on the confirmation.

18 . The computer-implemented method of claim 1 , further comprising: tokenizing the universal identifier and sending the tokenized universal identifier to a computing device associated with a user.

19 . A computer system for tokenized inter-process data message routing based at least on token transformation conducted dynamically by a token service provider computing device during processing of a transaction authorization request data message for a transaction of funds between a cardholder's corresponding issuer host server and a merchant's corresponding acquirer host server, the computer system comprising:

a computer processor coupled to computer memory, the computer processor configured to:

generate, by the token service provider computing device maintaining a centralized token vault data storage, a tokenized universal identifier associated with one or more payment token data objects, each payment token data object having a surrogate value data field that replaces a primary account number (PAN) data field, the tokenized universal identifier configured for transmission across a near-field communication system to a merchant device electronically coupled to the acquirer host server, each payment token data object corresponding to an underlying individual verified payment token and the primary account number (PAN) data field issued by the issuer host server and each tokenized universal identifier being stored locally on a digital wallet residing on a user's mobile device;

persist, by the token service provider computing device, a dynamically updatable merchant map data object comprising a plurality of electronic records associated with each merchant identified by a merchant identifier data field, each electronic record comprising a transaction characteristic variable data field and one or more corresponding merchant transaction preferences configured by the merchant, the one or more corresponding merchant transaction preferences indicating the merchant's preferred method of payment under one or more conditions in the transaction characteristic variable data field;

persist, by the token service provider computing device, a machine-learning enabled mapping model trained on the dynamically updatable merchant map data object, the machine-learning enabled mapping model optimized and validated using the dynamically updatable merchant map data object;

input, by the token service provider computing device, historic transactions to the machine-learning enabled mapping model operating in classification mode to determine the merchant transaction preferences, the token service provider computing device updating the merchant transaction preferences for the dynamically updatable merchant map data object using an output of the machine-learning enabled mapping model;

receive from the acquirer host server, by the token service provider via a communication network, the transaction authorization request data message comprising a transaction data for a transaction performed at the merchant device using the tokenized universal identifier transmitted across the near-field communication system, the transaction data comprising the tokenized universal identifier, the merchant identifier data field, and a transaction characteristic variable data field;

detokenize, by the token service provider computing device, the tokenized universal identifier in the transaction authorization request data message, the token service provider computing device determining the one or more underlying payment token data objects based on a token-to-universal identifier mapping stored in the token vault database;

traverse, by the token service provider computing device, the merchant map data object maintained by the token service provider and retrieving the underlying merchant transaction preference matching the merchant identifier data field in the merchant map data object;

input, by the token service provider computing device, the transaction authorization request data message to the machine-learning enabled mapping model operating in inference mode, the machine-learning enabled mapping model determining one or more payment token data objects for the transaction based on the merchant transaction preferences and the transaction characteristic variable data field;

obtain, by the token service provider computing device, from the centralized token vault data storage, the one or more corresponding primary account number (PAN) data fields corresponding to the selected one or more payment token data objects, and sending, via the communication network, one or more authorization data messages including the selected one or more payment token data objects to one or more corresponding remote payment processors to authorize the transaction;

transfer funds, between the issuer host server and the acquirer host server, according to an activity net balance determined by an aggregate of the one or more authorization data messages corresponding to each primary account number (PAN); and

receive, by the token service provider computing device, a user input from the cardholder or the merchant representative of transaction miscategorization, the token service provider computing device updating the machine-learning enabled mapping model using the user input.

20 . A non-transitory computer-readable medium having computer executable instructions stored thereon for execution by one or more computing devices, that when executed by the processor perform the method for tokenized inter-process data message routing based at least on token transformation conducted dynamically by a token service provider computing device during processing of a transaction authorization request data message for a transaction of funds between a cardholder's corresponding issuer host server and a merchant's corresponding acquirer host server, the method comprising:

generating, by the token service provider computing device maintaining a centralized token vault data storage, a tokenized universal identifier associated with one or more payment token data objects, each payment token data object having a surrogate value data field that replaces a primary account number (PAN) data field, the tokenized universal identifier configured for transmission across a near-field communication system to a merchant device electronically coupled to the acquirer host server, each payment token data object corresponding to an underlying individual verified payment token and the primary account number (PAN) data field issued by the issuer host server and each tokenized universal identifier being stored locally on a digital wallet residing on a user's mobile device;

persisting, by the token service provider computing device, a dynamically updatable merchant map data object comprising a plurality of electronic records associated with each merchant identified by a merchant identifier data field, each electronic record comprising a transaction characteristic variable data field and one or more corresponding merchant transaction preferences configured by the merchant, the one or more corresponding merchant transaction preferences indicating the merchant's preferred method of payment under one or more conditions in the transaction characteristic variable data field;

persisting, by the token service provider computing device, a machine-learning enabled mapping model trained on the dynamically updatable merchant map data object, the machine-learning enabled mapping model optimized and validated using the dynamically updatable merchant map data object;

inputting, by the token service provider computing device, historic transactions to the machine-learning enabled mapping model operating in classification mode to determine the merchant transaction preferences, the token service provider computing device updating the merchant transaction preferences for the dynamically updatable merchant map data object using an output of the machine-learning enabled mapping model;

receiving from the acquirer host server, by the token service provider via a communication network, the transaction authorization request data message comprising a transaction data for a transaction performed at the merchant device using the tokenized universal identifier transmitted across the near-field communication system, the transaction data comprising the tokenized universal identifier, the merchant identifier data field, and a transaction characteristic variable data field;

detokenizing, by the token service provider computing device, the tokenized universal identifier in the transaction authorization request data message, the token service provider computing device determining the one or more underlying payment token data objects based on a token-to-universal identifier mapping stored in the token vault database;

traversing, by the token service provider computing device, the merchant map data object maintained by the token service provider and retrieving the underlying merchant transaction preference matching the merchant identifier data field in the merchant map data object;

inputting, by the token service provider computing device, the transaction authorization request data message to the machine-learning enabled mapping model operating in inference mode, the machine-learning enabled mapping model determining one or more payment token data objects for the transaction based on the merchant transaction preferences and the transaction characteristic variable data field;

obtaining, by the token service provider computing device, from the centralized token vault data storage, the one or more corresponding primary account number (PAN) data fields corresponding to the selected one or more payment token data objects, and sending, via the communication network, one or more authorization data messages including the selected one or more payment token data objects to one or more corresponding remote payment processors to authorize the transaction;

transferring funds, between the issuer host server and the acquirer host server, according to an activity net balance determined by an aggregate of the one or more authorization data messages corresponding to each primary account number (PAN); and

receiving, by the token service provider computing device, a user input from the cardholder or the merchant representative of transaction miscategorization, the token service provider computing device updating the machine-learning enabled mapping model using the user input.