Further Interface Functions/ General

Storage/Internal Extinguishing Routines

By default, financial information is deleted 30 days after collection within the one-time access products.

The following data is stored for billing purposes in accordance with the statutory deadlines: Name, bank details, amount and purpose of use

Test bank

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 can be found in the interface description.  

Webhooks (optional)

If a successful creation of a transaction takes place, via the corresponding interface, within the respective merchant account, this event is transmitted via webhook. For this the necessary URL can be administered over the dealer portal or be handed over with the initial interface call. Further details regarding the transmitted information and signature can also be found in the interface documentation.

Security checks (optional)

In order to reduce the provider's risk of non-payment, the following security checks can be used optionally and configured individually:


  • maximum amount per transaction
  • Maximum number of transactions within defined period (customer-specific)
  • Maximum transaction volume within defined period (customer-specific)
  • Account balance check
  • Examination of earmarked revenues
  • Perform garnishment check
  • Review of chargebacks
  • Verification of outstanding payments
  • Checking low sales activity
  • IBAN blacklists/whitelists
  • 30 Days Check - if a payment has been made within the last 30 days, it will be credited to the bank statement.

As soon as one or more security checks are negative, the transaction will be rejected.

Sender (optional)

By transferring the name of the sender or a sender IBAN as part of the initial creation of a payment, a plausibility check is made to ensure that only payments via this account holder and/or this IBAN may be initiated.

Metadata (optional)

During the initial call, additional information can be transferred, which is then routed through the process to this transaction and stored together with the result. This information can then be queried via the interface or the dealer portal. Further details can also be found in the interface documentation.


Adjusted payment form (optional)

The payment form can be customized via the dealer portal. Further details on the range of functions can be found in the chapter Dealer Portal in the further course of the document. The adapted payment form can then be used both within the framework of the product payform and paycode. For both products, the adapted payment forms are controlled as part of the initial interface call. A separate default payment form can always be stored or the standard online transfer payment form can be used. For further details on how to use the standard payment form, see the interface documentation.

Account reconciliation (optional)

The merchant receiving account to be deposited via the merchant portal can be released for the incoming payment reconciliation (automatically or manually). This means that the incoming payments on this account are matched against the open incoming payments either cyclically or upon request. Each transaction can be assigned an appropriate status that indicates whether or not the payment has actually been received on the provider's account. It can happen that payments have been successfully initiated but are not executed by the bank.