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
    • General Information
      • Data Security and PCI DSS
      • Versioning
      • 3-D Secure
      • Payment Service Directive 2 - PSD2
      • Dynamic Currency Conversion
      • Iframe Integration and CSS
    • Ways of 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
      • Fraud Intelligence
        • Silver
        • Fraud Intelligence Integration
      • 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
  • Payment Page integration
  • Testing

Was this helpful?

  1. Integration Guide
  2. Payment Methods & Wallets

iDEAL 2.0

PreviousGoogle PayNextJCB

Last updated 2 months ago

Was this helpful?

iDEAL transactions can be processed via the Saferpay JSON API. However, as iDEAL is a third party provider, there are a few things to consider.

General requirements

The handling of iDeal 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.

  • An iDeal contract with Worldline. Others are not supported.

For iDeal activation on the Saferpay terminal, please contact your sales contact.

Technical requirements

The general integration of iDEAL 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.

  • The parameter is mandatory. If it is not set, Saferpay will set the Saferpay as its value.

  • The is limited to a length of 18 and no special characters. Saferpay will automatically filter any special character, to prevent issues.

  • iDEAL does not support the . .

  • Refunds are technically not directly supported by iDeal. Due to that, Saferpay will perform the refund through other means. Thusly, the payer will not see the refund in their iDeal-App. Aside that, the refund is processed normally.

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 (DCC)

❌

Mail Phone Order

❌

✅

Omni-Channel

❌

Payment Page integration

Testing

✅

iDeal is integrated via the standard .

Please refer to , if you want to test iDEAL.

Payment Page integration
Refunds
(needs attention)
Testing
corresponding license
Payment Page
Iframe integration
Payment.Payernote
Transaction.Id
Payment.OrderId
Saferpay will break out of the IFrame, if necessary
Payment Page process
this chapter