Bancontact is Belgium’s dominant payment method: a bank-linked debit scheme that lets shoppers pay by authenticating with their own bank instead of typing in card details. It holds roughly 78-80% of Belgian ecommerce payment share (Purse.eu, 2025; Stripe, 2021), which makes it close to mandatory for any business selling into Belgium online rather than an optional local method to add later. Here’s what a Bancontact payment actually is, how it moves money, and what changes if you accept it through a payment orchestration platform instead of a direct PSP integration.
Key takeaways:
- Bancontact holds ~78-80% of Belgian ecommerce payment share, making it close to mandatory for any business selling into Belgium online
- 2.5 billion Bancontact/Payconiq payments were processed in 2024, up 4.5% year over year
- The bank-authentication step satisfies PSD2 SCA by construction, so no separate 3D Secure challenge is needed
- Wero is entering Belgium alongside Bancontact, not replacing it; both rails coexist
- Accepting Bancontact through an orchestration layer makes it a configuration change at the platform level, not a new codebase to maintain
What is Bancontact?
Bancontact started in 1989 as Bancontact/Mister Cash, a Belgian domestic card scheme. In 2018, it merged with Payconiq Belgium to form the Bancontact Payconiq Company, bringing card payments and a QR/app-based mobile wallet under one operator (Stripe; Wikipedia). Today there are 17.4 million Bancontact cards in circulation, more than Belgium’s entire population, linked to 20 Belgian banks (Stripe, via Akurateco).
It’s a debit method, not a credit one. Bancontact sits closer to iDEAL than to a card network like Visa or Mastercard: the transaction pulls directly from the payer’s bank account rather than extending credit. That said, most Belgian debit cards carry a Bancontact badge alongside a Maestro/Mastercard Debit or Visa Debit co-badge, and payment can also be completed entirely without a physical card, through the Bancontact app.
How Bancontact payments work
Bancontact isn’t one flow, it’s three, and which one a payer uses depends on the channel:
- Card and PIN, in person or online with a card reader. The payer taps or inserts their card. Contactless payments above roughly €25-50 require PIN entry rather than tap-only authentication, a common threshold that can vary by issuer.
- In-app QR or bank-app approval. The payer scans a QR code with the Bancontact app, or approves the transaction directly inside their banking app, without touching a card at all.
- Online redirect. At checkout, the payer selects Bancontact, is redirected to their bank or the Bancontact app to authenticate, and is then redirected back to the merchant with a confirmed or failed result.
All three routes end at the same place: the payer authenticates with their own bank, and the merchant gets a confirmation rather than raw card data. That authentication step matters beyond the checkout experience. Under PSD2, it’s itself a Strong Customer Authentication event, something the payer has (their phone or bank app) combined with something they know or are (a PIN or biometric), which satisfies the regulation’s SCA requirement without a separate 3D Secure challenge layered on top (European Banking Authority).
Why Bancontact matters for ecommerce in Belgium
Key stat: Bancontact and Payconiq processed more than 2.5 billion payments in 2024, up 4.5% year over year. Of those, 382 million were online transactions, and 90% of those online payments were completed via smartphone (Bancontact Payconiq Company, 2025).
The full breakdown: 1.35 billion in-store contactless card payments, 471 million smartphone payments, 70.4 million mobile P2P transfers, and 65 million in-store smartphone payments.
That volume sits inside a Belgian B2C ecommerce market valued at roughly $21.85 billion in 2025, projected to reach $26.99 billion by 2029 (ResearchAndMarkets, via GlobeNewswire, 2026). A merchant selling into Belgium without Bancontact isn’t missing a niche preference. They’re missing the payment method most Belgian online shoppers reach for first.
Bancontact, Payconiq, and Wero: what’s changing (and what isn’t)
Two things are moving at once here, and conflating them leads to the wrong conclusion. Starting in March 2026, the Payconiq by Bancontact app is being renamed Bancontact Pay, and the Payconiq brand is being retired (BNP Paribas Fortis). Separately, Wero, the pan-European digital wallet backed by the European Payments Initiative, is rolling out in Belgium alongside Bancontact, not replacing it (BNP Paribas Fortis).
Neither of those is a Bancontact deprecation. Bancontact’s 2024 volume grew 4.5% year over year, the opposite trajectory of a rail on its way out. What’s changing is the app name on the mobile wallet piece and a second wallet option entering the market beside it. A merchant that already accepts Bancontact doesn’t need to rip anything out; a merchant weighing whether to add Bancontact now shouldn’t treat the Wero rollout as a reason to wait, since the two are coexisting rather than one displacing the other.
Bancontact vs. cards, iDEAL, and other European rails
Bancontact belongs to a category of European bank-linked local payment methods that share a redirect-and-authenticate pattern but differ by country and underlying rail:
| Method | Region | Mechanism | Status |
|---|---|---|---|
| Bancontact | Belgium | Bank-linked debit, card/app/redirect | Active, growing |
| iDEAL | Netherlands | Bank redirect | Active, dominant Dutch method |
| SEPA direct debit | Eurozone | Direct debit mandate | Active |
| Visa / Mastercard | Global | Card network | Active |
| Wero | Belgium, Netherlands, France, Germany | Pan-European wallet (EPI) | Rolling out alongside existing rails |
The pattern across this table is regional specificity: each rail dominates its home market and barely registers outside it. A payment stack built for one European country’s preferred method needs a different one for the next, which is the same problem SEPA and iDEAL integrations create individually. Bancontact isn’t an exception to that pattern, it’s a clean example of it.
Integrating Bancontact: technical requirements and payment flow
From a merchant’s side, accepting Bancontact doesn’t require a Belgian bank account. The payer needs a participating Belgian bank account or a Bancontact-linked card; the merchant’s PSP or orchestration platform handles settlement on the other end.
The integration shape depends on which flow you’re supporting. PayPal’s developer docs, for example, expose Bancontact through two separate integration paths on the same PSP: a JavaScript SDK flow and an Orders API flow, each with its own request shape (PayPal Developer, PayPal Developer). CM.com’s docs describe a similar split between hosted-redirect and API-driven flows (CM.com). In practice, that means:
- Enabling Bancontact as a payment method in your PSP’s configuration or
payment_method_typesequivalent - Handling the redirect to the bank/app authentication step and the return callback
- Building webhook handling for the confirmation event, distinct from a card auth/capture response
- Not building a separate SCA or 3D Secure flow for this method, since the bank-authentication step already satisfies PSD2 SCA by design
None of this is unusually hard on its own. It’s the same shape of work every bank-redirect method requires, with its own field names, webhook events, and edge cases per PSP.
Integration challenges developers hit in practice
The friction shows up at the second or third provider, not the first. Adyen, Stripe, Worldpay, PayPal, and CM.com each document Bancontact separately, with different request/response shapes, different webhook event names, and different redirect-handling requirements (Worldpay, Stripe Documentation, PPRO). Add Bancontact to a stack that already runs two PSPs, and you’re not writing one integration, you’re writing and maintaining two, each with its own deprecation and versioning cycle.
Spreedly already lists Bancontact among its supported methods (spreedly.com/payment-methods/bancontact), which is worth noting for a different reason than the sales pitch: it confirms accepting Bancontact through an orchestration layer is a validated, already-solved pattern, not an experimental one. A developer evaluating whether to route Bancontact through an abstraction layer isn’t the first team to ask that question.
Accepting Bancontact through a payment orchestration platform
The problem Bancontact exposes isn’t really about Bancontact. It’s what happens every time you add a payment method that only one or two of your existing PSPs support well: a new integration surface, a new webhook contract, a new thing that breaks when a provider changes its API.
Orchestra’s Library captures the payment on the client side, whichever method the payer chooses, so card and bank details never touch your servers, while the REST API handles what happens after capture: charges against stored tokens, refunds, and recurring billing, against whichever gateway processed the original transaction. Orchestra routes transactions to whichever PSPs in its network support the payment methods and regions a merchant needs, and adds new PSP or payment-method connections at no additional integration cost.
Tip: Check current PSP coverage for Bancontact specifically before committing a build; network coverage changes as new providers connect.
That’s the same argument that applies to any local payment method your platform needs to support as you expand into new markets. Maintaining each one as a direct, per-PSP integration multiplies your integration surface every time you add a method or a provider changes its roster. Routing Bancontact through an orchestration layer instead means adding it is a configuration change at the platform level, not a new codebase to maintain, and the same is true for whatever cross-border settlement questions come up next as you add markets beyond Belgium.
Frequently Asked Questions
What is Bancontact?
Bancontact is Belgium’s dominant domestic payment method, a bank-linked debit scheme run by Bancontact Payconiq Company that lets shoppers pay by authenticating with their own bank rather than entering card details. It holds roughly 78-80% of Belgian ecommerce payment share.
Is Bancontact a debit or credit card?
Debit, not credit. Bancontact is a bank-redirect/debit method tied directly to a Belgian bank account, closer to iDEAL than to a card network like Visa or Mastercard, though most Belgian debit cards carry both a Bancontact badge and a co-badge (Maestro/Mastercard Debit or Visa Debit).
How do I pay with Bancontact online?
The shopper selects Bancontact at checkout and completes authentication one of three ways: entering card details with a card reader/app, scanning a QR code in the Bancontact Pay app, or approving the payment directly in their banking app, then is redirected back to the merchant with a confirmed or failed result.
Do I need a Belgian bank account to accept Bancontact?
No, the merchant doesn’t need a Belgian account. A PSP or orchestration platform that supports Bancontact handles settlement. The shopper is the one who needs a participating Belgian bank account or a Bancontact-linked card.
Is Bancontact the same as Payconiq?
They’re run by the same company (Bancontact Payconiq Company, formed by a 2018 merger) but aren’t identical. Bancontact centers on card and bank-app authentication; Payconiq by Bancontact centered on QR-code, mobile-first flows. The Payconiq brand name is being retired in 2026 in favor of “Bancontact Pay.”
What is Bancontact Pay, and what happened to Payconiq?
Bancontact Pay is the renamed Payconiq by Bancontact app, rolling out from March 2026 as the Payconiq brand is retired. This is a brand consolidation, not a shutdown. Bancontact itself continues and its transaction volume is still growing: 2.5 billion Bancontact/Payconiq payments in 2024, up 4.5% year over year.
Does Bancontact require 3D Secure or extra SCA steps?
No separate 3DS challenge is needed. Bancontact’s bank-authentication step (PIN, biometric, or in-app approval) is itself a multi-factor authentication event, which satisfies PSD2’s Strong Customer Authentication requirement by construction.
What is Wero, and does it replace Bancontact?
Wero is a pan-European digital wallet backed by EPI (European Payments Initiative). In Belgium, Wero is rolling out alongside Bancontact rather than replacing it. The two coexist, with the system selecting whichever rail the recipient’s bank supports.
Can Orchestra route Bancontact payments?
Orchestra routes transactions to whichever PSPs in its network support the payment methods and regions a merchant needs, and adds new PSP or payment-method connections at no extra integration cost. Check current PSP coverage for Bancontact specifically before committing a build to it.
