A method of binding non-transactable tokens to a user's account with a payment service provider device, comprising:
- receiving, by a token requestor device, a request to pay for a transaction using the user's account with the payment service provider device, the request specifying a funding instrument that is a payment source for the transaction, the payment service provider device being a source of the funding instrument, and the transaction being between a user device and a merchant application;
- receiving, by the token requestor device from the token service provider device, a common identifier (ID) corresponding to the funding instrument, the common ID being a first non-transactable token and associated with the merchant application and the user;
- generating, by the token requestor device, a payment token corresponding to the common ID and the funding instrument, the payment token being a second non-transactable token that maps to the common ID;
- binding, by the token requestor device, the user's account to the payment token and the common ID;
- receiving, by the token requestor device, a second request to pay for a second transaction between the user and the merchant application, the second request including a second payment token and transaction information, wherein the transaction information includes a first portion of the transaction information that is acceptable in a routing message field standard of a routing message standard used by a card network routing message, and wherein a second portion of the transaction information includes supplemental transaction data associated with the merchant application and that cannot be provided in a card network routing message that uses the routing message standard due to the supplemental transaction data not being acceptable in the routing message field standard;
- determining, by the token requestor device, whether the second payment token corresponds to the common ID;
- in response to a determination that the second payment token corresponds to the common ID, providing, by the token requestor device to the token service provider device, a request for a transactable token corresponding to the common ID, wherein the request includes the supplemental transaction data;
- receiving, by the token requestor device from the token service provider device, the transactable token;
- sending, by the token requestor device to the card network, a card network routing message that uses the routing message standard and that includes at least some of the first portion transaction information, and the transactable token;
- receiving, by the token service provider device, the transactable token from the card network;
- de-tokenizing, by the token service provider device, the transactable token to identify the funding instrument;
- determining, by the token service provider device, that the funding instrument is an account provided by the payment service provider device;
- determining, by the token service provider device, that the transactable token is associated with the supplemental transaction data previously received by the token service provider device;
- sending, by the token service provider, the at least some of the first portion transaction information and the supplemental transaction data in the same Application Programming Interface (API) call to the payment service provider device;
- completing, by the payment service provider device, the second transaction with the card network using only the at least some of the first portion transaction information, presented in the routing message standard;
- and
- providing the at least some of the supplemental transaction data to a user device associated with the user along with information associated with a completion of the second transaction with the card network.