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
  • Supported payment methods per interface
  • What should I use?
  • Questions?

Was this helpful?

  1. Integration Guide

Ways of integration

PreviousIntegrating SaferpayNextGeneral Information

Last updated 2 days ago

Was this helpful?

Saferpay consists of two main interfaces and a set of different additional modules that can be added to each interface depending on the business requriements and desired payment flow.

The main components of the Saferpay JSON API are:

  • Payment Page Interface

  • Transaction Interface

  • and the additional Secure Card Data module

It is important to understand the different intended uses and functionalities of each component to decide which Interface is best suited for your business and desired payment flows.

Supported payment methods per interface

Payment method

Transaction Interface

Payment Page

✅

✅

✅

✅

✅

✅

✅

✅

✅

✅

❌

✅

❌

✅

✅

✅

✅

✅

✅

✅

❌

✅

❌

✅

❌

✅

❌

✅

❌

✅

❌

✅

❌

✅

✅

❌

✅

❌

✅

✅

❌

✅

❌

✅

✅

✅

❌

✅

❌

✅

❌

✅

What should I use?

Before implementing, it is important to clarify which functions are important for you.

Use the PaymentPage/ E-Commerce, if...

Use the Transaction Interface/Saferpay Business, if...

Why not both?

If you have access to Saferpay Business, you also have access to all API functions Saferpay has to offer. You don't have to stick to one interface or the other, you can also mix both interfaces.

Questions?

Still unsure what you need?

+ Billie

-Integration via this method requires special attention. See the respective payment method chapter for more information!

You only want to do transactions: Do you have a small and simple web shop? Are , or not important for you? The Payment Page and a regular E-Commerce contract probably are sufficient for you.

You want to have one solution for every payment method: does support every payment method Saferpay has to offer. Once integrated, it is a simple matter of activating the payment methods you need, and they will show up on the page.

You want a more embedded/integrated solution: does offer a more integrated and personalized payment flow for credit cards, via , or . Think of it as reduced down to the card entry form, which can be embedded into every HTML-based application.

You want to do recurring payments: need special API functions, that are only available over Saferpay Business!

You want to execute refunds via the API: (Consider that refunds are also possible via the Saferpay Backoffice) are only possible with the transaction interface and a Saferpay Business license.

You want to save and use card data in our Secure Card Data store: Similar to , but Secure Card Data can do more than just that. Furthermore, you could also spare your customer from entering his card data over and over again, even for 3D Secure payments.

In some cases, you have to use the . For example, if you want to use , or any other 3rd party provider.

Another use case could be that you do all your normal authorizations over the , but then you use the .

If you decide to upgrade from E-Commerce to Business (For example for executing refunds via API) and already have a , you can simply extend your integration for the functions you need, without changing the whole existing implementation.

and we will help you to decide.

refunds over the API
recurring payments
The PaymentPage
The Transaction Interface
the Saferpay Fields
iframe integration
the Payment Page
Recurring Payments
Refunds via API
recurring payments
PaymentPage
PayPal
PaymentPage
Transaction Interface for Refunds
PaymentPage Integration
Visa/V PAY
Mastercard
Maestro International
American Express
Bancontact
blik
Click to Pay
Diners Club/Discover
JCB
SEPA Direct Debit
PayPal
Przelewy24
eps
giropay
iDEAL
SOFORT
paydirekt
Twint
Unionpay
Alipay+
Apple Pay (Wallet)
Klarna Payments
WL Crypto Payments
Google Pay (Wallet)
PostFinance Pay
WeChat Pay
Account-to-Account Payments
Reka
Contact the Saferpay Integration Support
(click to enlarge)