iDEAL in,
and then the rest.
Creating a Mollie payment is a few lines of code. What people underestimate: the payment is only really in when the webhook says so, not when the customer comes back to your thank-you page. Confuse the two and you ship orders that were never paid for.
What goes wrong when you build it yourself.
The thank-you page decides the status
The customer closes the tab, or comes back without paying. With Mollie the webhook leads; the redirect is only what the customer sees.
The webhook is unreachable
Tested locally, put behind a login or blocked by a firewall. Then every payment stays on 'open'.
Amounts come from the client
If the amount is sent from the browser, it can be changed in the browser. That has to be calculated on the server.
Refunds are manual work
Every refund by hand in the Mollie dashboard, after which your own bookkeeping knows nothing about it.
Recurring direct debit is missing
Subscriptions with a first iDEAL payment and automatic collection after need a mandate. That gets skipped often.
No trace afterwards
Without logging per payment, a discussion with a customer or the bookkeeper becomes a hunt through the dashboard.
From pay button to bookkeeping that adds up.
Decide what has to happen after payment
Release the order, grant access, send an invoice or ping a colleague. That is the actual work, not the pay button.
The server calculates, Mollie collects
Amounts and discounts are calculated and recorded server-side. The customer cannot change anything along the way.
The webhook as the only truth
Publicly reachable endpoint, status always re-fetched from Mollie, and processed idempotently so a duplicate notification does not become a duplicate order.
What comes after
Confirmation email, invoice, refunds from your own admin screen, and for subscriptions the mandate for automatic collection.
- ✓iDEAL, credit card, Bancontact and PayPal
- ✓A webhook that tracks payment status reliably
- ✓Amounts that cannot be tampered with
- ✓Refunds from your own admin screen
- ✓Invoices and confirmations that go out automatically
The first opinion costs you nothing: send me the repository or a link and I will tell you honestly whether building on beats starting over.
Clients rate me
5 stars on average.
Translated from the Dutch originals on Google.
I am Bas Voets. Since 2021 I have been building websites, client portals and business software for small and mid-sized companies, from Hazerswoude-Dorp in the Netherlands. From first call to launch you talk to me, not to an account manager.
What does a Mollie integration cost?
Can you connect Mollie to my existing site?
Can I collect subscriptions through Mollie?
How do I know nothing goes wrong with payments?
Tell me what you
want to build.
A half-hour call. You get an honest answer about what it costs, how long it takes and whether building it is smart at all.
Have your current site or tool scanned
You do not have to want to buy anything yet. Send what you have and I will tell you honestly what I would keep, what I would replace and whether that is worth the investment. Including when the answer is that you are better off doing nothing.
The scan is a first impression, not a security audit.
- 01Send a link to your site, your tool or your repository
- 02I look at speed, structure, data and security
- 03Usually within two working days you hear what I would replace and what that costs