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
  • Bancontact Direct Mode
  • Flow description
  • Testing

Was this helpful?

  1. Integration Guide
  2. Payment Methods & Wallets

Bancontact

PreviousAmerican ExpressNextblik

Last updated 4 months ago

Was this helpful?

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

General requirements

The handling of Bancontact 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 by which payments can be carried out and availability of the associated Saferpay TerminalId.

  • A valid Bancontact contract.

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

Technical requirements

The general integration of Bancontact can be done either via the , or the and does not require any special attention, besides what is mentioned in the respective chapters.

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

Special Cases

  • Refunds for Bancontact are limited to only.

  • Bancontact Secure Card Data aliases may only be used for "card on file" 3D Secure transactions.

Supported features

Feature

Support

Capture/Cancel

❌

Multipart Captures

❌

✅

✅

Recurring Payments

❌

✅

❌

Mail Phone Order

✅

✅

Omni-Channel

❌

Bancontact Direct Mode

The Bancontact Direct Mode allows the merchant to directly integrate Bancontact into their site or mobile app. This chapter handles the technical details and flow of this type of integration.

Flow description

  1. Saferpay forwards the merchant request to the Bancontact system, where the IntentUrl and QR-Code data is generated.

  2. The merchant then has multiple options, how to proceed, also depending on the application:

    1. The merchant displays the QR-Code data, so his customer may scan it via the bancontact app.

    2. The IntentUrl is used to perform a direct switch towards the Bancontact payment app

  3. The payer performs the payment. Bancontact authorizes her/his card and sends the necessary data to Saferpay.

  4. Once the payment is finished, two things happen in parallel:

    • A.3: The merchant application validates the payment.

Testing

First, the merchant's application initiates the payment via the . Note that this should always be a centralized server, even if the payer/shopper interacts with the merchant system via an app!

The generated data is forwarded towards the merchant application through the .

A.1: The payment data is forwarded to the Saferpay system, which saves the data. Once a definitive transaction status has been determined, Saferpay will then call the StateNotificationUrl, which has been defined with the , to notify the merchant application that the data for this transaction is ready to be pulled.

A.2: The merchant application performs the to ask for the outcome of the transaction.

B: While the merchant application is notified of the transaction, in the background, the Bancontact app will redirect the payer towards the respective App-RedirectUrl, defined within , depending on the outcome.

Please refer to , if you want to test Bancontact.

Transaction AlternativePayment Request
Transaction AlternativePayment Response
Transaction AlternativePayment Request
Transaction QueryAlternativePayment Request
Transaction AlternativePayment Request
Secure Card Data
Refunds
3D Secure
Dynamic Currency Conversion (DCC)
Needs attention!
Testing
corresponding license
Payment Page
Transaction Interface
(click to enlarge)
Referenced Refunds
this chapter