Skip to content

    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

    eps-customer-experience

    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:

    1. For the merchant: Real-time confirmation of the payment by the bank.
    2. 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
    1Select EPS
    2View payment
    3Redirect to EPS
    4Select Bank
    5Log in to online banking
    6Follow the steps and pay the purchase

    PayEngine Details - EPS

    General

    NameDetails
    ProductEPS
    ChannelsECOM
    CurrenciesEUR
    CountriesAT
    Technical FlowAsynchronous
    RecurringNo
    ChargebacksNo
    Reusable Payment InstrumentsYes

    Supported Features & Services

    NameDetails
    DebitYes
    PreauthorizationNo
    CancelationNo
    CaptureNo
    RefundsYes (only TAN based)
    NotificationsYes (webhook and email)
    PayLink IntegrationYes (please contact support or account manager for this feature)
    Settlement ReportingNo (on the roadmap)

    Integration Types

    NameDetails
    APIYes
    WidgetYes
    BridgeNo
    Shop PluginNo

    Integration via API - EPS

    Technical Flow

    eps-techical-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:

    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

    PrerequisiteMandatory/Optional (M/O)Create Prerequisite
    CustomerOPOST /customers
    PersonaOPOST /customers//personas
    Billing AddressOPOST /customers//addresses
    Shipping AddressOPOST /customers//addresses

    Specific Debit Request Parameters

    ParameterMandatory/Optional (M/O)DescriptionExample
    payment.ibanOIBAN of the customerDE15111111111111111199
    async.successUrlMRedirect URL for successful paymenthttp://my.shop.com/success
    async.failureUrlMRedirect URL for unsuccessful paymenthttp://my.shop.com/fail
    async.cancelUrlMRedirect URL when payment is canceledhttp://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.

    Was this helpful?

    What was your feeling about it?