Skip to main content

Introduction

The debiX API offers debit and mobile services for debit card issuing banks.

These services enable the issuer's e-banking system and the mobile application to retrieve information about debit cards whether digitized or not.

This is an ongoing specification and the services will be extended with increasing version.

Card Identifiers​

SIX has introduced the CardToken as a full equivalent of the ShortCardId and the CardInstanceToken as a full equivalent of the CardId. While the ShortCardId and CardId contain the card number, the CardToken and CardInstanceToken are pure technical ids referencing a card. The CardToken together with the CardExpiry and CardSequenceNumber are equivalent to a CardInstanceToken.

If the issuer references cards only via CardToken and CardInstanceToken, he can instruct the SIX Client Delivery to omit the CardId and ShortCardId in the push messages.

Release Process​

The following principles are applied as a standard practice:

  • debiX API uses semantic versioning.
  • In general, a new debiX API major version is released approximately every 12 months. As an exception, the next major release is planned after the processing platform migration and therefore does not follow the regular release cycle.
  • New major versions are announced approximately 3 months in advance.
  • Following the release of a new major version, the preceding version remains in operation for 12 months and is marked as deprecated. During this period, banks are required to migrate to the new version.
  • In general, a new debiX API minor version is released approximately every month and does not contain any breaking change.

Releaselifecycle.png