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

SEPA Direct Debit

PreviousRekaNextSofort by Klarna

Last updated 4 months ago

Was this helpful?

SEPA transactions can also be processed via the Saferpay JSON API, through a partnership with Intercard.

General requirements

The handling of SEPA 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 SEPA contract with Intercard.

For SEPA activation on the Saferpay terminal and the necessary contract, please contact your Saferpay sales contact.

Technical requirements

The general integration of SEPA Direct Debit can be done either via the , or the Transaction Interface and requires the following things to be considered:

  • SEPA makes it necessary to define a unique SEPA MandateId for each transaction. You -the merchant- have two options to deal with this requirement:

    • You can define your own MandateId and submit it inside the Payment.MandateId parameter within the initialize request! Make sure it is unique!

    • If Payment.MandateId is not used, Saferpay will use the Saferpay TransactionId as its replacement, which is unique. You can find this value inside the authorization response as Transaction.Id!

    • On the , Saferpay will also display a mandate text, which the user has to agree to, before a payment can be made. If you use the transaction interface instead (see below), you must formulate and present a text yourself. The payer must agree to a SEPA mandate, or you are not allowed to carry out the payment!

  • The Integration via the Transaction Interface is only possible via direct post, using .

    • In this case, you must also display your own mandate text!

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

Supported features

Feature

Support

✅

Multipart Captures

❌

✅

Refunds

✅

✅

3D Secure

❌

Dynamic Currency Conversion

❌

Mail Phone Order

❌

✅

Omni-Channel

❌

Testing

/

Please refer to , if you want to test SEPA Direct Debit.

corresponding license
Payment Page
Payment Page
Authorize Direct
Secure Card Data
Needs attention!
Recurring Payments
Testing
Capture
Cancel
this chapter