Skip to main content

Architecture

An issuer with an e-banking system or an own mobile application can use the debiX API to integrate debit and mobile services into their multichannel application. The responsibilities are assigned as follows:

  • SIX provides the debit and mobile services via the debiX API.
  • SIX guarantees the client authentication and the segregation of the clients' data.
  • The issuer develops their own mobile application and manages the app within the app store.
  • The issuer manages the mobile users with their own IAM solution.
  • The issuer either implements their own 3DS authentication or reuses the 3DS authentication provided by SIX.

Since there is no real-time synchronization between Worldline DEBOL XML and SIX debiX, issuers are advised to keep a distance of one minute between a card creation or manipulation via Worldline DEBOL XML and an operation on the same card via the debiX API.

system-overview.png

Performance Target​

debiX API is designed to achieve a response time of less than 2 seconds for simple operations and less than 5 seconds for complex operations in 95% of cases.

The response times refer to the end-to-end processing time, including all involved backend and downstream systems.

Simple operations typically include read-only requests, such as:

  • Retrieve encrypted card data
  • Retrieve authorization code
  • Retrieve card Messages that debiX sends to the issuer via the message broker (MQ) are delivered in near real time.

Complex operations typically include write transactions, such as:

  • Block / Unblock a card
  • Register a card for 3DS
  • Set a new PIN

Requests per Minute per Bank​

The SIX API Gateway is configured to allow 1,000 requests per minute per bank.

It is the responsibility of the bank to appropriately allocate this capacity between daily business transactions and any bulk changes that are not submitted via debiX BULK.