Behavior based allocation of payment tokens

1. A method comprising:

programming, by a campaign director (CD) system at 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 based on a financial behavior history associated with a credit card account at the financial institution;

establishing, by the CM unit of the mobile device, communication with the CD system at the financial institution;

receiving, by the CM unit of the mobile device from a credit card, a static identifier for the credit card account of the credit card and preemptive information for a payment transaction with a merchant;

issuing, by the CM unit of the mobile device, a random identifier for the payment transaction;

generating, by the CM unit of the mobile device, a token for the payment transaction according to the token generation engine that is based on the financial behavior history associated with the credit card account, the token including a combination of the static identifier for the credit card account, the random identifier issued for the payment transaction, and the preemptive information received for the payment transaction;

sending, by the CM unit of the mobile device to the CD system at the financial institution, the token generated for the payment transaction;

receiving, by the CD system at the financial institution, the token generated for the payment transaction from the CM unit of the mobile device and merchant data that includes actual payment transaction information for the payment transaction from the merchant;

comparing, by the CD system, the preemptive information of the token generated for the payment transaction and the actual payment transaction information included in the merchant data for the payment transaction;

activating, by the CD system, the payment transaction based on a match between the preemptive information of the token and the actual payment transaction information included in the merchant data for 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 the activation of the payment transaction;

determining, by the CD system, whether to shut down the CM unit based on one of the activation of the payment transaction 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.

2. The method of claim 1 , further comprising updating, by the CD system at the financial institution, the token generation engine of the CM unit of the mobile device based on changes to the financial behavior history associated with the credit card account at the financial institution.

3. The method of claim 1 , wherein the CM unit is programmed with a number of tokens based on the financial behavior history associated with the credit card account, and wherein generating the token for the payment transaction comprises generating one token of the number of tokens.

4. The method of claim 1 , further comprising receiving, by the CM unit of the mobile device from the CD system at the financial institution, a time slot for the payment transaction, wherein sending the token comprises:

sending, by the CM unit of the mobile device to the CD system at the financial institution, the token generated for the payment transaction while the time slot is active; and

requesting a decision of whether the payment transaction is activated.

5. The method of claim 1 , wherein the credit card comprises a physical smart card or one of a plurality of virtual credit cards stored in a mobile payment unit of the mobile device.

6. A system comprising:

a campaign director (CD) system at a financial institution comprising one or more computing devices, and a memory storing computer executable instructions that, when executed by the one or more computing devices, cause the one or more computing devices to perform the steps of programming a token generation engine of a computer executable campaign manager (CM) unit to generate tokens for payment transactions based on a financial behavior history associated with a credit card account at the financial institution; and

a mobile device comprising one or more processors, and a memory storing the CM unit that, when executed by the one or more processors, causes the one or more processors to perform the steps of:

establishing communication with the CD system,

receiving, from a credit card, a static identifier for the credit card account of the credit card and preemptive information for a payment transaction with a merchant,

issuing a random identifier for the payment transaction,

generating a token for the payment transaction according to the token generation engine that is based on the financial behavior history associated with the credit card account, the token including a combination of the static identifier for the credit card account, the random identifier issued for the payment transaction, and the preemptive information received for the payment transaction, and

sending the token generated for the payment transaction to the CD system at the financial institution,

wherein the one or more computing devices of the CD system further perform the steps of:

receiving the token generated for the payment transaction from the CM unit of the mobile device and merchant data including actual payment transaction information for the payment transaction from the merchant,

comparing the preemptive information of the token generated for the payment transaction and the actual payment transaction information included in the merchant data for the payment transaction,

activating the payment transaction based on a match between the preemptive information of the token and the actual payment transaction information included in the merchant data for the payment transaction;

sending, to at least one of the CM unit of the mobile device or the merchant, a message indicating the activation of the payment transaction;

determining whether to shut down the CM unit based on one of the activation of the payment transaction or occurrence of an error or an exception at the CM unit; and

based on a determination to shut down the CM unit, sending, to the CM unit of the mobile device, instructions to shut down the CM unit.

7. The system of claim 6 , wherein the one or more processors of the mobile device further perform the steps of receiving periodic updates to the token generation engine of the CM unit of the mobile device from the CD system at the financial institution based on changes to the financial behavior history associated with the credit card account at the financial institution.

8. The system of claim 6 , wherein the CM unit is programmed with a number of tokens based on the financial behavior history associated with the credit card account, and wherein to generate the token for the payment transaction, the one or more processors of the mobile device further perform the steps of generating one token of the number of tokens.

9. The system of claim 6 , wherein the one or more processors of the mobile device further perform the steps of:

receiving, from the CD system at the financial institution, a time slot for the payment transaction;

sending, to the CD system at the financial institution, the token generated for the payment transaction while the time slot is active; and

requesting a decision of whether the payment transaction is activated.

10. The system of claim 6 , wherein the credit card comprises a physical smart card or one of a plurality of virtual credit cards stored in a mobile payment unit of the mobile device.

11. The system of claim 6 , wherein the one or more computing devices of the CD system further perform the steps of periodically updating the token generation engine of the CM unit of the mobile device based on changes to the financial behavior history associated with the credit card account at the financial institution.

12. The system of claim 6 , wherein the one or more computing devices of the CD system further perform the steps of programming the CM unit of the mobile device with a number of tokens based on the financial behavior history associated with the credit card account.

13. The system of claim 6 , wherein the one or more computing devices of the CD system further perform the steps of, in the case that the preemptive information of the token does not match the actual payment transaction information included in the merchant data, sending a transaction denial message to the merchant and the CM unit of the mobile device.

14. The system of claim 6 , wherein the one or more computing devices of the CD system further perform the steps of:

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 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.

15. The system of claim 6 , wherein the one or more computing devices of the CD system further perform the steps of, in the case that 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, by the CD system at the financial institution, the CM unit of the mobile device.

16. Non-transitory computer readable media storing instructions that, when executed, cause one or more processors to:

program, by a campaign director (CD) system at 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 based on a financial behavior history associated with a credit card account at the financial institution;

establish, by the CM unit of the mobile device, communication with the CD system at the financial institution;

receive, by the CM unit of the mobile device from a credit card, a static identifier for the credit card account of the credit card and preemptive information for a payment transaction with a merchant;

issue, by the CM unit of the mobile device, a random identifier for the payment transaction;

generate, by the CM unit of the mobile device, a token for the payment transaction according to the token generation engine that is based on the financial behavior history associated with the credit card account, the token including a combination of the static identifier for the credit card account, the random identifier issued for the payment transaction, and the preemptive information received for the payment transaction;

send, by the CM unit of the mobile device to the CD system at the financial institution, the token generated for the payment transaction;

receive, by the CD system at the financial institution, the token generated for the payment transaction from the CM unit of the mobile device and merchant data that includes actual payment transaction information for the payment transaction from the merchant;

compare, by the CD system, the preemptive information of the token generated for the payment transaction and the actual payment transaction information included in the merchant data for the payment transaction;

activate, by the CD system, the payment transaction based on a match between the preemptive information of the token and the actual payment transaction information included in the merchant data for the payment transaction;

send, by the CD system to at least one of the CM unit of the mobile device or the merchant, a message indicating the activation of the payment transaction;

determine, by the CD system, whether to shut down the CM unit based on one of the activation of the payment transaction or occurrence of an error or an exception at the CM unit; and

based on a determination to shut down the CM unit, send, by the CD system to the CM unit of the mobile device, instructions to shut down the CM unit.