Commercetools Mollie integration for faster, local payments at scale
Connect Commercetools with Mollie to add cards, iDEAL, Bancontact, and more, with cleaner checkout flows, fewer payment drop-offs, and simpler reconciliation across markets.
%201.svg){kind=small}
• Checkout creates a Mollie payment (and, where applicable, an order) and stores Mollie IDs in Commercetools Payment custom fields for traceability.
• Payment method selection is mapped to Mollie payment method codes, with amount, currency, locale, and shopper context passed in the create-payment request.
• Mollie webhooks drive asynchronous updates, mapping Mollie statuses to Commercetools Payment and Order state transitions (authorized, paid, failed, canceled, refunded).
• Redirect URLs return the shopper to Commercetools after 3DS or external authorization, while final payment truth comes from Mollie webhook events.
• Refunds and cancellations are initiated as Mollie API calls and written back to Commercetools as transactions, including partial refund amounts and references.
• Event payloads are validated and logged, with idempotency handling to prevent duplicate updates when Mollie retries webhook delivery.
.png)
Why choose scandiweb to handle Commercetools integration for you?
How does the Commercetools Mollie payment integration sync authorization, capture, and refund status back to Commercetools?
We map Mollie payment events to Commercetools payment and order states via API and webhooks. This keeps payments, captures, cancellations, and refunds consistent across the checkout and post-purchase flow.
Can I use Mollie payment methods like iDEAL and Bancontact in a Commercetools checkout with localized currencies?
Yes, Mollie supports local methods and currency handling, and Commercetools can route them by market and channel. The integration applies the right method set per locale without hardcoding the checkout.
What data moves between Commercetools and Mollie for reconciliation and finance reporting?
Typically, order IDs, payment references, amounts, statuses, refunds, chargebacks, and settlement identifiers are passed and stored for auditability. You can also enrich the payload with customer and cart context when needed.
How do you handle failed payments and pending orders in a Commercetools Mollie integration?
We implement clear state transitions and retry logic, and we separate “payment pending” from “order confirmed” rules. This reduces stuck orders, duplicate captures, and manual support work.
How long does a Commercetools Mollie integration take, and who builds it?
Timelines depend on your checkout, tax, and fraud stack, but most builds start with a short discovery and a staged rollout. scandiweb has delivered 2,100+ eCommerce projects since 2003, so you get engineers who’ve seen payment edge cases before.
1. Submit your integration request
2. Join a free strategy & discovery call
We’ll review your business systems, identify key challenges, and uncover actionable opportunities.
3. Get a tailored proposal
Trusted by 700+ leading brands worldwide
