Learn about EPS, a common payment method in Austria.

EPS and Giropay used to be payment methods only for their respective 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 typeOnline banking
Customer currenciesEUR
Processing currenciesEUR
One-time PaymentYes

General flow

The status of the transaction is pending during redirect.


As soon customer completes the payment:

  1. Customer is redirected to the url_return page sent in the original request.
  2. An asynchronous notification to the notification_url is sent in the original request which can be used to update the shops database.
  3. When the bank transfer from the customer bank reaches the bank account a second notification is sent to the notification_url errorcode=0&payment_state=credited

Step 1. Make a transaction request

From your server, make a POST /payment_preauthorize request.

POST https://sandbox.payabl.com/pay/backoffice/payment_preauthorize

Include in request:

merchantid40 charactersMerchant identification number assigned during account creation
orderidmax. 40 charactersThe field orderid is optional and exclusively for the merchants' convenience
amountdigits only, either no decimals or two decimal places (e.g. 8 or 8.50)Transaction’s total amount that will be deducted from the customer
currency3 characters. ISO 4217The currency field contains the alpha-3 currency code for the transaction. Links to ISO
payment_method118payabl. Payment methods IDs
signature40 charactersSignature Calculation
country3 characters. ISO 3166-1 alpha-3Customer countries. List of official country codes
emailmax. 50 charactersCustomer email. An RFC 822 compliant email address
firstnamemax. 50 charactersFirst name of the customer
lastnamemax. 50 charactersLast name of the customer
url_successmax. 255 characters starting with http or httpsURL for customer redirection to success page
url_returnmax. 255 characters starting with http or httpsURL for customer redirection to failed page

You can see a full list of parameters in Pre-Authorization.

Request example:

merchantid=gateway_test&orderid=Payabl-Test&amount=19.99&currency=EUR&payment_method=118&language=en&[email protected]&firstname=John&


Public Sandbox information

Do not use your personal email address, Order ID with sensitive information, real customer details and credit card data in the public Sandbox. For email field you may use [email protected].


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

Step 2. Handle the redirect

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

Response example:


Response fields reference:

transactionidpayabl. internal transaction id. Please use this transaction id when referring to the transaction in communications with the payabl. team
transidThe same as transactionid
statusTransaction error code
errormessageBrief explanation of transaction decline reason (empty on success)
errmsgThe same as errormessage
amountTransaction amount
priceThe same as amount
currencyTransaction currency
orderidOptional transaction identifier given by the merchant
redirect_urlURL for customer redirection to finalize the payment (URL encoded)
user_idPayment system user identifier

Step 3. Receive the final status

Once the customer completes the payment, we will send a notification with the transaction's status to the notification_url specified by you.

url_return and notification_url should be passed by you in the Pre-authorization request.

Alternatively, you can communicate a notifciation_url to be used by default to payabl. technical team. By doing so, you won't need to send it in every request.

EPS notifications contain 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, either provided in the request body or configured when the merchant account was created.

Notification example - Accepted Capture:


Notification example - Successful Capture:


Notification fields reference:

transactionidpayabl. internal transaction id. Please use this transaction id when referring to the transaction in communications with the payabl. team
typeTransaction type
errorcodeTransaction error code (0 for success)
errormessageBrief explanation of transaction decline reason (empty on success)
amountTransaction amount
orderidOptional transaction identifier given by the merchant
securitySignature to verify the authenticity of the notification. You can find more information here
timestampNotification timestamp
payment_stateTransaction acceptance state as described above

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

bank_countryCustomer bank country in ISO-3166 alpha-2 format
bicCustomer bank BIC
payment_systemIdentify if EPS or Giropay was used
account_holderAccount holder name
ibanCustomer IBAN

Notification example - Accepted Capture (additional parameters):


Notification example - Successful Capture (additional parameters):


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.


In case 15 days pass and payabl. didn't receive any funds from an issuer, the transaction will be failed automatically. You will receive a notification update.


Below you will find additional information on some common declines that can occur during an EPS payment attempt.

Redirect timeout
In case the customer wasn't redirected to the EPS interface to complete the payment within 1 hour and the redirect link got expired, the transaction will be failed with error 021 – Transaction not completed. We will post a notification to your notification_url.


Transaction aborted
In case the customer has been successfully redirected to the EPS interface, but aborted the payment in the process, pressed the browser back button, or performed other action that interrupted the process – the transaction will be failed and we will post a notification containing error code -1315 – Response failed to your notification_url.


Funds not arriving within the waiting period

As it was described above, in cases where the transaction has been in not_credited_yet payment state for 15 days and payabl. still haven't received the funds from the customer's bank, the transaction will be failed automatically with error -6211 – No confirmation from bank, triggering a notification to your notification_url.


Our Technical Support team is there to help you:
Email: [email protected]
Available Monday – Friday between 09:00 and 17:00 CET/CEST