# US 12,118,533 B1 · Behavior based allocation of payment tokens

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 12,118,533 B1
- Document ID: US12118533B1
- Status: Granted
- Kind: B1
- Application number: 16/722,966
- Filed: 2019-12-20
- Granted: 2024-10-15
- Earliest claimed: 2015-09-25
- Assignees: Wells Fargo Bank, N.A.
- Applicants: Wells Fargo Bank, N.A.
- Inventors: Ben L. Hussey
- Web page: https://patentgrep.com/patent/US12118533B1

## CPC

- G06Q 20/3263: {characterised by activation or deactivation of payment capabilities}
- G06Q 20/322: {Aspects of commerce using mobile devices [M-devices]}
- G06Q 20/326: {Payment applications installed on the mobile devices}
- G06Q 20/34: using cards, e.g. integrated circuit [IC] cards or magnetic cards
- G06Q 20/341: {Active cards, i.e. cards including their own processing means, e.g. including an IC or chip}
- G06Q 20/385: {using an alias or single-use codes}
- G06Q 20/389: {Keeping log of transactions for guaranteeing non-repudiation of a transaction}
- G06Q 20/401: {Transaction verification}
- G06Q 20/4016: {involving fraud or risk level assessment in transaction processing}
- G06Q 20/4018: {using the card verification value [CVV] associated with the card}
- G06Q 20/405: {Establishing or using transaction specific rules}
- H04L 9/0847: {involving identity based encryption [IBE] schemes}
- H04L 9/3228: {One-time or temporary data, i.e. information which is sent for every authentication or authorization, e.g. one-time-password, one-time-token or one-time-key}
- G06Q 20/24: Credit schemes, i.e. "pay after"
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

The disclosure describes a campaign director (CD) system associated with a financial institution and an associated campaign manager (CM) unit executing on a mobile device used to facilitate behavior based allocation of payment tokens and activation of payment transactions based on the tokens. The CM unit of the mobile device may be programmed by the CD system at the financial institution to generate tokens according to a token generation model that is a function of financial behavior history associated with a credit card account. When a credit card is used to initiate a payment transaction with a merchant, the CM unit of the mobile device may generate a token for the payment transaction and send the token to the CD system at the financial institution. The CD system then determines whether to activate the payment transaction based on the token and merchant data associated with the payment transaction.

## Claims

### Claim 1

A campaign director (CD) system associated with a financial institution, the system comprising:
one or more processors;
and a memory storing computer executable instructions that, when executed by the one or more processors, cause the one or more processors to:
program a token generation engine of a campaign manager (CM) unit executed on one or more processors of a mobile device to generate tokens for payment transactions using at least one of a complexity of algorithm or a level of encryption based on a level of risk indicated by a financial behavior history associated with a credit card account at the financial institution,
receive, from the token generation engine of the CM unit of the mobile device, a token generated for a payment transaction initiated by a credit card of the credit card account with a merchant in accordance with the least one of the complexity of algorithm or the level of encryption, wherein the token comprises a static identifier for the credit card account, a random identifier generated by the CM unit of the mobile device for the payment transaction, and preemptive information for the payment transaction,
receive, from the merchant, merchant data associated with the payment transaction,
compare the preemptive information of the token generated for the payment transaction and actual payment transaction information included in the merchant data associated with the payment transaction,
determine whether to activate the payment transaction based on the comparison of the token generated for the payment transaction and the merchant data associated with the payment transaction,
send, to at least one of the CM unit of the mobile device or the merchant, a message indicating whether the payment transaction is activated,
determine whether to shut down the CM unit based on one of the payment transaction being activated or occurrence of an error or an exception at the CM unit, and
based on a determination to shut down the CM unit, send, to the CM unit of the mobile device, instructions to shut down the CM unit.

### Claim 2 (depends on 1)

