EPS
Overview - EPS
Electronic Payment Standard (EPS) is currently the most widely used payment method in Austria. It is developed jointly by Austrian banks and the Government.
Main advantages of this payment method:
For merchants: EPS offers merchants guaranteed payments at zero risk. Merchants receive a payment guarantee from the customer's bank immediately after successful EPS transfer and can thus issue the goods or services immediately and without risk. Online payments are 100% guaranteed from the customer's bank.
For customers: EPS offers merchants guaranteed payments at zero risk. Merchants receive a payment guarantee from the customer's bank immediately after successful EPS transfer and can thus issue the goods or services immediately and without risk. Online payments are 100% guaranteed from the customer's bank.
Customer Experience - EPS

From customer perspective successful payment with EPS contains the following steps:
- Selecting EPS on merchant's site
- Choosing bank in which customer has bank account
- Redirecting the customer to his/her bank's login page
- Entering payment details by the customer - account number, PIN, and either: - A remittance slip is sent to the customer for confirming the transaction, containing a TAN (Transaction Authentication Number). The customer enters it to confirm the transaction. - The customer signs the transaction digitally using a 2FA token (if their bank offers that service)
- Authorizing the transaction in real-time by the bank, deducting the amount directly from the customers's account (if there is not enough balance, the transaction will be refused)
Notifications in case of successful EPS payment are:
- For the merchant: Real-time confirmation of the payment by the bank.
- For the customer: Redirection back to the merchant's page with a confirmation that the payment has been successful.
Customer Flow in the Payenegine Widget
Step No. | Description | |
---|---|---|
1 | Select EPS | ![]() |
2 | View payment | ![]() |
3 | Redirect to EPS | |
4 | Select Bank | ![]() |
5 | Log in to online banking | ![]() |
6 | Follow the steps and pay the purchase | ![]() |
![]() | ||
![]() | ||
![]() |
PayEngine Details - EPS
General
Name | Details |
---|---|
Product | EPS |
Channels | ECOM |
Currencies | EUR |
Countries | AT |
Technical Flow | Asynchronous |
Recurring | No |
Chargebacks | No |
Reusable Payment Instruments | Yes |
Supported Features & Services
Name | Details |
---|---|
Debit | Yes |
Preauthorization | No |
Cancelation | No |
Capture | No |
Refunds | Yes (only TAN based) |
Notifications | Yes (webhook and email) |
PayLink Integration | Yes (please contact support or account manager for this feature) |
Settlement Reporting | No (on the roadmap) |
Integration Types
Name | Details |
---|---|
API | Yes |
Widget | Yes |
Bridge | No |
Shop Plugin | No |
Integration via API - EPS
Technical Flow

Note: Before execution of EPS transactions, it's necessary merchant to setup a EPS Bank account.
Webhook Notifications
As it is not ensured at the time of the redirect to the shop that the payment was 100% successful, the Payengine waits for the final asynchronous notification before a status is moved from PENDING into SUCCESS or FAILURE.
A merchant should register for the Payengine webhook notifications in order to receive this final status update.
Alternatively a GET request on the order or DEBIT transaction would also work, but it is not ensured that the final status will be available immediately after the redirect and a merchant might have to query the GET multiple times.
Therefore it is strongly recommended that the asynchronous notifications from the Payengine are used instead.
The notifications could be subscribed:
- via the payengine API (link to API documentation)
- via the Payengine Merchant Center (link to Merchant Center notifications documentation)
Once the merchant receives notification for Debit transaction success, he can immediately ship the goods or provide the service subject of the order. The amount of the order will be received in the merchant's bank account one business day after receiving notification for successful Debit transaction.
Specifications - EPS
Prerequisites for Debit Transactions
Prerequisite | Mandatory/Optional (M/O) | Create Prerequisite |
---|---|---|
Customer | O | POST /customers |
Persona | O | POST /customers//personas |
Billing Address | O | POST /customers//addresses |
Shipping Address | O | POST /customers//addresses |
Specific Debit Request Parameters
Parameter | Mandatory/Optional (M/O) | Description | Example |
---|---|---|---|
payment.iban | O | IBAN of the customer | DE15111111111111111199 |
async.successUrl | M | Redirect URL for successful payment | http://my.shop.com/success |
async.failureUrl | M | Redirect URL for unsuccessful payment | http://my.shop.com/fail |
async.cancelUrl | M | Redirect URL when payment is canceled | http://my.shop.com/cancel |
Samples
Debit Transaction
EPS Debit Request
{ "product" : "eps", "terms": 1468590412476, "privacy": 1468590412476,
EPS Debit Response
{ "createdAt": 1549459395975, "modifiedAt": 1549459395997, "merchantId": "Merchant-11111111-1111-1111-1111-111111111111",
Testing
Currently testing of Giropay payment transactions on TM environment is possible only via simulator.