WL SIPS DOCS

Release 22.5

go directly to content

Search by keywords

Bancontact integration

To search in the page use Ctrl+F on your keyboard

WL Sips is a secure multi-channel e-commerce payment solution that complies with the PCI DSS standard. It allows you to accept and manage payment transactions by taking into account business rules related to your activity (payment upon shipping, deferred payment, recurring payment, payment in instalments, etc.).

The purpose of this document is to explain the the Bancontact means of payment integration into WL Sips.

This document is intended to help you implement the the Bancontact means of payment on your e-commerce site.

It includes:

  • functional information for you
  • implementation instructions for your technical team

To get an overview of the WL Sips solution, we advise you to consult the following documents:

  • Functional presentation
  • Functionality set-up guide

Bancontact is the market leader in electronic payments in Belgium. The Bancontact card is the Belgian national card.

To pay with a Bancontact card, cardholders have to provide their card details, namely:

  • card number
  • expiry date
  • some co-branded Bancontact cards also have a security code (Bancontact/VPay and Bancontact/Maestro cards). It is not necessary to enter this code to make a Bancontact payment.

The 3-D Secure authentication is generally mandatory in order to finalise an online Bancontact payment. Any payment transaction is subject to cardholder authentication. This process involves both the card issuer bank as well as the network.

Therefore, you will have to subscribe to the 3-D Secure programme.

However, if you also subscribe to the Wallet Initiated Payment (WIP) service (see the WIP paragraph of the Functionality set up guide documentation), the OneClick transactions below of a certain amount (determined with Worldline Acquiring Belgium), may be exempt from 3-D Secure authentication.

Payment channels
Internet V Default payment channel
MOTO X
Fax X
IVS X
Means of payment
Immediate payment V Default method
End-of-day payment X
Deferred payment X
Payment upon shipping X
Payment in instalments X
Subscription payment V With WIP option
Batch payment X
OneClick payment V WIP: allows to bypass the authentication.
Currency management
Multicurrency acceptance X EURO only
Currency settlement X EURO only

The customer selects the Bancontact means of payment.

They are then redirected to their required information entry page:



The payment ticket is displayed, then the customer returns to your website.

In order to offer the Bancontact means of payment on your website, you have to sign an acceptance contract with Worldline Acquiring Belgium. Thereafter, you transmit us the contract number for recording in our information system.

These means of payment are also co-badged with Maestro and soon with V-Pay (Visa debit), which means that they can be accepted as international Maestro or Visa cards.

If you meet the required conditions, you can also subscribe to the WIP service, which will allow you to benefit the 3-D Secure authentication exemption on OneClick payments, and subscription payments.

When you subscribe to the WIP service with Bancontact, Bancontact provides 2 id:

  • Merchant Wallet ID: Unique identifier assigned by BANCONTACT to the WIP merchant. Disposition: 71xxxx.
  • WIP BEPAF or WIP TOKEN: alphanumeric id on 16 positions, provided by Bancontact to each merchant and that must be provided in BPAF field for each WIP transaction

You must provide those two id to WL Sips to complete the subscription to WIP service.

WL Sips offers you three solutions to integrate the Bancontact mean of payment:

  • Sips Paypage which directly acts as the payment interface with customers via their web browser.
  • Sips Office which gives you the possibility to display your payment pages and works through a server-to-server dialog.
  • Sips Office Batch which allows you to process batch payments.

For Bancontact payments, it is not allowed to defer the remittance. You cannot adjust the date of funds transfers (immediate payment).

The diagram below explains the different transaction statuses according to the chosen capture mode:


description of the possible statuses for a Bancontact transaction

The only capture mode available is IMMEDIATE. Three states are possible: the transaction is waiting to be captured (status TO_CAPTURE, responseCode 60) or the transaction is accepted and therefore captured (status CAPTURED, responseCode 00) or the transaction is rejected (status REFUSED, responseCode different from 00 and 60).

The payment process for Sips Paypage is described below:


steps of a bancontact payment with paypage

1) The customer makes the payment. 2) The customer is redirected to the payment method selection page hosted at WL Sips and selects Bancontact and enters his card number. 3) He is redirected to the ACS page where he authenticates himself. 4) The customer is redirected to the WL Sips pages. 5) If the customer clicks on the back to store button, WL Sips sends the manual response. 6) WL Sips sends the automatic automatic response.
Note: in WIP mode, the authentication phase is deleted (flows 3 and 4).

The following fields have a particular behaviour:

Field name Remarks/rules
statementReference The value sent will appear on your account statement.
The allowed characters are [a-zA-Z0-9 / \ + =.].
orderId In order to be compatible with the BXAP protocol, the field must not exceed 30 characters.
Any value longer than 30 characters will be truncated.
The allowed characters are [a-zA-Z0-9 / \ + =.].
fraudData.bypass3DS WIP_BANCONTACT if you wish to deactivate the 3-D Secure authentication for a OneClick Bancontact payment.

The following fields must be necessarily populated during a payment to benefit from the WIP functionality:

Field name Remarks/rules
Bancontact.BancontactMerchantCustomer AuthentMethod The cardholder's authentication method used on the merchant's website.
Merchant.merchantWalletId Client wallet identifier (not to confuse with the unique identifier assigned by BANCONTACT to benefit from the WIP service).

