Article summary

        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 payment page at EPS by the transaction gateway. Once the customer reaches this page, he can enter his banking information. Once these have been entered and verified the payment is executed immediately and the customer will be redirected back to the merchant website, along with the result. Additionally, the Payment Engine will also perform a Transaction Push, with the status of the payment.

        Servicecodes and actions

        The EPS service uses the servicecode: eps

        The EPS service supports the following actions: Pay, Refund. Use channel "Web" for action Pay and channel "Backoffice" for action Refund.

        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 value "True" to your EPS API request. Once successful, you can perform a recurring SEPA direct debit transaction. However, we do not always receive the account information from EPS. If we have not received this information, a SEPA Direct Debit cannot be performed based on the EPS transaction. Therefore, it is advised to make sure you are informed in some way if your SEPA Direct Debit API request fails. Please see the SEPA Direct Debit section for an explanation of the "PayRecurrent" request.

        Was this article helpful?

        What's Next