Accept iDEAL payments alongside cards on one payment gateway.


iDEAL is the bank-redirect method Dutch shoppers reach for at checkout. On BazPay it sits behind the same REST API call as cards and wallets — one charge object, one signed webhook, one settlement balance. Confirmation lands in seconds and no card number changes hands.

Built for merchants across the EU, UK, Australia, Canada and New Zealand selling into the Netherlands: e-commerce, subscription software, professional services and digital publishers. Add iDEAL from the dashboard, not through a separate onboarding.

Why merchants add iDEAL alongside card acceptance

iDEAL is not a rounding-error method for a merchant serving the Netherlands — it is typically the first-choice payment for Dutch shoppers. Four properties keep the integration light and the reconciliation clean.

  • First-class method, not a redirect afterthought

    iDEAL sits behind the same REST API call as cards, wallets and other local APMs. One charge object, one signed webhook envelope, one reporting surface — Dutch checkout is not a separate integration to maintain.

  • Near-instant payment confirmation

    iDEAL runs on the shopper's own banking environment. The confirmation reaches BazPay in seconds and fires the same charge.succeeded webhook your fulfilment stack already listens for.

  • Low chargeback exposure on iDEAL

    Because iDEAL is authenticated inside the shopper's bank app, cardholder-dispute chargebacks do not apply — a shopper who wants a refund does so through the merchant. That is why iDEAL is a common addition alongside cards for larger Dutch orders.

  • Reconciles into the same balance as cards

    iDEAL settlements land in your local settlement account alongside card acquiring lines. Every settled iDEAL charge appears on the same statement, keyed by rail, so finance teams do not open a second portal to close the book.

The iDEAL flow, end to end

Six stages describe a single iDEAL payment from checkout to settled dollar. Each stage is visible in the dashboard and the confirmation stage fires the same signed webhook your card flow uses.

  1. Shopper picks iDEAL

    iDEAL appears alongside card and wallet options in your checkout — hosted page, hosted fields or REST API.

  2. Bank select

    The shopper picks their bank from the iDEAL bank list. Modern iDEAL flows can also open the shopper's default banking app directly.

  3. Redirect to bank

    The shopper is redirected to their own bank environment (web or app) to approve the payment with their usual authentication.

  4. Bank approves

    Once approved, the bank returns the shopper to your success URL and confirms the payment to BazPay through the iDEAL scheme.

  5. Webhook fires

    BazPay fires a signed charge.succeeded webhook to your fulfilment endpoint — the same event handler cards use.

  6. Settle in EUR

    Funds reconcile per iDEAL settlement cycle and land in your local settlement account alongside your other BazPay volume.

iDEAL vs a card payment on the same order

iDEAL and cards do different things well. Most Dutch checkouts show both and let the shopper decide. The comparison below shows where each earns its place.

iDEAL compared with a card payment on the same order
Dimension iDEAL Card + 3-D Secure 2
Authentication Shopper's own bank app Card + 3-D Secure 2 challenge on risk
Confirmation Near-instant, bank-driven Authorisation code from issuer
Chargeback exposure No cardholder-dispute chargebacks Cardholder dispute rights apply
Refund flow Refund to original settlement account via iDEAL Refund to original PAN via scheme
Currency EUR only Multi-currency presentment
Fits best for Dutch checkout, higher-ticket orders International traffic, subscription renewals

Card-side detail on card and APM processing. Bank-rail context on Single Euro Payments Area processing and SEPA and SEPA Instant.

Features that ship with iDEAL out of the box

Every capability below is on the standard integration — no premium tier for iDEAL, and no separate SDK. If it works for cards on BazPay, it works for iDEAL charges too.

  • One charge object

    Set payment_method: "ideal" on the charge request. Everything else stays the same as a card charge; iDEAL is not a bolt-on SDK.

  • Bank selector UI

    The hosted checkout and drop-in JS render the iDEAL bank selector automatically. Custom integrations can query the bank list from the API and render it themselves.

  • charge.succeeded webhook

    The same signed HMAC event that fires for a card success fires for an iDEAL success — one fulfilment handler covers both.

  • Refunds

    Full and partial refunds return to the shopper's original settlement account through the iDEAL refund flow, initiated from the API or dashboard.

  • Real-time analytics

    Approval, cancellation and expiry outcomes on iDEAL appear in real-time analytics alongside card decline codes for the same order.

  • Metadata propagation

    SKU, order and buyer references on the charge metadata ride through to settlement and refund events, so reconciliation stays SKU-level per iDEAL payment.

  • Plugin support

    Maintained plugins for WooCommerce, Magento 2, PrestaShop and Shopware expose iDEAL alongside cards with a single configuration screen.

  • EUR-only settlement

    iDEAL is a EUR method — no multi-currency conversion needed for Dutch shoppers, so the interchange++ statement stays clean.

Create an iDEAL charge with one REST call

The payment_method field selects iDEAL. Pass amount and currency (always EUR for iDEAL). The response returns a canonical charge object with a next_action that redirects the shopper to the iDEAL flow. After bank approval, the signed webhook fires.

