No momento, esta página não está disponível em português
Payment-method icon

EPS for API only

Add EPS to an existing API-only integration.

Accept EPS payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.

Before you begin

These instructions explain how to add EPS to your existing API-only integration. The API-only integration works the same way for all payment methods. If you haven't done this integration yet, refer to our API-only integration guide.

Before starting your EPS integration:

  1. Make sure that you have set up your back end implementation.
  2. Add EPS in your test Customer Area.

Build your payment form for EPS

To show EPS in your payment form, you need to:

  1. Show a list of available banks to your shopper.
  2. After the shopper selects a bank, pass the corresponding Issuer ID value to your server. You'll need this to make a payment.

The available banks for EPS are different in the test and live environment:

Bank name Issuer ID
Bank Austria e6819e7a-f663-414b-92ec-cf7c82d2f4e5
BAWAG P.S.K. AG ba7199cc-f057-42f2-9856-2378abf21638
Dolomitenbank d5d5b133-1c0d-4c08-b2be-3c9b116dc326
Erste Bank und Sparkassen 3fdc41fc-3d3d-4ee3-a1fe-cd79cfd58ea3
Easybank AG eff103e6-843d-48b7-a6e6-fbd88f511b11
HYPO Tirol Bank AG 6765e225-a0dc-4481-9666-e26303d4f221
Posojilnica Bank eGen 65ef4682-4944-499f-828f-5d74ad288376
Raiffeisen Bankengruppe Österreich ee9fc487-ebe0-486c-8101-17dce5141a67
Schoellerbank AG 1190c4d1-b37a-487e-9355-e0a067f54a9f
Sparda Bank Wien 8b0bfeea-fbb0-4337-b3a1-0e25c0f060fc
Volksbanken e2e97aaa-de4c-4e18-9431-d99790773433
Volkskreditbank AG 4a0a975b-0594-4b40-9068-39f77b3a91f9

We provide logos for EPS and the issuing banks, which you can use on your payment form. For more information, refer to Downloading logos.

You can also get the issuer list from the /paymentMethods response, as explained in the API-only integration guide.

In your /paymentMethods request, specify:

The list of issuing banks are included in the object with type: eps.

Make a payment

In your /payments request, specify:

  • paymentMethod.type: eps
  • paymentMethod.issuer: The EPS issuer value of the shopper's selected bank. For example, Dolomitenbank.
  • returnUrl: The URL where the shopper will be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters.

The /payments response contains an action object with the information needed to redirect the shopper.

Handle the redirect

  1. To complete the payment, redirect the shopper to the action.url returned in the /payments response.

When using the HTTP GET method:
For security reasons, when displaying the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.

  1. After the shopper is redirected back to your website, check the payment result by making a POST /payments/details request, specifying:

    • details: Object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.

You receive a response containing:

  • resultCode: Use this to present the result to your shopper.
  • pspReference: Our unique identifier for the transaction.

Present the payment result

Use the  resultCode that you received in the /payments/details response to present the payment result to your shopper.

The resultCode values you can receive for EPS are:

resultCode Description Action to take
Authorised The payment was successful. Inform the shopper that the payment has been successful.
You will receive the funds in 2 days.
Cancelled The shopper cancelled the payment while on their bank's website. Ask the shopper whether they want to continue with the order, or ask them to select a different payment method.
Error There was an error when the payment was being processed. Inform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.
Pending or
The shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the EPS payments network to confirm this. Inform the shopper that you've received their order, and are waiting for the payment to be completed.
You will receive the final result of the payment in an AUTHORISATION webhook.
Refused The payment was refused by the shopper's bank. Ask the shopper to try the payment again using a different payment method.

If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment:

eventCode success field Description Action to take
AUTHORISATION false The transaction failed. Cancel the order and inform the shopper that the payment failed.
AUTHORISATION true The shopper successfully completed the payment. Inform the shopper that the payment has been successful and proceed with the order.

Recurring payments

We support recurring transactions for EPS through SEPA Direct Debit. To make recurring payments, you need to:

  1. Create a shopper token.
  2. Use the token to make future payments for the shopper.

Create a token

We strongly recommend that you request explicit permission from the shopper if you intend to make recurring SEPA payments. Being transparent about the payment schedule and the charged amount reduces the risk of chargebacks.

To create a token, include in your /payments request:

  • storePaymentMethod: true
  • shopperReference: Your unique identifier for the shopper (minimum length three characters).

When the payment has been settled, you receive a webhook containing:

  • originalReference: The pspReference of the initial payment.
  • pspReference: This is the token that you need to make recurring payments for this shopper.

Make sure that your server is able to receive RECURRING_CONTRACT as part of your standard webhooks. You can enable the RECURRING_CONTRACT event code in the webhook settings page.

Make a payment with a token

To make a payment with the token, include in your /payments request:

  • paymentMethod.storedPaymentMethodId: The pspReference from the RECURRING_CONTRACT webhook.

You can also get this value by using the /listRecurringDetails endpoint.

  • shopperReference: The unique shopper identifier that you specified when creating the token (minimum length three characters).
  • shopperInteractionContAuth.
  • recurringProcessingModel: Subscription or UnscheduledCardOnFile.

For more information about the shopperInteraction and recurringProcessingModel fields, refer to Recurring transaction types.

Test and go live

Check the status of EPS test payments in your Customer Area > Transactions > Payments.

Before you can accept live EPS payments, you need to submit a request for EPS in your live Customer Area.

See also