Integration
Initiating a SOFORT payment request
The merchant begins by sending a SOFORT payment request to the BPE transaction gateway. The gateway processes this request and returns a response to the merchant.
- Without customer redirect: If the request is sent to a gateway that does not handle customer redirection, the response includes a redirect URL. The customer must be redirected to this URL manually.
- With customer redirect: If the original request redirects the customer to the Buckaroo public gateway, the transaction gateway automatically redirects the customer to the SOFORT payment page.
- Payment execution: Upon reaching the payment page, the customer inputs their banking details. Once these details are entered and verified, the payment is executed immediately. The customer is then redirected back to the merchant's website along with the payment result. Additionally, the payment engine sends a transaction push with the payment status.
Service codes and supported actions
Service codes:
The SOFORT service uses the following codes:
- Sofortueberweisung
- SofortDigital
Supported actions:
The service supports the following actions on the 'Web' channel:
- Pay
- Refund
Minimum transaction amount
A minimum transaction amount of β¬ 0,10 is required for a successful SOFORT transaction. Transactions below this amount will fail in both test and live modes.
Recurring payments
SOFORT transactions can serve as reference transactions for recurring SEPA Direct Debit payments. To enable this feature:
- Add the "StartRecurrent" parameter with the value "True" in your SOFORT API request.
- Once successful, recurring SEPA Direct Debit payments can be processed.
Refer to the SEPA Direct Debit documentation for details on the "PayRecurrent" request.
Test transactions
For test transactions, the maximum allowable transaction amount is β¬ 2501,-. Transactions exceeding this amount will fail.
Updated 7 days ago