Accept an EPS payment

Learn how to accept EPS, a common payment method in Austria.

EPS is a single use payment method where customers are required to authenticate their payment. Customers pay with EPS by redirecting from your website, authorizing the payment, then returning to your website where you get immediate notification on whether the payment succeeded or failed.

Your use of EPS must be in accordance with the EPS Terms of Service.

Set up Stripe
Server-side

First, you need a Stripe account. Register now.

Use our official libraries for access to the Stripe API from your application:

Terminal

# Available as a gem
sudo gem install stripe

Gemfile

# If you use bundler, you can add this line to your Gemfile
gem 'stripe'

Create a PaymentIntent
Server-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.

Terminal

curl https://api.stripe.com/v1/payment_intents \
  -u sk_test_4eC39HqLyjWDarjtT1zdp7dc
: \
  -d "amount"=1099 \
  -d "currency"="eur" \
  -d "payment_method_types[]"="eps"

Instead of passing the entire PaymentIntent object to your app, return its client secret. The PaymentIntent’s client secret is a unique key that lets you confirm the payment and update payment details on the client, without allowing manipulation of sensitive information, like the payment amount.

You can retrieve the client secret from an endpoint on your server using the browser’s fetch function on the client side. This is generally the best approach when your client side is a single-page application, especially one built with a modern frontend framework such as React. This example shows how to create the server endpoint that serves the client secret:

main.rb

get '/secret' do
  intent = # ... Create or retrieve the PaymentIntent
  {client_secret: intent.client_secret}.to_json
end

This example demonstrates how to fetch the client secret with JavaScript on the client side:

var response = fetch('/secret').then(function(response) {
  return response.json();
}).then(function(responseJson) {
  var clientSecret = responseJson.client_secret;
  // Call stripe.() with the client secret.
});

Collect payment method details
Client-side

You’re ready to collect payment information on the client with Stripe Elements. Elements is a set of prebuilt 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

Stripe Elements is automatically available as a feature of Stripe.js. Include the Stripe.js script on your payment page by adding it to the head of your HTML file. Always load Stripe.js directly from js.stripe.com to remain PCI compliant. Do not include the script in a bundle or host a copy of it yourself.

checkout.html

<head>
  <title>Checkout</title>
  <script src="https://js.stripe.com/v3/"></script>
</head>

Create an instance of Elements with the following JavaScript on your checkout page:

var stripe = Stripe('pk_test_TYooMQauvdEDq54NiTphI7jx');
var elements = stripe.elements();

Add and configure an `epsBank` Element

Elements needs a place to live in your payment form. Create empty DOM nodes (containers) with unique IDs in your payment form and then pass those IDs to Elements.

checkout.html

<form id="payment-form">
  <div class="form-row">
    <label for="accountholder-name">
      Name
    </label>
    <input id="accountholder-name" name="accountholder-name">
  </div>

  <div class="form-row">
    <!--
      Using a label with a for attribute that matches the ID of the
      Element container enables the Element to automatically gain focus
      when the customer clicks on the label.
    -->
    <label for="eps-bank-element">
      EPS Bank
    </label>
    <div id="eps-bank-element">
      <!-- A Stripe Element will be inserted here. -->
    </div>
  </div>

  <button>Submit Payment</button>

  <!-- Used to display form errors. -->
  <div id="error-message" role="alert"></div>
</form>

When the form above has loaded, create an instance of an epsBank Element and mount it to the Element container created above:

var options = {
  // Custom styling can be passed to options when creating an Element
  style: {
    base: {
      padding: '10px 12px',
      color: '#32325d',
      fontSize: '16px',
      '::placeholder': {
        color: '#aab7c4'
      },
    },
  },
};

// Create an instance of the epsBank Element
var epsBank = elements.create('epsBank', options);

// Add an instance of the epsBank Element into
// the `eps-bank-element` <div>
epsBank.mount('#eps-bank-element');

Elements are completely customizable. You can style Elements to match the look and feel of your site, providing a seamless checkout experience for your customers. It’s also possible to style various input states, for example when the Element has focus.

Submit the payment to Stripe
Client-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. Do not log it, embed it in URLs, or expose it to anyone but the customer.

Use stripe.confirmEpsPayment to handle the redirect away from your page and to complete the payment. Add a return_url to this function to indicate where Stripe should redirect the user after they complete the payment on their bank’s website or mobile application.

client.js

var form = document.getElementById('payment-form');
var accountholderName = document.getElementById('accountholder-name');

form.addEventListener('submit', function(event) {
  event.preventDefault();

  // Redirects away from the client
  stripe.confirmEpsPayment(
    '{{PAYMENT_INTENT_CLIENT_SECRET}}',
    {
      payment_method: {
        eps: epsBank,
        billing_details: {
          name: accountholderName.value,
        },
      },
      return_url: 'https://example.com/checkout/complete',
    }
  );
});

The return_url should correspond to a page on your website that provides the status of the payment, by verifying the status of the PaymentIntent when rendering the return page. When Stripe redirects the customer to the return_url, the following URL query parameters are provided to verify status. You may also append your own query parameters when providing the return_url. They will persist through the redirect process.

Parameter	Description
`payment_intent`	The unique identifier for the `PaymentIntent`
`payment_intent_client_secret`	The client secret of the `PaymentIntent` object

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_action 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_action to requires_payment_method.

OptionalHandle post-payment events
Server-side

OptionalHandle EPS Bank Element changes
Client-side

OptionalHandle EPS redirect manually
Server-side

OptionalStore the customer's bank preference
Client-side

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

Accept an EPS payment

Set up StripeServer-side

Create a PaymentIntentServer-side

Collect payment method detailsClient-side

Set up Stripe Elements

Add and configure an epsBank Element

Submit the payment to StripeClient-side