Learn about Giropay, a common payment method in Germany.

Giropay was a payment method only for their national markets. Both reach out to establish online payments in e-commerce in Europe based on the approved high-security standards of online banking.

Because of that, eps and giropay interlink their systems for interoperability. Merchants can now receive payments from customers from Germany using the already implemented eps-interface without technical effort.

Payment type Online banking
Market Germany
Customer currencies EUR
Processing currencies EUR
Settlement currencies EUR
One-time Payment No
Refunds No

Step 1. Make a transaction request

From your server, make a POST /payment_preauthorize request.


Include in request:

  • merchantid: The merchant identification number.
  • orderid: The field orderid is optional and exclusively for the merchant's convenience.
  • amount: The amount field contains the transaction’s total amount. This is the amount that will be transmitted to the authorizing system.
  • currency: The currency field contains the alphanumeric currency code for the transaction, according to ISO 4217, e.g. EUR.
  • payment_method: The payment method id - 118.
  • signature: The signature field contains a 40-figure hexadecimal value. This signature value is a checksum designed to protect the merchant account from unauthorized access.
  • country: Customer country in ISO Alpha-3 format. Supported countries: AUT, DEU.
  • url_return: link where customer will be redirected after payment is complete or cancelled. This url will receive a response from payabl with transaction details.
  • email: The customer's email address.
    You can see a full list of parameters in Pre-Authorization .


Redirection to url_return does not confirm that the transaction is successful. Always check the transaction via notification_url or use diagnose interface to get the final status of the transaction.

Request example


Giropay contains an additional notification parameter which is payment_state, which could contain the following values:

  • not_credited_yet: Capture - Accepted.
  • credited: Capture - Successful.
  • not_credited: Capture - Failed.
    Each state change would trigger a notification to the notification URL, notification URL is the URL that was provided when the merchant account was created.

Step 2. Handle the redirect

To complete the payment, you need to redirect the customer to the correct URL in the response.



Notification example - Accepted Notification


Notification example - Successful Notification


Additional Customer details can be added to both callbacks. Please contact Tech support to enable them:

  • bank_country (alpha2 format)
  • bic
  • payment_system
  • account_holder
  • iban

When the customer finished or canceled the payment, he will be redirected back to url_return, provided by you in the initial request to payment_preauthorize. After that, you will receive a notification, posted to notification_url, with the final transaction status, which you suppose to use to update your system.


Notification URL can be configured by our tech support team in your account on our side,
or you can send it as a parameter notification_url in the initial request to payment_preauthorize.


Giropay supports refunds and can be initiated only on a successful captured transaction.
The request will send a credit note to the authorization system after the customer has already been charged. The refund amount will be credited to the customer and the merchant’s account will be charged.

The refund can be done in two ways:

  • Through API integration
  • Through payabl. dashboard

If you have API integration, you can check more in our documentation Refund.