LogoLogo
BlogLogin
English
English
  • An Introduction to Saferpay
    • Licensing
      • Legacy licensing
    • Reconciliation
    • Acquirers & Payment Methods
    • Web Shop Plugins and certified partners
      • ePages Beyond
      • ePages NOW
      • Magento 2
      • Odoo
      • PrestaShop
        • PrestaShop User Guide
      • Salesforce Commerce Cloud
      • SAP Commerce Cloud
      • Shopware 6
        • Shopware 6 User Guide - German
        • Shopware 6 User Guide - English
      • WordPress WooCommerce
      • Shopify
    • Supported Languages
    • Common Saferpay terms - Glossary
  • News
    • Changes for transactions without customer presence
    • Changes for the Saferpay Hosted Forms, Fields and Payment Page
  • Quick Links
    • Web Shop Plugins and certified partners
    • Secure PayGate
    • User Administration
    • Payment Page Configuration
    • Risk Management
    • API Authentication
  • Interfaces
    • Payment API (aka JSON API)
    • Management API
    • Backoffice
      • The Home screen
      • Batch Processing
      • Transactions
        • Transaction Details
        • Batch Close
        • Declined transactions
        • Pending authorizations
        • Analytics
        • SEPA Refunds Export
        • Authorization & Payment
        • Credit
      • Risk Management
      • Secure PayGate / Payment Links
      • Secure Card Data
        • Secure Card Data Details
      • Settings
        • JSON API basic/Client Certificate authentication
        • User Administration
        • Payment Page Configuration
      • Online Support
      • User Profile
    • Saferpay OnSite
    • Feedback
  • Integration Guide
    • Integrating Saferpay
    • Ways of integration
      • General Information
        • Data Security and PCI DSS
        • Versioning
        • 3-D Secure
        • PSD2
        • Dynamic Currency Conversion
        • Iframe Integration and CSS
        • Fraud Intelligence
          • Silver
          • Fraud Intelligence Integration
      • Payment Page
        • Payment Page checklist
      • Transaction Interface
        • Recurring Payments
        • Refunds
          • SEPA Refunds
      • Capture and Daily Closing
        • Partial Captures
          • Marketplace
      • Secure Card Data - Tokenization
      • Saferpay Fields
      • Inquire Interfaces
      • Mobile Integration
      • Omni-Channel
      • Mail Phone Order
      • Error Handling
      • API Health Check
      • Saferpay API Specification
    • Payment Methods & Wallets
      • General and special cases
      • Account-to-Account Payments
      • Alipay+
      • Apple Pay
      • American Express
      • Bancontact
      • Billie
      • blik
      • Click to Pay
      • Diners Club International & Discover Card
      • eps
      • giropay
      • Google Pay
      • iDEAL 2.0
      • JCB
      • Klarna Payments
      • Maestro International
      • Mastercard
      • paydirekt
      • PayPal
      • PostFinance Pay
      • Przelewy24
      • Reka
      • SEPA Direct Debit
      • Sofort by Klarna
      • TWINT
      • UnionPay
      • Visa & V PAY
      • WeChat Pay
      • WL Crypto Payments
    • Testing
    • Go-Live
    • Frequently Asked Questions
    • Saferpay Demo
      • Saferpay Demo Environment
      • Saferpay Demo Shop
    • Support
    • Changelog
Powered by GitBook
On this page
  • General requirements
  • Technical requirements
  • Supported features
  • Testing

Was this helpful?

  1. Integration Guide
  2. Payment Methods & Wallets

eps

PreviousDiners Club International & Discover CardNextgiropay

Last updated 4 months ago

Was this helpful?

eps is a third party means of payment by the Austrian banks. To process eps via the Saferpay JSON API, a few things must be observed.

General requirements

The handling of eps payments with Saferpay requires:

  • A and thus a valid identification with a username and password for the Saferpay system.

  • Availability of at least one active Saferpay terminal via which payment can be carried out, and availability of the associated Saferpay TerminalId.

  • A valid acceptance agreement for eps.

For eps activation Saferpay needs:

  • Your eps Merchant ID.

  • Your eps IBAN.

  • Your eps BIC.

  • Your eps PIN.

  • The Currency your customers will purchase with eps.

  • Your Saferpay Customer ID.

  • The ID of the Saferpay eCommerce Terminal eps has to be added.

For eps activation on the Saferpay terminal, please about your eps credentials and the desired currency.

Technical requirements

  • Transactions made before 18.05.2021 cannot be refunded, as they're made via an old protocol-version!

  • Sometimes, Saferpay will not recieve the information necessary from eps, to be able to do a refund. In this case a refund will also not be possible!

Furthermore, for other flows (Refunds etc.), please refer to the table below.

Supported features

Feature

Support

Capture/Cancel

❌

Multipart Captures

❌

Secure Card Data

❌

✅

Recurring Payments

❌

3D Secure

❌

Dynamic Currency Conversion

❌

Mail Phone Order

❌

✅

Omni-Channel

❌

Testing

The general integration of eps can only be done via the and requires the following things to be noted:

The notification URLs, inside theNotification conatiner are mandatory, in order to avoid missing payment successes. See the for further information.

Only are possible, as eps does not support the generation of an alias.

eps does not support the . .

Please refer to , if you want to test eps.

Payment Page
Refunds
Needs attention!
Testing
Iframe integration
Saferpay will break out of the IFrame, if necessary
this chapter
corresponding license
inform our customer service
Payment Page process
referenced refunds