By default, the financial information within the one-time access products (XS2A.pay and XS2A.risk) is deleted 30 days after collection. Independently of this, the financial information can also be deleted earlier with the help of an interface call by the provider. In addition, the name, the bank details, the amount and the intended use are stored for billing purposes in accordance with the statutory deadlines.
For the product with temporary access (XS2A.api), a time limit can be set for how long the transactions are to be stored.
With the help of this interface you can manage your own blacklist. At the center of this list is the respective IBAN. If an IBAN is part of your own so-called blacklist, then no transactions can be triggered by this IBAN via our system. The individual functions (add, delete and retrieve) are explained in more detail in the interface documentation.
With the help of this interface you can manage your own whitelist. In the center of this list is the respective IBAN. If an IBAN is part of your own whitelist, transactions triggered by such an IBAN can be handled separately. The individual functions (add, delete and retrieve) are explained in more detail in the interface documentation.
Our test bank can be used during the test or integration phase. In test mode, no actions can be performed with real bank accounts.
The test bank can be used to simulate the behaviour of the system during use. Further details, e.g. available bank details, accounts and commands, can be found in the interface description.
Events and Webhooks
Our system distinguishes between various events that can occur during the use of our interfaces and the system. A common example of such an event is the successful creation of a transaction, via the appropriate interface, within the respective provider account. The available events can be queried as a list via the interface (filtered). A detailed query for a specific event is also possible. Further information on the individual call variants and the scope can be found in the interface documentation.
The events are also transmitted via webhook. For this the necessary URLs can be administered over the customer portal. Further details regarding the transmitted information, signature and error handling can also be found in the interface documentation.
The interface can be used to query whether a bank is supported by our system or not. To do this, the relevant bank code or BIC must be used. As a result, in addition to the above-mentioned feature, information on this bank (name, city, country) is returned. Alternatively, a country-specific bank list can also be requested. Further details can be found in the interface documentation.