Menu

Versioning and Change log

This log details any breaking and non-breaking API changes we have released for our Verified Tokens service.

Prerequisite: Make yourself familiar with ourAPI Principlesto ensure a resilient integration.

Versioning log

Version 3 was introduced to include card data in theVerified Tokens response.

Version 2 was introduced to cater for downstream cross service integration.

  • no changes to our Verified Tokens API

Note: You can find documentation for all versionshere.

Change log (Non-breaking changes)

  • In version 3, we're now creating unverified token in case of account verification failure and return code and description as part of theNot Verified Token response.

  • In version 2, we're now creating unverified token href in case of account verification failure and return code and description as part of theNot Verified Token response.

  • In version 1, we're now creating unverified token href in case of account verification failure as part of theNot Verified Token response.

You can now optionally send narrative as part of the Verified Tokens request.