Bancontact
Information
Bancontact is available for Flow. Flow enables you to accept payments on your website using Checkout.com's global network of payment methods with a single integration.
Bancontact enables customers to perform secure online payments in Belgium.
Information
To enable Bancontact payments on your account, contact your account manager or request support.
Model | Collecting |
|---|---|
Payment flow | Redirect |
Payment method type | Card payment |
Auto-capture payment | |
Authorization | |
Capture | |
Refund | |
Partial refund | |
Chargeback | |
Recurring payment |
Bancontact Wallet Initiated Payments (WIP) enable you to store a customer's Bancontact account and charge it later without Strong Customer Authentication (SCA).
The customer authenticates and pays once. This first payment creates an agreement, which Checkout.com stores as a payment instrument. You then use the payment instrument to request later payments.
Bancontact supports the following use cases:
One-click payment: A customer-initiated transaction (CIT). The customer is present and starts the payment. For example, a returning customer who pays with one tap.
Recurring payment: A merchant-initiated transaction (MIT). You start the payment without the customer present. For example, a subscription billed on a schedule.
Bancontact also sets a maximum amount for your account during onboarding. You cannot split a payment into several smaller WIP payments to exceed this amount.
Recurring payments have the following limitations:
- Recurring payments are always automatically captured. Manual captures are not supported.
- You must create the agreement during an initial payment. You cannot create an agreement without charging the customer.
- Smart retries and dunning are not supported.
- The payment instrument Checkout.com stores only contains the card's last four digits, expiry date, agreement reference, and agreement status. You cannot retrieve the full card number or the customer's IBAN.
To enable Bancontact recurring payments on your account, contact your account manager or request support.
Checkout.com communicates status updates for your payments through webhooks. You must configure your webhook server.
When integrating Bancontact payments, you can receive the following webhooks:
| Webhook | Description |
|---|---|
| Occurs when an asynchronous payment request is successfully initiated. For example, a payment that requires an additional action to complete it, such as the cardholder completing a redirect to the alternative payment method's (APM) checkout page. |
| Occurs when an APM payment expires (not applicable to 3DS payment expiries). |
| The bank declined the payment request due to a technical or fraud-related issue. |
| Occurs when the customer approves the payment on their banking page. |
| Occurs when a capture is successful. |
| Occurs when a refund is successful. |
| Occurs when a refund is declined. |
| Occurs when the customer completes the initial payment and the agreement becomes active. You can now use the payment instrument for subsequent payments. |
| Occurs when the initial payment fails and an agreement is not created. The payment instrument cannot be used. |
| Occurs when the customer, you, or Bancontact revokes the agreement. The payment instrument status changes, and any future payments requested using the payment instrument fail. |
The following sections describe the order in which each notification is sent, depending on the payment lifecycle:
You can receive the following response codes when processing Bancontact payments:
| Response code | Description |
|---|---|
| Approved |
| Deferred capture |
| The transaction failed for unknown reasons. |
| The external system declined the transaction. For example, bank account not accepted, not enough funds. |
| The payment gateway declined the transaction. For example, for risk management reasons. |
| Error / Invalid request parameters. |
| The customer canceled the payment. |
| There was a timeout while waiting for the transaction result. The customer either never completed the transaction and left the payment page open, or they closed the browser. |
| Administration error. For example, a configuration error. |
| System malfunction. |