DOCUMENTATION
🔗 SupportRecipient login

Account number tokenization FAQs

How do I know if an account number has been tokenized?

An account number that has been tokenized can be identified within the /payment-networks endpoint response. When tokenized, the value for the field identifierType is "TOKENIZED_ACCOUNT_NUMBER."

Will end-users not be able to identify their account due to the tokenized values?

Data elements such as masked account numbers/last four will still be available through Akoya APIs even if the account number used to initiate a payment is tokenized. The masked account numbers/last four can be displayed to the end-user; the tokenized account does not need to be displayed (we can compare this to the way card tokens are used today, e.g., Apple Pay).

Are we able to identify existing mandates based on the returned tokens or do we need to replace existing mandates?

If you do not want to use an existing mandate and if you are looking to retrieve payment credentials from the API, then yes, you will need to replace the mandate for the tokenized account number.

What is the data format of a tokenized account number?

Tokenized account numbers follow the same format as real account numbers in order to be compatible with Nacha files without any changes. In other words, tokens “look and feel” like real account numbers. This is true for tokens obtained through The Clearing House or providers who use TANs.

Length of an tokenized account number: 1 - 17.

How will the tokenized account number work with our payment processor/provider?

You will be able to work with your payment processor (e.g., Dwolla or Stripe) without any changes. Because tokenized account numbers are compatible with the Nacha/RTP files, there are no changes required in order to be able to use them. The detokenization either happens “in-transit” (for The Clearing House tokens) or at the bank. Therefore, your ACH provider can accept tokenized account numbers without any additional work. For more detail on this please refer to the “Tokenization within a payment flow” section of this paper.

What is the planned development/adoption of tokenization over the near future?

When possible, Akoya will make the real account number available through our Payments product (/payment-networks endpoint); this is the case for many providers currently live on our network. When the provider requires account numbers to be tokenized, Akoya will share the tokens through the same Payments product (/payment-networks endpoint).

Tokenized account number help de-risk the entire ecosystem. Akoya is working with multiple financial institutions to increase the adoption of tokenized account numbers. Therefore, the number of data providers opting for this approach will increase over time.

What is the relationship between the dedicated routing numbers and the actual routing numbers?

The term “dedicated routing number” refers to an ABA routing number that a financial institution reserves for tokenized account numbers only. In other words, the “dedicated” routing number is a real ABA routing number. This is a pre-requisite for a financial institution to use the tokenization solution. Typically, a financial institution can repurpose a routing number they have “on the shelf” or they can get a new one from ABA.

Is it possible that one dedicated routing number is used by multiple institutions?

No, it is unique for each participating institution.

Is it possible that one real routing number can map to multiple dedicated routing numbers?

In theory, yes, a financial institution can use more than one dedicated routing number. However, The Clearing House (TCH) recommends only maintaining a single real routing number to dedicated number pairing.

Are all routing numbers of one institution mapped to the same one dedicated routing number?

The Clearing House (TCH) does not have limitations on this and it is up to the financial institutions to decide. However, TCH recommends that financial institutions only maintain a single real routing number to dedicated number pairing.

On which payment rails can I use the tokenized account numbers?

The issued tokenized account numbers are compatible with the ACH (both EPN and FedACH) and RTP payment rails. Both ACH and RTP networks will be able to de-tokenize and process the tokenized account numbers. Please note that having a tokenized account number does not mean that the account is enabled to receive RTP payments.

The issued tokenized account numbers are currently not compatible with Wire, FedNow, or checks (e.g., check printing services). For these payment rails, e.g., Wire, if the account number is available through the Payments product, Akoya would not return a tokenized account number.

Is the suspension of a tokenized account number immediate?

Yes, suspending a tokenized account number is immediate. Once a tokenized account number is suspended, any future payment made using the token will be declined.

If a user revokes their data access consent, will that revocation also suspend any associated tokens?

Yes, when a user revokes their consent to a third party to access data, the revocation will automatically suspend any tokenized account numbers issued to that third party.

Can I use services provided by the likes of Early Warning or GIACT to verify the tokenized account numbers?

We do not recommend that. Because the tokenized account numbers are unique to a data recipient, these services wouldn’t recognize them and may flag the accounts unnecessarily.

For account verification purposes, our Payments product returns data retrieved directly from the financial institution and are validated by default. Additional Akoya products can provide more details as needed, such as account status, current balance, account ownership, and customer information (see our Balances and Customers products).

For more information, please contact us.


Last Updated: 8/31/2023