Skip to content


Start accepting payments with Bancontact, the most popular online payment method in Belgium, maintaining its position as the market leader in both online and in-person transactions.

To make a payment with Bancontact, customers are directed to the website or mobile app for authorization. They enter their card details or scan a QR code, then authorise payment.

Afterward, they return to your website, with immediate notification of payment success or failure.

Payment optionCategoryCountryCurrencyFeaturesIntegrations
BancontactCardsBelgiumEURPartial refund
Payment form
Prestashop plugin
WooCommerce plugin
Magento plugin

How to use Bancontact

The workflow proceeds as follows:

  1. On the merchant’s website, the customer selects Bancontact.
  2. The customer is redirected to Bancontact’s payment page where they are presented with an option to enter their PAN or scan a QR code.
  3. They complete the payment:
    a. If the consumer selects to enter their PAN, they are redirected to their issuing bank for 3DS authentication.
    b. If the consumer scans the QR code, they confirm the payment in the Bancontact app.
  4. The consumer is redirected to the merchant’s website.
  5. The merchant receives the payment confirmation.
  6. After that, the merchant can ship the order/deliver the goods to the consumer.

How it works

Below you will find the essential steps required to integrate the Bancontact payment method.

Step 1: Create the Order
Step 2: Get the Payment Link
Step 3: Get the Payment Status
Step 1: Create the Order

Make sure to create the order request with Bancontact (“BNCT”) as the chosen payment method  (transaction.paymentMethod) and set the customer language preference in customerInfo.customerLanguage.

Step 2: Get the Payment Link

Proceed to obtain the payment link, outlined below, to redirect the customer to a secure payment page for authentication and payment authorization.

Please be aware that the request below requires an Authorization Header containing the transactionSignature obtained on the previous step.

EnvironmentURLOperation Method & EndpointOperation Description
PRODapi.sibsgateway.comPOST {version-id}/payments/{id}/pbl/payment-linkPerform the transaction and redirect user to Payment Host.[1|2].sibs.ptPOST {version-id}/payments/{id}/pbl/payment-linkPerform the transaction and redirect user to Payment Host.

Ensure that you include these essential elements as specified:

LocationData ElementTypeConditionDescription
PathidStringMandatoryUsed to identify the transaction
Header parameters:
LocationData ElementTypeConditionDescription
Request HeaderContent-TypeStringMandatoryapplication/json
Request HeaderAuthorizationStringMandatoryAuthorization Digest
Request parameters:
LocationData ElementTypeConditionDescription
Request BodyuserAcceptanceIndicatorBooleanMandatoryIndicates if the user has accepted the Terms and Conditions, in order to continue with the payment.
Request BodygatewayIdStringMandatoryPayment Channel identifier for the channel the Customer is going to use for their payment.
Value: ‘bcmc’ – Bancontact;
Request BodyinfoInfoMandatoryObject that defines the transaction additional information.
Request Body.infodeviceInfoDeviceInfoOptionalObject that defines the customer device information.
Request Accept Header
Request Java Enabled
Request Language
Request Color Depth
Request Screen Height
Request Screen Width
Request Time Zone
Request User Agent
Request Family
Request Version
Request Architecture
Request Manufacturer
Request Model
Request Unique Identification
Request Name
Request Version
Request Address
Request BodycustomerInfoCustomerInfoOptionalKey Value tuple array.
Request Body.customerInfokeystringMandatoryUsed to supply “customerName”, “customerEmail”.
Request Body.customerInfovaluestringMandatoryUsed to supply “customerName”, “customerEmail”.
Request BodymerchantMerchantOptionalMerchant Data
Request Body.merchantmerchantURLstringMandatoryMerchant Shop URL for redirect.
Request Body.merchantappToAppURLstringOptionalCustom app URL for customer redirect back to the app, which triggered the payment.
Applicable when gatewayId is ‘bcmc’.
Overrides merchantURL for mobile flows.
Request Body.infoaccountInfoAccountInfoOptionalAccount related data.
Applicable when gatewayId is ‘bcmc’
Request Holder Name. UTF-8 Format. 
Request CodeOptionalCustomer Country Code. Alpha2

Here’s a model of how to get the payment link:

    "userAcceptanceIndicator": true,
    "gatewayId": "bcmc",
    "info": {
        "deviceInfo": {
            "browserAcceptHeader": "application/json, text/plain, */*",
            "browserJavaEnabled": "false",
            "browserLanguage": "en",
            "browserColorDepth": "24",
            "browserScreenHeight": "1080",
            "browserScreenWidth": "1920",
            "browserTZ": "-60",
            "browserUserAgent": "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/ Safari/537.36",
            "geoLocalization": "Lat: 38.7350528 | Long: -9.2143616",
            "systemFamily": "Windows",
            "systemVersion": "Windows",
            "deviceID": "498bfd4c3a3645b38667a7037b616c18",
            "applicationName": "Chrome",
            "applicationVersion": "106"
        "customerInfo": [
                "key": "customerName",
                "value": "Test Name"
                "key": "customerEmail",
        "accountInfo": {
            "holderName": "Test Name",
            "customerCountry": "BE"
    "merchant": {

After successfully completing the operation, a ‘pending’ paymentStatus is received.

The user is then redirected to a payment confirmation environment before being seamlessly returned to the merchant’s URL.

Step 3: Get the Payment Status

You can perform a “Get Status” operation to check the status at any time.

The Authorization HTTP header is set to the Bearer token as it was used in the initial Checkout.

GET {transactionID}/status
Request URL:{transactionID}/status
Request Headers:
Authorization: ‘Bearer <AuthToken>’
X-IBM-Client-Id: ‘<ClientId>’
Content-Type: application/json

A successful technical response comprises of an HTTP-200 status and a returnStatus.statusCode=”000″.

Here are some examples of the possible result codes:

Result CodestatusMsgDescriptionAction
HTTP-200SuccessSuccess responseN/A
HTTP-400Bad RequestThe JSON payload is not matching the API definition or some mandatory HTTP headers are missing.Please check in API Market for the correct syntax.
HTTP-401UnauthorizedOn the Authorization, Bearer token is invalid/expired or not associated with the Terminal used.Please check in SIBS Backoffice under the Credentials if the token is valid and create a new one if needed.
HTTP-403ForbiddenThe ClientID set on the X-IBM-Client-Id HTTP header is not valid or does not possess a valid subscription to the API.Please check in SIBS Backoffice under the SPG APP 2.0 if the ClientID is correct. If the problem persists contact SIBS Gateway support for a ClientID reset.
HTTP-405Method Not AllowedThe HTTP Method used is not matching any of the API definitions available.Please check in API Market for the correct HTTP Method.
HTTP-429Too Many RequestsThe API calls rate limit has been exceeded.Please check in API Market for information on the rate limits that apply to the API.
HTTP-500Internal Server ErrorThe API call has failed… and its most likely on our side.You should retry the operation, and if the problem persists contact SIBS Gateway support for assistance.
HTTP-503Service UnavailableThe API call is not currently available. Usually we are always on, but short availability issues may occur during scheduled maintenance.You should wait and try again later.