The following table summarises the different response cases to be processed:

Status Response fields Action to take
Payment accepted acquirerResponseCode = 00
authorisationId = (cf. the Data Dictionary).
maskedPan = (cf. the Data Dictionary).
panExpiryDate = (cf. the Data Dictionary).
You can deliver the order.
OneClick payment accepted acquirerResponseCode = 00
authorisationId = (cf. the Data Dictionary).

holderAuthentProgram =

  • 3DS: the holder authenticated themselves using a 3-D Secure process
  • BYPASS: the holder has not been authenticated because the payment is made via WIP.
maskedPan = (cf. the Data Dictionary).
panExpiryDate = (cf. the Data Dictionary).
You can deliver the order.
Acquirer refusal acquirerResponseCode = (cf. the Data Dictionary). The authorisation is refused for a reason unrelated to fraud.
If you have not opted for the "new payment attempt" option (please read the Functionality set-up Guide for more details), you can suggest that your customer pay with another means of payment by generating a new request.
Refusal due to the number of attempts reached responseCode = 75 The customer has made several attempts that have all failed.
Refusal due to a technical issue acquirerResponseCode = 90-98
responseCode = 90, 99
Temporary technical issue when processing the transaction. Suggest that your customer redo a payment later.

For the complete response codes (responseCode) and acquirer response codes (acquirerResponseCode), please refer to the Data dictionary.

The payment process for Sips Office is described below:


steps of an American Express payment via Office

1) You collect the card information on the payment page hosted on your website and transmit this information to information to WL Sips via the cardCheckEnrollment method. 2) WL Sips sends you the url of the ACS. 3) You redirect your customer to the ACS. 4) Your client authenticates and is redirected to your site. 5) You collect authentication information and send an authorization request to WL Sips via the cardValidateAuthenticationAndOrder method. 6) WL Sips sends you the payment response and you display the payment result to your your customer on your website.

Bancontact payments can be initiated using the cardCheckEnrollment function of the CheckOut service.

The following fields are used to send information specific to this means of payment:

Field name Remarks/rules
cardNumber Mandatory
cardExpiryDate Mandatory
cardCSCValue Optional
orderId In order to be compatible with the BXAP protocol, the field must not exceed 30 characters.
Any value longer than 30 characters will be truncated.
The allowed characters are [a-zA-Z0-9 / \ + =.].
paymentMeanBrand Must be populated with BCMC.
statementReference The value sent will appear on your account statement.
The allowed characters are [a-zA-Z0-9 / \ + =.].

For more information, please refer to the 3-D Secure guide on Sips Office connector to implement the other steps of a 3-D Secure payment.

The following fields must be necessarily populated during a payment to benefit from the WIP functionality:

Field name Remarks/rules
Bancontact.BancontactMerchantCustomer AuthentMethod The cardholder's authentication method used on the merchant's website.
Bancontact.initialAuthenticationCavv Corresponds to the Cryptogram (CAVV) of the original transaction made in 3DS.

The following table summarises the different response cases to be processed:

Status Response fields Action to take
Payment accepted acquirerResponseCode = 00
authorisationId = (cf. the Data Dictionary).
You can deliver the order.
Acquirer refusal acquirerResponseCode = (cf. the Data Dictionary). The authorisation is refused for a reason unrelated to fraud, you can suggest that your customer pay with another means of payment by generating a new request.
Refusal due to a technical issue acquirerResponseCode = 90-98
responseCode = 90, 99
Temporary technical issue when processing the transaction. Suggest that your customer redo a payment later.

For the complete response codes (responseCode) and acquirer response codes (acquirerResponseCode), please refer to the Data dictionary.

Please refer to 3-D Secure guide to analyse the authentication information.

The following operations are available on Bancontact transactions:

Cash management
Cancellation X

Validation X
Refund V
Maximum amount allowed per refund: €3,000 (several partial refunds required for any transaction over €3,000).
Duplication V With WIP option
Credit X

The diagram below explains which cash management operation is available when a transaction is in a given status:


possible status after a cash management operation for a bancontact transaction

When the transaction is created, the status is TO_CAPTURE. If the captur fails, the status becomes CAPTURE_REFUSED. if the captur succeeds, the status becomes CAPTURED. Once the transaction captured, it can be refunded patially or completly. If the whole transaction is refunded, the status becomes CREDITED. If only a part of the transaction is refunded, the status remains CAPTURED.

The reports provided by WL Sips allow you to have a comprehensive and consolidated view of your transactions, cash operations, accounts and chargebacks. You can use this information to improve your information system.

The availability of Bancontact transactions for each type of report is summarised in the table below:

Reports availability
Transactions report V
Operations report V
Reconciliations report X
Chargebacks report X
Note: for Bancontact transactions, the paymentMeanBrand field is populated with the value BCMC.

You can view your Bancontact transactions and perform various cash management operations with Sips Office Extranet.



This site uses trackers to improve your experience, perform analysis and researches on your use of WL Sips documentation website.
You have several options:
Closing this banner you refuse the use of trackers on your device.

Configuration