Integration

Overview

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.

• Customer Redirect:
  • 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 Giropay page at their bank by the transaction gateway.

Once the customer reaches this page, they can enter their banking information and verify the payment. 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: giropay
• Supported Actions:
  • Pay: Use channel "WEB".
  • Refund: Use channel "WEB".

Recurring Payments

It is 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 the value True to your Giropay API request.

Once the payment has been completed by the customer and the money has been received by Buckaroo (which can take up to a week), a recurring SEPA direct debit request can be performed and accepted. It is advised to wait at least a week before performing a recurring payment request. If the request returns a failure because the money hasn't arrived yet, it should be performed again later for it to be accepted and executed.

Please see the SEPA Direct Debit section for an explanation of the PayRecurrent request.