Accepting payments is no longer just a back-office function. It is a core part of the customer experience and a significant lever on both conversion and margin, yet most businesses treat it as a box to tick once and never revisit.
The difference between a payment method and a payment strategy is the difference between “we can take money” and “we take money in the way that maximizes completed orders, minimizes cost, and survives the situations that go wrong”. This article covers what that involves.
Offer the methods your customers already use
Payment preference is strongly regional, and getting this wrong costs orders at the last possible moment.
In the Netherlands, iDEAL dominates. A Dutch consumer who reaches checkout and does not see iDEAL frequently abandons rather than reaching for a card. Belgium has Bancontact. Germany leans toward invoice-based and direct debit methods to a degree that surprises outsiders. Card payment is the default in much of southern Europe.
If you sell across borders, the practical approach is to detect the customer’s country and present the relevant methods first rather than showing an identical list everywhere. This alone typically improves checkout completion.
Understand what you are actually paying
Headline rates conceal real differences. When comparing providers, look at the whole picture:
- Per-transaction fees, which differ substantially by method. An iDEAL payment usually costs a fixed amount of a few tens of cents, while a European card typically costs a percentage plus a small fixed fee. A high-value order paid by iDEAL is dramatically cheaper than the same order paid by card.
- Non-European cards, which carry noticeably higher rates.
- Currency conversion, which is often the largest hidden cost for businesses selling internationally.
- Chargeback fees, charged per dispute regardless of who wins.
- Payout timing, which is a cash flow question rather than a cost, but frequently matters more.
Work out your blended cost per order using your actual method mix, not the advertised rate. Businesses that do this often find the cheapest-looking provider is not the cheapest for them.
Match the model to how you actually sell
One-off purchases are the simplest case. The priorities are speed, familiarity, and not surprising anyone with fees at the final step.
Subscriptions introduce a different problem: failed renewals. Cards expire, funds are unavailable, and authentication requirements interrupt automatic charges. A subscription business without intelligent retry logic, card update services, and a dunning sequence loses customers who never intended to leave. This is usually the single largest recoverable loss in a subscription operation.
Invoicing suits B2B, where net terms are expected. The strategy question is how you chase payment: automated reminders on a defined schedule recover far more than ad hoc chasing, and they remove an awkward conversation from your team.
Marketplaces and platforms paying out to third parties face the most complex situation, involving split payments, seller onboarding, identity verification, and reconciliation. This is specialist work and it is worth treating as such from the beginning.
Strong customer authentication, handled properly
European rules require an extra verification step for many online payments, typically a confirmation in the customer’s banking app. This is not optional, and how your checkout handles it makes a measurable difference.
The failure mode is subtle. A payment that requires authentication is no longer instantaneous: the customer leaves your site, confirms, and returns. If your checkout does not handle that return journey correctly, you get orders marked as failed that the customer believes they completed, or worse, payments taken with no order created.
Exemptions exist for low-value and recurring transactions, and a well-configured integration applies them where permitted, reducing friction without breaking compliance.
Plan for the things that go wrong
A strategy is largely defined by how it handles failure.
- Failed payments need a clear recovery path. Tell the customer what happened in plain language and let them retry with another method rather than sending them back to an empty cart.
- Refunds should be issuable by your team without a developer. If refunding requires engineering time, refunds get delayed and complaints escalate.
- Chargebacks need a process for gathering evidence quickly. Most businesses lose disputes they could have won because nobody assembled the delivery confirmation in time.
- Reconciliation must be automatic. Manual matching of payouts to orders consumes finance time every month and produces errors that surface at year end.
- Provider outages happen. Businesses with meaningful volume increasingly keep a secondary provider configured so that an outage means degraded service rather than no revenue.
Connect payments to your accounting
The step most often skipped. When payments feed your bookkeeping automatically, with correct VAT treatment per country and per customer type, you eliminate a recurring monthly task and a recurring source of error.
This matters more than it sounds for EU sellers. VAT rates differ by country, B2B sales within the EU are typically reverse charged against a validated VAT number, and getting this wrong is discovered late and corrected expensively.
Frequently asked questions
Which provider should we choose?
For Dutch businesses selling domestically, Mollie is usually the simplest and most cost-effective, particularly for iDEAL. Stripe is stronger for subscriptions and international card payments. Adyen makes sense at higher volume. The right answer depends on your method mix, your order values, and whether you need recurring billing. We compare the real cost against expected volume before recommending one.
Can we use more than one provider?
Yes, and above a certain volume it is sensible. Route methods to whichever provider is cheapest for them, and keep a fallback for outages. It adds integration complexity, so it is worth doing once volume justifies it rather than at launch.
Do we need to worry about PCI compliance?
Far less than most people fear, provided card details are entered directly into fields hosted by your provider and never touch your server. This keeps you at the lightest compliance level. Building your own card form moves you into a much heavier regime and there is almost never a good reason to do it.
How long does a payment integration take?
A straightforward one-off checkout is typically a week. Subscriptions with invoicing and retry logic take one to two weeks. Marketplace payouts take longer. Provider account approval can add several days and sits outside our control. Our packages are on the payments page.
Where to start
Pull your last three months of transactions and calculate your blended cost per order, your checkout completion rate by device, and, if you run subscriptions, your failed renewal rate. Those three numbers tell you whether you have a payment strategy or merely a payment method.
We implement payment stacks that fit how a business actually sells, including the recovery and reconciliation work that determines whether the setup holds up in practice. One honest note: if your current website is dated, a new store with payments built in often costs less than retrofitting them into the old one, and we will tell you which route makes more sense. Describe your situation and we will be specific.
