Versioning and Change log

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

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

Versioning log

Breaking Changes

Version 3 is introduced to successfully process entity based billing

  • header change to "Content-Type: application/vnd.worldpay.tokens-v3+json"
  • You must now supply the new mandatory field merchant.entity in yourcreate token request

Breaking changes

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

  • header change to "Content-Type: application/vnd.worldpay.tokens-v2+json"

Note: You can find documentation for all versionshere.

Change log (Non-breaking changes)

We have now added paymentAccountReference (PAR) support fornetwork payment tokens.

We have increased the number of updates you can make to atokenin a rolling 30 day period, from 10 updates to 50.

You now receive a new fundingType field in yourtoken responsewith possible values of:

  • debit
  • credit
  • unknown

The default expiry date/time of a token is 7 days in Try and 4 years in the Live environment. This expiry is extended by 7 days or 4 years after any use of the token, if under half of the time remains on the token.

  • You can now createnetwork tokens and cryptograms. These can be used in card on file sale payments.

    You can also use these tokens across other service providers or payment gateways.

  • You can nowquerya card network token
  • we may now include bin and brand properties in our tokens response