POST /v1/charges
Idempotency-Key: 8f1c-2b3a-9e4d
{
  "amount": 4990,
  "currency": "EUR",
  "payment_method": "ideal",
  "return_url": "https://your-shop.example/checkout/return",
  "metadata": { "order_id": "ORD-10842" }
}

The response returns the charge with status: "requires_action" and a redirect URL for the shopper. Once the bank approves, the status moves to succeeded and the webhook fires. Full schema in the API reference.

Where iDEAL earns its place at checkout

The four merchant profiles below already rely on iDEAL on BazPay for the Dutch part of their traffic. Each uses the same charge object and the same signed webhook.

  • Dutch e-commerce storefronts

    DTC brands selling into the Netherlands add iDEAL as the primary local method alongside card and Apple Pay. Storefront plugins ship with the bank selector already wired in.

  • Higher-ticket B2B invoicing

    Professional-services and B2B software vendors use iDEAL for larger Dutch invoices where chargeback exposure on a card would be a concern.

  • Ticketing and event businesses

    Events with a Dutch audience surface iDEAL first at checkout for the fastest completion path on higher-value ticket purchases.

  • Digital-goods sellers

    Software licences, courses and downloadable content use iDEAL alongside cards; the near-instant confirmation triggers the fulfilment webhook in seconds.

Out of scope for BazPay: adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection and MLM. Buyer's shortlist on payment processors; build motion on integrated payment solutions; ongoing service envelope on gateway services.

Security and compliance signals for iDEAL processing

iDEAL is a bank-authenticated method — the shopper approves the payment inside their own bank environment, so no card data is collected for iDEAL charges. That keeps the attack surface for iDEAL narrow by construction. PCI DSS Level 1 covers BazPay's broader environment; Authentication runs natively inside the shopper's bank for iDEAL and through 3-D Secure 2.2 for cards.

iDEAL scheme adherence
Bank-authenticated flow, no card data collected for iDEAL charges
Authentication
Native strong customer authentication runs inside the shopper's own bank
GDPR
In-region data residency; DPA on request
Currence rulebooks
Underlying settlement adheres to the Currence iDEAL rulebooks

Questions merchants ask about accepting iDEAL

What is an iDEAL payment, and where does it work?

iDEAL is a bank-redirect payment method popular in the Netherlands. The shopper picks their bank at checkout, is redirected to that bank's environment to approve the payment, and the merchant receives confirmation in seconds. iDEAL is EUR-only and primarily serves Dutch consumers; a broader region-wide account-to-account flow is emerging under the EU, UK and Commonwealth Payments Initiative.

How do I accept iDEAL payments on BazPay?

Set payment_method: "ideal" on the standard charge request, or enable iDEAL in your hosted checkout or storefront plugin. The bank selector renders automatically on the hosted surface; custom integrations can list banks through the API and render them themselves. Fulfilment listens to the same signed charge.succeeded webhook that cards use.

How fast is confirmation on an iDEAL payment?

The shopper approves the payment inside their own bank environment and the confirmation reaches BazPay within seconds. Your charge.succeeded webhook fires immediately after — treat iDEAL as a near-instant method for release-of-goods and licence fulfilment.

How do refunds work for iDEAL payments?

Refunds are issued via the API or dashboard and return to the shopper's original settlement account through the iDEAL refund flow. Full and partial refunds are supported; the refund event fires a signed webhook so your fulfilment stack can revoke the entitlement in the same handler that processes card refunds.

Ca iDEAL be used for subscription renewals?

The classic iDEAL flow is single-payment and bank-authenticated per transaction, which is not directly suited to silent renewals. For subscriptions on Dutch shoppers, BazPay typically pairs iDEAL for the initial payment with a BACS Direct Debit mandate or a card-on-file for subsequent renewals. The newer generation of iDEAL includes recurring-payment concepts that will slot into the same BazPay integration as they become generally available.

How does iDEAL compare with a card payment for the same order?

iDEAL runs inside the shopper's bank, so there are no cardholder-dispute chargebacks — refunds go through the merchant directly. Cards work internationally and support saved-card renewals; iDEAL is EUR-only and the Netherlands-first but wins on chargeback exposure and confirmation speed. Most Dutch checkouts offer both and let the shopper pick.

Do I need a separate contract to add iDEAL on BazPay?

No. iDEAL is enabled from the same merchant contract that covers card acquiring and other local payment methods. Turn iDEAL on from the dashboard, wire the API call, and it appears alongside your other methods without a second onboarding.

Which merchant types can accept iDEAL through BazPay?

Merchants across the EU, UK, Australia, Canada and New Zealand: e-commerce sellers, subscription software firms, professional-services businesses and digital publishers. BazPay does not board adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection or MLM merchants, and does not act as a merchant of record.

Add iDEAL to your Dutch checkout on one contract

Share your business model, monthly Dutch volume and existing stack. A named engineer will confirm boarding fit and turn iDEAL on alongside cards inside one working day. See also merchant acquiring, open banking and pricing.