Accept an EPS payment
Learn how to accept EPS, a common payment method in Austria.
Caution
The content of this section refers to a Legacy product. You should use the Accept a payment guide for the most recent integration path instead. While Stripe still supports this product, this support might end if the product is deprecated.
EPS is a single use payment method where customers are required to authenticate their payment. Customers pay with EPS by redirecting from your website, authorising the payment, then returning to your website where you get immediate notification on whether the payment succeeded or failed.
Note
Your use of EPS must be in accordance with the EPS Terms of Service.
Set up StripeServer-side
First, you need a Stripe account. Register now.
Use our official libraries for access to the Stripe API from your application:
Create a PaymentIntentServer-side
A PaymentIntent represents your intent to collect payment from a customer and tracks the lifecycle of the payment process.
Create a PaymentIntent
on your server and specify the amount
to collect, and the eur
currency (EPS doesn’t support other currencies). If you have an existing Payment Intents integration, add eps
to the list of payment method types.
Retrieve the client secret
The PaymentIntent includes a client secret that the client side uses to securely complete the payment process. You can use different approaches to pass the client secret to the client side.
Collect payment method detailsClient-side
You’re ready to collect payment information on the client with Stripe Elements. Elements is a set of pre-built UI components for collecting payment details.
A Stripe Element contains an iframe that securely sends the payment information to Stripe over an HTTPS connection. The checkout page address must also start with https:// rather than http:// for your integration to work.
You can test your integration without using HTTPS. Enable it when you’re ready to accept live payments.
Set up Stripe Elements
Submit the payment to StripeClient-side
Rather than sending the entire PaymentIntent object to the client, use its client secret. This is different from your API keys that authenticate Stripe API requests. The client secret should be handled carefully as it can complete the charge. Don’t log it, embed it in URLs, or expose it to anyone but the customer.
When your customer submits a payment, Stripe redirects them to the return_
and includes the following URL query parameters. The return page can use them to get the status of the PaymentIntent so it can display the payment status to the customer.
When you specify the return_
, you can also append your own query parameters for use on the return page.
Parameter | Description |
---|---|
payment_ | The unique identifier for the PaymentIntent . |
payment_ | The client secret of the PaymentIntent object. For subscription integrations, this client_secret is also exposed on the Invoice object through confirmation_ |
When the customer is redirected back to your site, you can use the payment_
to query for the PaymentIntent and display the transaction status to your customer.
You can find details about the bank account the customer used to complete the payment on the resulting Charge under the payment_method_details property.
{ "charges": { "data": [ { "payment_method_details": { "eps": { "bank": "bank_austria", "verified_name": "JENNY ROSEN" }, "type": "eps" }, "id": "src_16xhynE8WzK49JbAs9M21jaR", "object": "source", "amount": 1099, "client_secret": "src_client_secret_UfwvW2WHpZ0s3QEn9g5x7waU",
Test your integration
Select any bank in the EPS bank list with your test API keys. After confirming the payment, you’re redirected to a test page with options to succeed or fail the payment. You can test the successful payment case by authenticating the payment on the redirect page. The PaymentIntent will transition from requires_
to succeeded
.
To test the case where the user fails to authenticate, select any bank with your test API keys. On the redirect page, click Fail test payment. Your PaymentIntent will transition from requires_
to requires_
.
Bank values
Bank name | Value |
---|---|
Ärzte- und Apothekerbank | arzte_und_apotheker_bank |
Austrian Anadi Bank AG | austrian_anadi_bank_ag |
Bank Austria | bank_austria |
Bankhaus Carl Spängler & Co.AG | bankhaus_carl_spangler |
Bankhaus Schelhammer & Schattera AG | bankhaus_schelhammer_und_schattera_ag |
BAWAG P.S.K. AG | bawag_psk_ag |
BKS Bank AG | bks_bank_ag |
Brüll Kallmus Bank AG | brull_kallmus_bank_ag |
BTV VIER LÄNDER BANK | btv_vier_lander_bank |
Capital Bank Grawe Gruppe AG | capital_bank_grawe_gruppe_ag |
Dolomitenbank | dolomitenbank |
Easybank AG | easybank_ag |
Erste Bank und Sparkassen | erste_bank_und_sparkassen |
Hypo Alpe-Adria-Bank International AG | hypo_alpeadriabank_international_ag |
HYPO NOE LB für Niederösterreich u. Wien | hypo_noe_lb_fur_niederosterreich_u_wien |
HYPO Oberösterreich, Salzburg, Steiermark | hypo_oberosterreich_salzburg_steiermark |
Hypo Tirol Bank AG | hypo_tirol_bank_ag |
Hypo Vorarlberg Bank AG | hypo_vorarlberg_bank_ag |
HYPO-BANK BURGENLAND Aktiengesellschaft | hypo_bank_burgenland_aktiengesellschaft |
Marchfelder Bank | marchfelder_bank |
Oberbank AG | oberbank_ag |
Raiffeisen Bankengruppe Österreich | raiffeisen_bankengruppe_osterreich |
Schoellerbank AG | schoellerbank_ag |
Sparda-Bank Wien | sparda_bank_wien |
Volksbank Gruppe | volksbank_gruppe |
Volkskreditbank AG | volkskreditbank_ag |
VR-Bank Braunau | vr_bank_braunau |