Skip to main content

Introduction

With debiX PUSH, SIX introduces a dedicated interface to inform issuers of key events across the payment ecosystem – for instance, updates to token data (e.g., Apple Pay wallet enrolment) or card-related operations (e.g., card blockings, feature toggles mutations).

The interface is built on IBM Message Queue (MQ) technology, a common used industry standard that enables near real-time delivery of notifications. Issuers are instantly notified when relevant events occur in connected platforms of stakeholders such as customer service center, schemes, merchants, wallet providers, or issuer platforms.

The interface supplies structured, card-related event information. Issuers can utilize this in various ways, for example:

  • Sending push notifications through the channels of the issuer (e.g., mobile apps, eBanking portals) to promptly inform cardholders.
  • Updating issuer’s backend systems, ensuring customer service teams have access to the latest data within the issuer’s infrastructure.

Setup​

To begin onboarding and configure the debiX PUSH interface, please reach out to your assigned Account Manager.

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.

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.

Versioning​

This is an ongoing specification and the services will be extended with increasing version. The aim is to release major versions at intervals of at least 12 months. However, this interval may be shortened for regulatory reasons.

Old major versions will be decommissioned 12 months after the introduction of the new major version.

The modules are versioned separately.