Integration

EPS Payment Process

An EPS payment can be initiated by sending the request to a BPE transaction gateway. The gateway processes the request and sends a response to the merchant.

• If the request is sent to a gateway without a customer redirect, the response will contain a redirect URL to which the customer must be redirected.
• If in the original request the customer was redirected along to the Buckaroo public gateway, the customer is automatically redirected to the EPS payment page by the transaction gateway.

Once the customer reaches this page, they can enter their banking information. Once these have been entered and verified, the payment is executed immediately, and the customer will be redirected back to the merchant's website along with the result. Additionally, the Payment Engine will also perform a Transaction Push, updating the status of the payment.

Service Codes and Actions

• Service Code: eps
• Supported Actions:
  • Pay: Use channel "Web".
  • Refund: Use channel "Backoffice".

Recurring Payments

It is also possible to use an EPS transaction as a reference transaction for recurring SEPA Direct Debit transactions. To do this, add the basic parameter StartRecurrent with the value True to your EPS API request. Once successful, you can perform a recurring SEPA direct debit transaction.

However, note that we do not always receive the account information from EPS. If this information is not received, a SEPA Direct Debit cannot be performed based on the EPS transaction. Therefore, it is advised to ensure you are informed if your SEPA Direct Debit API request fails. Please see the SEPA Direct Debit section for an explanation of the PayRecurrent request.