Issued: 21st February 2023 | TB-022123
Token.io has introduced auto redeem for Single Immediate Payments (SIP) for banks that require a 2-step initiated payment flow.
For banks using 2-step payment flows, a payment request is split into two parts:
end-user (PSU) authentication
payment execution
Previously, Token.io didn't support the ability for TPPs to automatically redeem tokens for 2-step SIP. TPPs had to explicitly confirm authentication from the PSU with the bank.
This meant that TPPs had to handle this additional layer of complexity and have a clear understanding of which banks used 2-step flows in order to manage payments.
In addition, 2-step flows add a potential point of failure between Token.io and TPPs.
Using auto redeem, TPPs now have the option to automatically redeem authentication tokens for 2-step flows, avoiding the need to confirm authentication with the bank.
This is an optional change that will only affect you if you're using Single immediate Payments (SIP) services for banks that require 2-step payment initiation flows as part of Token.io's Payment Initiation Services (PIS).
If you're currently using 2-step payments and don't wish to implement this change, you don't need to do anything.
If you're a provider of Token.io services to TPPs, you can choose to implement this change on a TPP-by-TTP basis.
It's also possible to support both 1-step and 2-step flows within the same implementation, if required.
This change doesn't affect you if you're using Token.io's Account Information Service (AIS).
If, as an existing customer, you'd like to make use of the auto redeem feature for 2-step payments, contact your Implementation Manager or Support and they will enable it for you.
New customers will have the auto redeem feature turned on by default. If you'd like this feature turned off, in order to use 2-step payments without auto redeem, please contact your Implementation Manager or .
The POST /transfers call is no longer required when the auto redeem flag is turned on.
You'll continue to receive the transferId when you make the GET /token-requests/{tokenRequestId}/result call.
For assistance with the above and other operational aspects of the Token.io Account-to-Account Infrastructure, please contact Token Support.