Article summary

        The merchant starts by sending the request for a Giropay payment to a BPE transaction gateway. The gateway will then process the request and send 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 Giropay page at his bank by the transaction gateway. Once the customer reaches this page, he can enter his banking information and verify 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 Giropay service uses the service code: giropay.

        The Giropay service supports the following actions: Pay, Refund. For both actions the channel "WEB" is supported.

        Recurring payments

        It is also possible to use a Giropay transaction as a reference transaction for recurring SEPA Direct Debit transactions. To do this, add the basic parameter "StartRecurrent" with value "True" to your Giropay API request. Once the payment has been successfully completed by the customer and the money has been received by Buckaroo (the latter can take up to a week), a recurring SEPA direct debit request can be performed and accepted. We advise to wait at least a week before performing a recurring payment request. In any case, if the request returns a failure (because the money hasn't arrived yet) it should be performed again later in order for it to be accepted and executed. Please see the SEPA Direct Debit section for an explanation of the "PayRecurrent" request.

        Was this article helpful?

        What's Next