Frequently Asked Questions
You have general questions? We have collected the most frequently asked questions and provide you with the answers here. If you have further questions, please do not hesitate to contact our Support Team.
How do the individual payment methods work?
We have prepared a payment method overview of the functions, features and add-ons for the respective payment methods.
How does the onboarding work?
The onboarding process consists of three steps: registration, KYC check and contract conclusion. A detailed onboarding guide can be found in the merchant documentation.
What does the respective transaction status mean?
You can find a detailed overview of all transaction statuses in our API Documentation.
How can I protect myself when using SEPA direct debit or purchase on account?
At best, these payment methods can be secured with appropriate risk management, including address, identification and score checks.
Who pays for bounced SEPA direct debits and returned direct debits?
In case a SEPA direct debit bounces or is subject to a chargeback the merchant will be charged additional fees by the bank. The level of charges depends on the contractual agreement between merchant and bank.
Who is responsible for sending dunning notices for SEPA direct debits or purchases on account?
This depends on the payment model and the provider. As a rule of thumb, however, the merchant is usually responsible for billing, accounts receivable management and dunning.
In the case of receivables management using YFS's purchase of residual debt, the merchant usually has to issue dunning notices independently. In factoring models, the factoring company is responsible for accounts receivable management and dunning.
What do the transaction statuses "registered", "started", "pending" and "successful" mean for SEPA direct debits?
Registered: The SEPA mandate has been retrieved.
Started: The payment is created in the payment system (after the payment call).
Pending: The payment is transmitted to the bank.
Successful: The payment has been marked complete (either manually in the dashboard or reconciled via EBICS CAMT 53)
Rejected: The payment has been rejected by the risk check or the direct debit has bounced at the bank.
Where can I find test data?
All test data for testing payment methods in the Test Dashboard can be found in our API Documentation.
You have technical questions? We have collected the most frequently asked questions and provide you with the answers here. If you have further questions, please do not hesitate to contact our Tech Helpdesk.
What do the individual API error codes mean?
An overview of all possible API error codes and their meaning can be found in our API Documentation.