The system of claim 1, wherein the instructions cause the one or more processors to periodically update the token generation engine of the CM unit of the mobile device to change the at least one of the complexity of algorithm or the level of encryption used by the token generation engine based on changes to the level of risk indicated by the financial behavior history associated with the credit card account.

### Claim 3 (depends on 1)

The system of claim 1, wherein the instructions cause the one or more processors to program the token generation engine of the CM unit of the mobile device with a predetermined number of tokens available for generation by the token generation engine of the CM unit based on the financial behavior history associated with the credit card account.

### Claim 4 (depends on 1)

The system of claim 1, wherein the preemptive information of the token generated for the payment transaction includes one or more of a handshake timestamp between the credit card and the merchant, a monetary amount, a geographic location of the merchant, or a name of the merchant.

### Claim 5 (depends on 1)

The system of claim 1, wherein the instructions cause the one or more processors to, when the token generated for the payment transaction matches the merchant data associated with the payment transaction, send a transaction activation message to the merchant and the CM unit of the mobile device indicating that the payment transaction is activated.

### Claim 6 (depends on 1)

The system of claim 1, wherein the instructions cause the one or more processors to, when the token generated for the payment transaction does not match the merchant data associated with the payment transaction, send a transaction denial message to the merchant and the CM unit of the mobile device indicating that the payment transaction is denied.

### Claim 7 (depends on 1)

The system of claim 1, wherein the instructions cause the one or more processors to:
allocate a time slot interval for the payment transaction;
upon receipt of the token for the payment transaction within the time slot interval, store the token for the payment transaction and start a watchdog timer;
in the case that the merchant data is received prior to expiration of the watchdog timer, activate the payment transaction based on the match between the preemptive information of the token and the actual payment transaction information included in the merchant data; and
in the case that the merchant data is received after expiration of the watchdog timer, deny the payment transaction.

### Claim 8 (depends on 1)

The system of claim 1, wherein the instructions cause the one or more processors to, when the payment transaction is denied and a number of denied payment transactions initiated by the credit card of the credit card account exceeds a risk threshold value, deactivate at least one of the CM unit of the mobile device, the credit card of the credit card account, or the CD system at the financial institution.

### Claim 9

A method comprising:
programing, by a campaign director (CD) system associated with a financial institution, a token generation engine of a campaign manager (CM) unit executed on one or more processors of a mobile device to generate tokens for payment transactions using at least one of a complexity of algorithm or a level of encryption based on a level of risk indicated by a financial behavior history associated with a credit card account at the financial institution;
receiving, by the CD system and from the token generation engine of the CM unit of the mobile device, a token generated for a payment transaction initiated by a credit card of the credit card account with a merchant in accordance with the least one of the complexity of algorithm or the level of encryption, wherein the token comprises a static identifier for the credit card account, a random identifier generated by the CM unit of the mobile device for the payment transaction, and preemptive information for the payment transaction;
receiving, by the CD system and from the merchant, merchant data associated with the payment transaction;
comparing, by the CD system, the preemptive information of the token generated for the payment transaction and actual payment transaction information included in the merchant data associated with the payment transaction;
determining, by the CD system, whether to activate the payment transaction based on the comparison of the token generated for the payment transaction and the merchant data associated with the payment transaction;
sending, by the CD system to at least one of the CM unit of the mobile device or the merchant, a message indicating whether the payment transaction is activated;
determining, by the CD system, whether to shut down the CM unit based on one of the payment transaction being activated or occurrence of an error or an exception at the CM unit; and
based on a determination to shut down the CM unit, sending, by the CD system to the CM unit of the mobile device, instructions to shut down the CM unit.

### Claim 10 (depends on 9)

The method of claim 9, further comprising periodically updating the token generation engine of the CM unit of the mobile device to change the at least one of the complexity of algorithm or the level of encryption used by the token generation engine based on changes to the level of risk indicated by the financial behavior history associated with the credit card account.

### Claim 11 (depends on 9)

