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.

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.

Endpoints:

Ensure that you include these essential elements as specified:

Header parameters:

Request parameters:

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/106.0.0.0 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",
 "value": email@provider.com
 }
 ],
 "accountInfo": {
 "holderName": "Test Name",
 "customerCountry": "BE"
 }
 },
 "merchant": {
 "appToAppURL": https://egadget2.azurewebsites.net/#/returns?id={{transactionId}},
 "merchantURL": https://egadget2.azurewebsites.net/#/returns?id={{transactionId}}
 }
}

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:

https://stargate-cer.qly.site1.sibs.pt/api/v1/payments/{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: