Skip to content

Bancontact

Offer Bancontact cards and the Bancontact app through Silverflow: setup, flows and testing.

For acquirers on Silverflow. Bancontact is the Belgian debit card scheme. Ginger processes Bancontact payments through Silverflow, with the acceptor of the bancontact scheme in the project's silverflow-v2 contract. Available since July 2026: see the changelog.

Your customer pays in one of two ways:

FlowHow the customer pays
Card entryEnters the Bancontact card number and authenticates with 3-D Secure (3DS), run by Ginger or by your own 3DS provider. Bancontact cards have no CVC
Bancontact appOpens the Bancontact app from a link on mobile, or scans a QR code on desktop, and approves the payment in the app

On the hosted payment page, Ginger runs both flows. For your own payment page, see Accept a card payment in the payment acceptance docs. To run 3DS yourself, see Your own 3-D Secure.

Prerequisites

Configure the bancontact scheme

Add bancontact to the schemes of the project's silverflow-v2 contract, with charge_type set to charge. Enter its acceptor_key, or its bin_key and mid to let Ginger create the acceptor: see Board merchants on Silverflow. Bancontact payments fail with Bancontact is not configured for Silverflow. until the scheme has an acceptor key.

Complete the merchant and project details

For automatic boarding of the Bancontact acceptor, the merchant needs a billing address with its country, and the project a trade name, website URL and MCC. See What boarding needs.

  • Your Silverflow API keys have the bep:All permission: see Create Silverflow API keys.
  • The project has the permission /payment-methods/bancontact/ (POST).

The bancontact scheme in the project's contracts, set with Update a project contract:

{
  "silverflow-v2": {
    "fields": {
      "boarding_mode": "disabled",
      "schemes": {
        "bancontact": {
          "acceptor_key": "mac-EXAMPLEACCEPTOR005",
          "charge_type": "charge"
        }
      }
    }
  }
}

How Ginger processes Bancontact

When a merchant creates a bancontact transaction, Ginger asks Silverflow for a Bancontact payment intent and puts its QR code content and app link in the transaction. This needs the bep:All permission on your Silverflow API keys.

After the customer approves in the app, Silverflow notifies Ginger. Ginger gets the authentication result, authorises the payment at Silverflow and reports the result back, so the app can show it. If a notification doesn't arrive, Ginger checks Silverflow every minute. In the Admin portal, an app payment stays new until the customer opens the app or scans the code, is pending while they approve and Ginger authorises, then becomes accepted or error. A failed approval in the app has the reason BEP authentication failed.

Ask your Ginger contact whether the Bancontact app limits the amount of a payment. Above a limit, the customer pays with card entry and 3DS.

What's supported

  • Payments in EUR, without CVC: Bancontact cards have none.
  • Refunds: see Refunds.
  • Not supported through Silverflow: one-click and recurring Bancontact payments.

Refunds

Your merchants refund a Bancontact payment like any other, from the Merchant portal or with the API: see Refunds. This works the same for card entry, the app and the QR code. Ginger creates a refund order, linked to the original order, and sends the refund to Silverflow. Refunds through Silverflow are created as independent charges with their own reference: see the changelog.

Test Bancontact

Use a project in active-testing and the Bancontact test cards in Silverflow test cards.

The silverflow-v2 contract has a testing aid for the sandbox, bancontact_pan_flow_testing_mode. When it's true, results of the Bancontact app flow from the Silverflow sandbox don't change the transaction status, so you can test the card entry flow on its own. Production ignores it.

Next steps