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


Markets (consumer)	`BE`
Processing currencies	`EUR`
Consumer currencies	`EUR`
Authentication methods	`REDIRECT` `SCAN_CODE` `APP_INTENT`
Authentication timeout	1 hour
Minimum payment amount	0.01 EUR
Maximum payment amount	1,500.00 (via mobile authentication flows) No limit with 3DS authentication
Payment instrument	`BANCONTACT_ACCOUNT`
Recurring payments	Yes
Separate captures	No
Refund	Full - Partial - Multiple
Refund validity	365 days
Disputes	No
Settlement risk	No

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:

Data Field	Description
paymentMethod	`BANCONTACT`
amount.value	The amount to be paid in the smallest units of the currency used.
amount.currency	`EUR`
consumer.name	Full name of the consumer.
consumer.country	The country where the consumer is shopping.
paymentDescriptor	Description of the payment.
authenticationSettings: REDIRECT settings.returnUrl	Add the URL where the consumer should be redirected after they complete the payment. Required for the `REDIRECT` flow.
authenticationSettings: SCAN_CODE settings.scanBy	Specify the expiration time for the QR Code. Required for the `SCAN_CODE` flow.
authenticationSettings: APP_INTENT settings.mobileIntentUri	Add the mobile URI where the consumer should be redirected after they complete the payment. Required for the `APP_INTENT` flow.

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

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.
The consumer will be presented with the reference number and instructions to complete the payment.

SCAN_CODE

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

APP_INTENT

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

Handling the payment result

REDIRECT

After the consumer completes the payment, they are redirected to the returnUrl specified in the payment charge creation request.
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.
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

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

APP_INTENT

Once the consumer has confirmed the payment, they are returned to your app using the mobileIntentUri provided in the initial payment charge creation request.
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.
Webhooks are also sent to inform you of the payment outcome.

Sandbox testing

Test card numbers

PAN	Expiry Date	Result
60600599999899023	01/2035	Authentication success (frictionless)
60600599999899080	01/2035	Authentication denied

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.