Instant Bank Transfer

Learn how to accept open banking payments

Open banking is also known as "open bank data." Open banking is a banking practice that provides third-party financial service providers open access to consumer banking, transaction, and other financial data from banks and non-bank financial institutions through the use of application programming interfaces (APIs).
You can now accept SEPA bank transfers from European banks from your customer using our new OpenBanking PIS API.


  • Lower transaction fees

  • Accessible to customers who do not have a credit card/debit card

  • No Chargebacks as payment is initiated by customer and complies with PSD2 SCA

  • No instant final confirmation of funds, sometimes final confirmation can take 3-4 days

  • Payment guarantee only after final confirmation notification

Payment typeBank transfer
MarketAustria, Belgium, Germany, Estonia, Spain, France, Hungary, Italy, Latvia, Lithuania, Luxembourg, Netherlands, Poland, Portugal
Customer currenciesEUR, GBP
Processing currenciesEUR, GBP

Your customer based on the country you send in the request is presented with a list of the supported banks. Once the bank is selected, the customer is redirected to log in to their Online Banking system.

The customer then complying with PSD2 SCA authorizes a SEPA bank transfer to our bank account.

General flow

POST Request -> to /payment_preauthorize
<- Response (direct, synchronous) with status=2000&errormessage=pending and redirect_url
Customer is redirected to redirect_url (Open banking URL)
<- Callback (asynchronous) with errorcode=0&payment_state=not_credited_yet to notification_url
<- Callback (asynchronous) with errorcode=0&payment_state=credited to notification_url

Customer flow

The customer needs to select the country and the bank he plans to use.


payabl. open banking widget

After the user will see payment information that he needs to confirm


Transaction details

The widget will display the status of the transaction.


Transaction successful

Step 1. Make a transaction request

From your server, make a POST /payment_preauthorize request.


The process flow of this payment system is the same as the 3DSecure transaction procedure. Please note the following exceptions:

  1. For open banking transactions, we don’t need param_3d parameter.
  2. The redirect URL is provided in redirect_url, instead of url_3ds (used in step 2 and step 3)
  3. Only Pre-Authorization interface should be used for sending transactions.
  4. Merchant would be notified on the notification URL about the accepted, success and the failed transaction, capture may remain in the accepted state until credited or not_credited notification has been received from the
  5. Please pay special attention to the following pre-authorization interface parameters:
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_method123payabl. Payment methods IDs
signature40 charactersSignature Calculation
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 httpsSuccess transaction URL
url_failedmax. 255 characters starting with http or httpsFailed transaction URL
url_returnmax. 255 characters starting with http or httpsURL for customer redirection

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=123&language=en&customerip=[email protected]&
firstname=John&lastname=Doe&zip=60314&street=Hanauer Landstrasse&house=182c&city=Frankfurt am Main&country=DEU&url_return=https://yourshop.example/thank_you&


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
payment_methodPayment method ID
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

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 are supposed 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.

payabl. 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. The notification URL is the URL that was provided when the merchant account was created.

You will receive a notification from payabl. regarding the status update of the transaction. If payabl. received funds from the issuer for the transaction you will get the appropriate notification.

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
payment_methodPayment method ID
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


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.

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