The method of claim 9, wherein the preemptive information of the token generated for the payment transaction includes one or more of a handshake timestamp between the credit card and the merchant, a monetary amount, a geographic location of the merchant, or a name of the merchant.

### Claim 12 (depends on 11)

The method of claim 11, wherein sending the message comprises, when the token generated for the payment transaction matches the merchant data associated with the payment transaction, sending a transaction activation message to the merchant and the CM unit of the mobile device indicating that the payment transaction is activated.

### Claim 13 (depends on 11)

The method of claim 11, wherein sending the message comprises, when the token generated for the payment transaction does not match the merchant data associated with the payment transaction, sending a transaction denial message to the merchant and the CM unit of the mobile device indicating that the payment transaction is denied.

### Claim 14 (depends on 11)

The method of claim 11, further comprising:
allocating a time slot interval for the payment transaction;
upon receipt of the token for the payment transaction within the time slot interval, storing the token for the payment transaction and starting a watchdog timer;
in the case that the merchant data is received prior to expiration of the watchdog timer, activating the payment transaction based on the match between the preemptive information of the token and the actual payment transaction information included in the merchant data; and
in the case that the merchant data is received after expiration of the watchdog timer, denying the payment transaction.

### Claim 15 (depends on 11)

The method of claim 11, further comprising, when the payment transaction is denied and a number of denied payment transactions initiated by the credit card of the credit card account exceeds a risk threshold value, deactivating at least one of the CM unit of the mobile device, the credit card of the credit card account, or the CD system at the financial institution.

### Claim 16

A non-transitory computer readable medium storing instructions that, when executed, cause one or more processors of a campaign director (CD) system associated with a financial institution to:
program a token generation engine of a campaign manager (CM) unit executed on one or more processors of a mobile device to generate tokens for payment transactions using at least one of a complexity of algorithm or a level of encryption based on a level of risk indicated by a financial behavior history associated with a credit card account at the financial institution;
receive, from the token generation engine of the CM unit of the mobile device, a token generated for a payment transaction initiated by a credit card of the credit card account with a merchant in accordance with the least one of the complexity of algorithm or the level of encryption, wherein the token comprises a static identifier for the credit card account, a random identifier generated by the CM unit of the mobile device for the payment transaction, and preemptive information for the payment transaction;
receive, from the merchant, merchant data associated with the payment transaction; compare the preemptive information of the token generated for the payment transaction and actual payment transaction information included in the merchant data associated with the payment transaction;
determine whether to activate the payment transaction based on the comparison of the token generated for the payment transaction and the merchant data associated with the payment transaction;
send, to at least one of the CM unit of the mobile device or the merchant, a message indicating whether the payment transaction is activated;
determine whether to shut down the CM unit based on one of the payment transaction being activated or occurrence of an error or an exception at the CM unit; and
based on a determination to shut down the CM unit, send, to the CM unit of the mobile device, instructions to shut down the CM unit.

### Claim 17 (depends on 1)

The system of claim 1, wherein to program the token generation engine of the CM unit of the mobile device, the instructions cause the one or more processors to program the token generation engine to generate tokens for payment transaction using at least one of a high-complexity algorithm or a high level of encryption based on the financial behavior history indicating high risk behavior.

### Claim 18 (depends on 1)

The system of claim 1, wherein to program the token generation engine of the CM unit of the mobile device, the instructions cause the one or more processors to program the token generation engine to generate tokens for payment transaction using at least one of a low-complexity algorithm or a low level of encryption based on the financial behavior history indicating low risk behavior.

### Claim 19 (depends on 2)

The system of claim 2, wherein to periodically update the token generation engine of the CM unit of the mobile device, the instructions cause the one or more processors to change the at least one of the complexity of algorithm from a low-complexity algorithm to a high-complexity algorithm or the level of encryption from a low level of encryption to a high level of encryption based on changes to the financial behavior history from indicating low risk behavior to indicating high risk behavior.