Bancontact is a Belgian debit card scheme, with no no-chargeback risk and the most popular payment method in Belgium. Used by 94% of Belgians, with over 18 million cards in circulation and connected to 17 banks, Bancontact processed 382 million online payments in 2024 (+19,7% compared to 2023, with 90% of mobile transactions), making it an essential option for merchants targeting the Belgian market. Learn more about Bancontact.

Payment method properties

Make a Bancontact payment

Bancontact is available through our standardized REDIRECT, SCAN_CODE and APP_INTENT flows. Enabling you to offer a seamless desktop or in-store QR code to mobile handoff, as well as a smooth app-to-app experience.

To create a Bancontact payment, you'll need to provide the following data at minimum when calling our /v1/payment-charges API:

Request

POST /v1/payment-charges

{
  "paymentMethod": "BANCONTACT",
  "amount": {
    "value": 1000,
    "currency": "EUR"
  },
  "consumer": {
    "country": "BE"
  },
  "authenticationSettings": [
    {
      "type": "REDIRECT",
      "settings": {
        "returnUrl": "https://www.webshop.com/order-results-page"
      }
    },
    {
      "type": "SCAN_CODE",
      "settings": {
        "scanBy": "2025-06-22T11:09:22.937Z"
      }
    },
    {
      "type": "APP_INTENT",
      "settings":{
      "mobileIntentUri": "webshop://paymentresponse?123"
      }
    } 
  ]
}

Response

You'll receive our standard payment charge response with the available authentication methods:

{
  "id": "charge_qPoB2h51KyW3CcOiYdbUv",
  "paymentMethod": "BANCONTACT",
  "paymentMedium": "ECOMMERCE",
  "scheduleType": "UNSCHEDULED",
  "instrumentId": "instr_l0cbLJx0mniRjCknrPL0b",
  "currency": "EUR",
  "country": "BE",
  "status": "AUTHENTICATION_PENDING",
  "consumer": {
    "country": "BE"
  },
  "authenticationMethods": [
    {
      "details": {
        "requestUrl": "https://redirection-target.ppro.com",
        "requestMethod": "GET"
      },
      "type": "REDIRECT"
    },
    {
      "details": {
        "mobileIntentUri": "bepgenapp://paymentrequest?token=AAAAAAAAAAAAABYJmXQEEojHxoSjfRCF"
      },
      "type": "APP_INTENT"
    },
    {
      "details": {
        "codeType": "QR",
        "codePayload": "BEP://charge_Y3JVzvEaJpvG53xd2R2Zt",
        "scanBy": "2025-06-22T11:09:22.937Z"
      },
      "type": "SCAN_CODE"
    },
  ],
  "authorizations": [
    {
      "id": "authz_1KBdVLWcqMHwqqJT0ZDwV",
      "amount": 1000,
      "status": "AUTHENTICATION_PENDING",
      "createdAt": "2025-06-21T11:42:00.940Z",
      "updatedAt": "2025-06-21T11:42:00.940Z"
    }
  ],
  "captures": [],
  "refunds": [],
  "voids": [],
  "createdAt": "2025-06-21T11:42:00.438Z",
  "updatedAt": "2025-06-21T11:42:00.940Z",
  "_links": {
    "authorizations": {
      "href": "/v1/payment-charges/charge_qPoB2h51KyW3CcOiYdbUv/authorizations"
    },
    "captures": {
      "href": "/v1/payment-charges/charge_qPoB2h51KyW3CcOiYdbUv/captures"
    },
    "refunds": {
      "href": "/v1/payment-charges/charge_qPoB2h51KyW3CcOiYdbUv/refunds"
    },
    "voids": {
      "href": "/v1/payment-charges/charge_qPoB2h51KyW3CcOiYdbUv/voids"
    }
  }
}

Pick the desired authentication method

REDIRECT

1. Redirect your consumer to the returned $.authenticationMethods[?(@.type == "REDIRECT")].details.requestUrl.
   For example, with the value of https://redirection-target.ppro.com/ using the returned $.authenticationMethods[?(@.type == "REDIRECT")].details.requestMethod HTTP method.
2. The consumer will be presented with the reference number and instructions to complete the payment.

SCAN_CODE

1. Render the code using one of the techniques available.
2. The consumer will scan the code to complete the payment.

APP_INTENT

1. Use the intent system on Android or a similar mechanism on iOS to trigger the URI.
2. The consumer will be taken to the native app to complete the payment.

Handling the payment result

REDIRECT

1. After the consumer completes the payment, they are redirected to the returnUrl specified in the payment charge creation request.
2. Upon redirect back to your site, retrieve the latest payment status by performing a GET /v1/payment-charges/{paymentChargeId}. Use the returned status field to determine and display the final payment outcome to the consumer.
3. Additionally, webhooks are triggered to notify you of the payment result. This ensures you receive the outcome even if the consumer closes their browser or fails to return to your website.

SCAN_CODE

1. You'll be notified of the payment outcome via Webhook.
2. You can check the payment status at any time by making a GET /v1/payment-charges/{paymentChargeId}.
3. Use the Status that you received to display the payment outcome to the consumer.

APP_INTENT

1. Once the consumer has confirmed the payment, they are returned to your app using the mobileIntentUri provided in the initial payment charge creation request.
2. After the consumer is redirected back to your app, check the payment status by making a GET /v1/payment-charges/{paymentChargeId}. Use the Status that you received to display the payment outcome to the consumer.
3. Webhooks are also sent to inform you of the payment outcome.

Sandbox testing

Test card numbers

Additional information

• The PPRO-hosted payment page supports four languages: English, Dutch, French, and German. If no preferred language is specified, the default is French.
• Consumers see payment options based on screen size:
  • Mobile (≤599px): vertical layout with a “Pay with Bancontact app” link and PAN input form.
  • Small devices (600–767px): horizontal layout with the app link and PAN input form.
  • Medium devices (768–1199px): horizontal layout with app link, QR code, and PAN input form.
  • Large/desktop (≥1200px): horizontal layout with QR code and PAN input form.
    For payments over €1,500, all mobile app options are hidden.