Obriym CRMObriym CRMCustomer flow workspace
AIFeaturesGetting startedPricingRoadmapIntegrationsBlog
Sign inGet started
AIFeaturesGetting startedPricingRoadmapIntegrationsBlog
Payments · Mollie

Let them pay the way they already pay

A Dutch buyer reaches for iDEAL, a Belgian for Bancontact, a Pole for BLIK. One Mollie connection puts all of them behind a link you raise from the order — and the payment comes back to that order by itself.

Open your workspaceAll integrations
  • iDEAL — the default in the Netherlands, where a card is the unusual choice
  • Bancontact — Belgium's own debit scheme
  • BLIK and Przelewy24 — how Poland actually pays online
  • SEPA direct debit and bank transfer for invoices that are settled by bank
  • Cards, Apple Pay and Google Pay for everyone else

Which methods appear depends on what you enable in your own Mollie profile and on the buyer's country — the connection test tells you exactly what is switched on.

A card form is the wrong default in half of Europe. Mollie exists because the method a buyer trusts is local — a bank redirect in the Netherlands, a bank app in Poland, a debit scheme in Belgium — and abandoning a checkout over an unfamiliar payment screen costs more than any fee. This adapter puts that whole set behind one connection, raised from the order your team already has open. The buyer pays on Mollie's page; no card number, CVV or token ever reaches Obriym.

From an unpaid order to a recorded payment

  1. 1

    Raise the payment

    Open the order, go to the Payments tab and press “Payment link”. Enter the full total or a deposit; the CRM asks Mollie for a checkout page and hands you the link.

  2. 2

    The buyer picks their own method

    Mollie shows what is available for their country and your profile. Nothing about that choice needs to reach the CRM in advance.

  3. 3

    The CRM checks before it believes

    Mollie notifies the CRM that something changed. The CRM then reads the payment back over the authenticated API and records the result on the order it came from.

What the adapter does

A forged notification cannot move money

Mollie deliberately sends only a payment id and no status at all. The CRM answers by fetching that payment with your API key and trusting nothing else — so a fake notification can name an id but can never claim it was paid.

The link's life is Mollie's answer, not our guess

How long a payment stays open depends on the method the buyer picks — around fifteen minutes for iDEAL, up to two weeks for a bank transfer. Mollie tells developers not to predict it, so the CRM stores what Mollie reports rather than the term it hoped for.

Your store's payments come here too

If your own shop already charges through the same Mollie profile, those payments arrive as well. Each is matched to its order where possible, and anything unmatched waits in the Payments journal to be linked by hand — never silently dropped.

Test mode is labelled, not hidden

A test key exercises the entire flow and moves no money. The connection test says plainly which mode a key is in, so a test key can never sit behind a green badge pretending to take real payments.

Currencies, and the one that is missing

Mollie settles in 28 currencies — euro, pound, złoty, koruna, krone, dollar and more. It does not support the Ukrainian hryvnia, which is the default currency of a new Obriym workspace: a hryvnia order cannot be charged through Mollie, and the CRM says so before the request leaves rather than surfacing a provider error afterwards. Price the order in euro or dollars, or raise that link through a hryvnia provider instead.

Frequently asked questions

Does Obriym see my customers' card or bank details?
No. The buyer completes the payment on Mollie's own page. The CRM receives the outcome, the amount and Mollie's payment reference — nothing else.
Mollie's webhook has no signature. Is that safe?
It is safer than a shared secret, and deliberately so. The notification carries only an id and no status, so the CRM asks Mollie's API what actually happened using your key. Someone who forges a notification achieves nothing: they cannot make an authenticated read say a payment succeeded.
Why does the link sometimes expire sooner than the term I chose?
Because Mollie decides that, not the CRM. An iDEAL or card payment stays open for roughly fifteen minutes; a bank transfer for up to two weeks. Mollie's own guidance is not to predict it, so the CRM shows the expiry Mollie reports.
Which payment methods will my buyers see?
The ones you have enabled in your Mollie profile that are available for the buyer's country and the amount. Run the connection test on the adapter page and it lists exactly what is switched on today.
Can I try it without moving real money?
Yes. Save a test key instead of a live one — the whole flow works and no money moves. The adapter labels the mode so nobody mistakes one for the other.
Can I charge a deposit rather than the full amount?
Yes. Enter any amount up to what is still outstanding; the order is tracked as partly paid and you can raise another link for the rest.

One connection, the payment methods Europe expects

Connect Mollie once, then raise a link from any order without leaving the CRM.

Start for free
Obriym CRMObriym CRMCustomer flow workspace

Obriym CRM is a focused workspace for sales teams and e-commerce operations. Leads, deals, orders, and customer retention in one place.

Product by OBRIYM

  • crm@obriym.com
  • OBRIYM
  • Serhii Oberemchuk

Individual Entrepreneur Oberemchuk Serhii Oleksandrovych · State reg. 178752761226

Product

  • AI
  • Features
  • Getting started
  • Pricing
  • Compare
  • Blog
  • Roadmap
  • Integrations
  • API Reference

Company

  • About OBRIYM
  • Founder
  • Contact
  • Roadmap

Developers

  • For developers
  • OpenAPI spec
  • JS Widget
  • Lead intake API
  • Orders API

©2026Obriym CRM by OBRIYM. Built for production sales and e-commerce teams.

Terms of UseTerms of ServicePayment & RefundsPrivacy PolicySubprocessorsData ProcessingLegal detailsData DeletionPricingAPI Docs