A Mollie MCP for payment work your automations and agents can run
Connect one Mollie API key and payments, refunds, customers, mandates, subscriptions, payment links, chargebacks, settlements, and balance reports become workflow steps. An agent can look up a payment and put the refund behind an approval task, a scheduled run can reconcile a payout against the payments inside it, and every money moving node is flagged destructive so nothing irreversible happens by accident.
What the Mollie MCP connector does
The Mollie connector for Mattering Automations is 45 nodes on the Mollie API v2: payments from creation through update and cancel, refunds, customers with their mandates and recurring subscriptions, payment links, chargebacks, the enabled and full payment method catalogs, and the organization level reporting surface of settlements, settlement payments, balances, windowed balance reports, invoices, profiles, and onboarding status. One credential authenticates all of it, a Mollie API key sent as a bearer token, and there is one host for both modes: a profile API key's prefix decides whether you reach test data or live data, and an organization level token carries its mode in the request instead, which is why this connector has no environment switch to get wrong.
Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An agent can find a payment with Mollie: List Payments, read its refunded amount with Mollie: Get Payment, and draft the refund for a person to approve, without anyone opening the Mollie dashboard, and the same nodes are on the canvas for the scheduled and triggered work that runs without an agent at all.
This connector moves real money, so the safety modeling is stated on the nodes themselves rather than buried in a page. Of the 45 nodes, 30 read and 15 act, and seven carry a destructive flag: Mollie: Cancel Payment, Mollie: Create Payment Refund, Mollie: Cancel Payment Refund, Mollie: Delete Customer, Mollie: Revoke Mandate, Mollie: Create Subscription, and Mollie: Cancel Subscription. Two of them cascade, because Mollie says they do: deleting a customer cancels that customer's mandates and subscriptions, and revoking a mandate cancels the subscriptions connected to it. Creating a payment, a customer payment, or a payment link is a reversible write instead, because none of them charge anyone: they mint an unpaid checkout or a shareable link, and money only moves when the shopper completes it. Every write node exposes Mollie's documented idempotency key as an optional field, so a retry inside Mollie's replay window returns the original result rather than creating a second payment, refund, or subscription.
The scope is deliberate rather than exhaustive. Mollie's own documentation no longer recommends the Orders API and points to Payments instead, so this connector follows that advice. The platform operator surfaces, clients, business accounts, balance transfers, routing, and capabilities, need partner or OAuth app credentials and describe a marketplace product rather than the merchant product this catalog serves; the organization, profile, and onboarding reads that Mollie documents alongside them are here, because an advanced access token is enough for those. Payouts, captures, release authorization, point of sale terminals, and profile writes are all money movement or merchant configuration that belongs in a considered second pass or in the dashboard, not in an unattended workflow, so they are not here.
One connection, three surfaces
- Visual automations. Drag Mollie nodes onto the canvas and wire them to triggers, conditions, and other apps.
- AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
- The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.
Every Mollie node, ready to drop on the canvas
45 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.
Read and query nodes 30
Mollie: Get Balance
Read one balance: the available amount that can be paid out or refunded, and the pending amount still clearing. The alias primary works in place of an ID. The natural low balance check before a refund run. Needs an ORGANIZATION LEVEL credential.
Mollie: Get Balance Report
Summarize every movement on a balance between two dates: opening and closing amounts, plus totals per category (payments, refunds, chargebacks, transfers, fee prepayments, corrections). The from date is INCLUSIVE, the until date is EXCLUSIVE, and both are read in Central European Time, so a full month runs from the 1st to the 1st of the next month. The alias primary works in place of a balance ID. Needs an ORGANIZATION LEVEL credential.
Mollie: Get Current Organization
Read the organization the credential belongs to: name, email, locale, registered address, registration and VAT numbers, and when it was verified. Useful as an identity check for an organization level token. Needs an ORGANIZATION LEVEL credential (an access token), not a profile API key.
Mollie: Get Customer
Read one customer by its ID, including the stored name, email, locale, and metadata.
Mollie: Get Invoice
Read one Mollie invoice by its ID, with its status, amounts, fee lines, and a PDF download URL at data._links.pdf.href. To look one up by invoice number, use List Invoices with the reference filter. Needs an ORGANIZATION LEVEL credential.
Mollie: Get Mandate
Read one mandate by its ID and the ID of its customer. The details object carries the bank, card, or PayPal specifics of the authorization, and status tells you whether it can still be charged.
Mollie: Get Onboarding Status
Read the onboarding state of the organization: whether it is completed, and whether it can receive payments and settlements yet. The check to run before assuming a newly connected account can actually take money. Needs an ORGANIZATION LEVEL credential.
Mollie: Get Payment
Read one payment by its ID: status, amounts, method details, and the amounts already refunded or charged back. The isCancelable field tells you whether Cancel Payment will work right now.
Mollie: Get Payment Chargeback
Read one chargeback by its ID and the ID of its payment, including the reason code and description, the settlement amount deducted, and whether it was later reversed.
Mollie: Get Payment Link
Read one payment link by its ID, including whether it has been paid, whether it is archived, and the shareable URL at data._links.paymentLink.href.
Mollie: Get Payment Method
Read one payment method by its ID, including its logo and amount limits. Mollie returns 404 when the method is not available on the profile and 403 when it is available but not yet enabled, which makes this the check before offering a method in a checkout.
Mollie: Get Payment Refund
Read one refund by its ID and the ID of its payment. The status field (queued, pending, processing, refunded, failed, canceled) is what decides whether the refund can still be canceled.
Mollie: Get Settlement
Read one settlement, including the periods breakdown of revenue and costs per method for the payout. The literal values next and open also work in place of an ID, for the settlement being built and the one not yet closed. Needs an ORGANIZATION LEVEL credential.
Mollie: Get Subscription
Read one subscription by its ID and the ID of its customer: amount, interval, status, times remaining, and the next payment date.
Mollie: List All Chargebacks
List every chargeback across all payments, newest first, with the reason code and the amount deducted from the settlement. Rows land at data._embedded.chargebacks[]. This is the account wide view; use List Payment Chargebacks for one payment.
Mollie: List All Payment Methods
List every payment method Mollie offers, whether or not the organization is eligible for it. Use it to plan which methods to request; use List Payment Methods for what is actually usable today. Not paginated. Rows land at data._embedded.methods[].
Mollie: List Balances
List the organization's balances, including the primary one, with their available and pending amounts and payout settings. Rows land at data._embedded.balances[]. Needs an ORGANIZATION LEVEL credential (an access token), not a profile API key.
Mollie: List Customer Payments
List every payment linked to one customer, newest first. Rows land at data._embedded.payments[], the same shape as List Payments.
Mollie: List Customer Subscriptions
List the subscriptions of one customer with their status, interval, amount, and next payment date. Rows land at data._embedded.subscriptions[]. This is the source node behind the subscription picker, so it is scoped to a customer.
Mollie: List Customers
List customers, newest first. Rows land at data._embedded.customers[] and the next page URL at data._links.next.href. This is the source node behind every customer picker in this connector.
Mollie: List Invoices
List the invoices Mollie has issued to the organization for its own fees, newest first, with net, VAT, and gross amounts and the fee lines. Rows land at data._embedded.invoices[]. Needs an ORGANIZATION LEVEL credential (an access token), not a profile API key.
Mollie: List Mandates
List the mandates of one customer with their status (valid, pending, invalid) and method. Rows land at data._embedded.mandates[]. This is the source node behind the mandate picker, so it is scoped to a customer. The documented scopes filter is reachable through extra query.
Mollie: List Payment Chargebacks
List the chargebacks raised against one payment. Rows land at data._embedded.chargebacks[]. This is the source node behind the chargeback picker, so it is scoped to a payment.
Mollie: List Payment Links
List payment links, newest first, with their amounts, archived flag, and shareable URLs. Rows land at data._embedded.payment_links[]; note the embedded key is underscored, unlike the other list endpoints.
Mollie: List Payment Methods
List the payment methods enabled on the website profile, with their logos and minimum and maximum amounts. This is the Gate 1 auth probe: it needs no parameters and every credential tier can call it. In test mode Mollie also returns pending methods, and a profile that has requested nothing yet gets the most popular methods back. This endpoint is not paginated. Rows land at data._embedded.methods[].
Mollie: List Payment Refunds
List the refunds created for one payment, newest first. Rows land at data._embedded.refunds[]. This is the source node behind the refund picker, which is why it is scoped to a payment rather than the whole account.
Mollie: List Payments
List the payments created with the current website profile, newest first. Cursor paginated: rows land at data._embedded.payments[] and the next page URL at data._links.next.href. This is the source node behind every payment picker in this connector.
Mollie: List Profiles
List the organization's website profiles with their name, website, review status, and business category. Rows land at data._embedded.profiles[]. This is the source node behind the profile picker, and like the profile parameter itself it needs an ORGANIZATION LEVEL credential: a profile API key is already bound to one profile.
Mollie: List Settlement Payments
List the payments included in one settlement, in the same shape as List Payments, which is how a payout is reconciled against orders. Capture based methods such as Klarna appear as captures instead, so they are not listed here. Needs an ORGANIZATION LEVEL credential.
Mollie: List Settlements
List the payouts Mollie has made to the bank account, newest first, with their reference, status, amount, and the invoice they belong to. Rows land at data._embedded.settlements[]. Needs an ORGANIZATION LEVEL credential (an access token), not a profile API key.
Action nodes 15
Mollie: Cancel Payment
DESTRUCTIVE and IRREVERSIBLE: cancel an open payment. The payment moves to canceled and can never be paid; there is no uncancel, so a new payment has to be created instead. Only works while the payment reports isCancelable true, which depends on the method and usually lasts until the next business day.
Mollie: Cancel Payment Refund
DESTRUCTIVE and IRREVERSIBLE: stop a refund before it is executed. Mollie only allows this while the refund status is queued or pending, and a canceled refund cannot be reopened, so refunding again means creating a new refund. Returns no content on success.
Mollie: Cancel Subscription
DESTRUCTIVE and IRREVERSIBLE: cancel a subscription. Status becomes canceled and no further payments are scheduled; Mollie documents no way to reactivate one, so restarting billing means creating a new subscription. The customer's mandates are left alone.
Mollie: Create Customer
Create a customer record, the object mandates and subscriptions hang off. Nothing is charged and no email is sent; the customer also becomes visible in the Mollie dashboard. The new ID arrives at data.id.
Mollie: Create Customer Payment
Create a payment already linked to a customer, which is the Create Payment endpoint with the customer filled in. NO MONEY MOVES at creation: the shopper still completes the checkout at data._links.checkout.href. Linking the customer is what lets a returning shopper reuse a stored card and what a recurring sequence needs.
Mollie: Create Mandate
Record an existing authorization to charge a customer later. No money moves and no shopper is contacted. Only SEPA Direct Debit and PayPal mandates can be created directly this way; a card mandate is created by having the shopper make a first payment. The mandate ID arrives at data.id and is what a subscription bills against.
Mollie: Create Payment
Create a payment and get back a checkout URL at data._links.checkout.href to send the shopper to. NO MONEY MOVES here: the payment starts with status open and is only charged when the shopper completes the checkout, which is why this is a reversible write while refunds and cancellations are not. Set a webhook URL to receive the status change.
Mollie: Create Payment Link
Create a shareable payment link. NO MONEY MOVES: a payment only appears when someone opens the link and pays. The shareable URL comes back at data._links.paymentLink.href. Leave the amount blank to let the payer enter one, optionally with a minimum. Links do not expire unless an expiry is set, and a link can be archived later to stop accepting payments.
Mollie: Create Payment Refund
DESTRUCTIVE: this MOVES REAL MONEY back to the shopper and there is no un refund. The amount may be lower than the original payment for a partial refund. Mollie executes refunds after a delay, and Cancel Payment Refund is the only way back, and only while the refund is still queued or pending. Use the idempotency key so a retry cannot pay twice.
Mollie: Create Subscription
DESTRUCTIVE: schedules REAL RECURRING CHARGES against a mandate the customer has already authorized, so no further approval stands between this call and money moving, and cancelling later does not refund what was collected. The customer needs a valid mandate first. Set a start date to control when billing begins, and times to end the subscription after a fixed number of charges. The description must be unique among that customer's active subscriptions.
Mollie: Delete Customer
DESTRUCTIVE and IRREVERSIBLE: delete a customer. Mollie states that ALL mandates and ALL subscriptions of that customer are canceled with it, so recurring revenue stops and the authorizations cannot be restored. Past payments stay in the account's history.
Mollie: Revoke Mandate
DESTRUCTIVE and IRREVERSIBLE: revoke a mandate. The account or card can no longer be charged with it, and Mollie states that ALL connected subscriptions are canceled as well. A revoked mandate cannot be restored; the customer has to authorize a new one.
Mollie: Update Customer
Update a customer's name, email, locale, or metadata. Only the fields you fill are sent, so blank fields are left untouched rather than cleared.
Mollie: Update Payment
Update details of an existing payment: description, redirect and webhook URLs, metadata, method, locale, or due date. Only the fields you fill are sent, and Mollie states that updating a payment does not trigger a webhook call.
Mollie: Update Subscription
Change an active subscription's amount, interval, description, start date, number of times, webhook, or mandate. Future charges follow the new values and the change can be edited again; a canceled subscription cannot be updated. Fill BOTH amount fields when changing the amount, because Mollie expects the currency with the value.
Connecting Mollie takes one credential
Mollie authenticates every request with an Authorization header carrying the key as a bearer token, and the keys live in the Mollie Web App under Developers, API access tokens. Two tiers matter. A profile API key starts with test_ or live_, is scoped to one website profile, and covers 34 of the 45 nodes. An advanced access token, Mollie's organization level credential, is what the other eleven nodes need: settlements, settlement payments, balances, the balance report, invoices, the organization read, profiles, and onboarding status are all gated on it by Mollie, and each of those nodes says so in its own description. Both go in the same credential field, and the same field accepts either, so an account that needs both can hold two credentials and pick per workflow. The test half is available as soon as the account has a website profile, so you can build against it straight away, while processing real payments waits on Mollie's go live checklist, which asks for business verification, stakeholder details, and bank account information first. Mollie shows a key once at creation and cannot retrieve it afterwards, so a lost key means creating a new one and revoking the old.
Sign in to the Mollie Web App and open Developers, then API access tokens. Copy the key you need: a test_ or live_ profile API key for the payment, refund, customer, mandate, subscription, link, and chargeback nodes, or an advanced access token, the organization level credential an Admin creates, for the settlement, balance, invoice, organization, profile, and onboarding reads.
In Mattering Automations, open Connectors, click Add Connector, choose Mollie, and create a credential with the key.
Click Test Connection. Mattering calls Mollie's payment methods endpoint, which every credential tier can read: a method list, even a short one on a fresh profile, proves the credential, and a 401 with the title Unauthorized Request means the key is wrong, mistyped, or revoked.
All 45 Mollie nodes appear in the canvas palette. Run Mollie: List Payments first for payment IDs and Mollie: List Customers for the customer IDs that the mandate and subscription nodes need.
Common uses for the Mollie MCP
Refunds that a person approves and a retry cannot double
A support request arrives, Mollie: Get Payment reads the payment's status and how much of it is already refunded, a condition decides whether it is inside your policy, and only then does Mollie: Create Payment Refund run. That node is flagged destructive for the plain reason that it moves real money back to the shopper and there is no un refund. Two habits make it calm: put an approval task in front of it, and fill the idempotency key so a rerun of the same workflow cannot pay the same person twice. If the refund was a mistake and is still queued or pending, Mollie: Cancel Payment Refund is the only way back, and Mollie: Get Payment Refund is what tells you whether that window is still open.
Charge a customer without building a checkout
Mollie: Create Payment Link returns a shareable URL, and nothing is charged until someone opens it and pays, which makes it the safest money node in the connector for an agent to reach. Leave the amount blank and the payer enters one, optionally above a minimum, so the same node covers an invoice, a deposit, and a tip jar. Mollie: List Payment Links and Mollie: Get Payment Link tell a follow up workflow whether a link has been paid yet, so the reminder that goes out on day three can check first. When you do want a hosted checkout for a specific order instead, Mollie: Create Payment hands back the checkout URL to redirect the shopper to.
Recurring billing with the mandate step where it belongs
Recurring revenue in Mollie is a chain: a customer, then a mandate that authorizes charging them, then a subscription that bills against it. Mollie: Create Customer and Mollie: Create Mandate are both reversible writes, because recording an authorization the customer already gave contacts nobody and charges nothing. Mollie: Create Subscription is the one to gate, and it is flagged destructive: it schedules real charges against a mandate authorized earlier, so no second approval stands between the call and money leaving the customer's account. Set the start date explicitly rather than leaving it to a default, use Mollie: Update Subscription for changes, and remember that Mollie: Cancel Subscription is terminal, with no documented way to reactivate one.
Reconcile a payout against the payments inside it
The reporting family answers the question that spreadsheets usually absorb: which orders is this bank deposit made of. Mollie: List Settlements finds the payout by reference and date, Mollie: Get Settlement breaks its revenue and costs down per method, and Mollie: List Settlement Payments returns the payments it contains in the same shape as the ordinary payments lister, ready to match against orders in a Mattering database. Mollie: List Balances and Mollie: Get Balance cover the position right now, available and pending, and Mollie: Get Balance Report summarizes a window with opening and closing amounts and totals per category. This family needs an advanced access token, Mollie's organization level credential; a profile API key will not authenticate it.
Chargeback watch that opens work instead of an email
Mollie: List All Chargebacks sweeps the whole account newest first with the reason code and the amount deducted from the settlement, and Mollie: List Payment Chargebacks narrows to one payment when a workflow already has it in hand. Mollie: Get Payment Chargeback adds the reason description and whether the chargeback was later reversed. A scheduled run can write new ones into a Mattering database, open a task with the payment and customer attached, and notify the person who owns disputes, so the evidence deadline lands in the same system as everything else rather than in an inbox.
A pre flight check before an account takes money
Mollie: Get Onboarding Status is the honest check for whether a newly connected account can actually receive payments and settlements yet, rather than assuming it can and finding out at checkout. Mollie: Get Current Organization confirms which organization an access token belongs to, Mollie: List Profiles shows the website profiles under it with their review status, and Mollie: List Payment Methods returns what is enabled on the profile today, while Mollie: List All Payment Methods shows the wider catalog you could request. Running the four as a scheduled health check catches a profile that fell out of review before customers do.
Example: A refund request becomes an approved, idempotent refund
Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.
Trigger: a support form or an inbound webhook fires with the payment ID and the amount the customer is asking back.
Mollie: Get Payment reads the payment: its status, the total, and how much has already been refunded or charged back.
A condition compares the request against the remaining refundable amount and your policy, and routes anything unusual to a person.
An approval task opens in Mattering Productivity with the payment details attached, so a human signs off before money moves.
Mollie: Create Payment Refund runs on approval with the idempotency key filled, so a retried run cannot issue the refund twice.
Mollie: Get Payment Refund confirms the resulting status, and the run writes the refund ID and amount into a Mattering database next to the original order.
Mollie MCP questions, answered
What Mollie operations are supported?
45 nodes on the Mollie API v2: 30 query nodes and 15 action nodes. Payments (create, list, get, update, cancel, plus customer scoped create and list), refunds (create, list, get, cancel), customers (create, list, get, update, delete), mandates (create, list, get, revoke), subscriptions (create, list, get, update, cancel), payment links (create, list, get), chargebacks (account wide list, per payment list, get), payment methods (enabled, full catalog, single method), and the organization level reads: settlements, settlement payments, balances, balance report, invoices, current organization, profiles, and onboarding status. Deliberately not included: the Orders API, which Mollie's own documentation no longer recommends, the platform operator and marketplace surfaces, payouts, captures and release authorization, point of sale terminals, sessions, sales invoices, and profile writes.
Does this work with Claude, ChatGPT, or other AI assistants?
Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively.
Does Mollie have its own MCP server, and how is this different?
It does. Mollie ships an official MCP server at https://mcp.mollie.com/mcp, authenticated with an advanced access token that has to carry the profile.read scope, and its documentation names Claude Desktop and Cursor as clients. It covers Balances, Captures, Customers, Invoices, Mandates, Methods, Payments, Payment Links, Settlements, Subscriptions, Terminals, Webhooks, and Webhook Events, so it reaches captures, terminals, and webhook management that this catalog leaves out. Two things are genuinely different here. Mollie's server wants an organization level advanced access token for everything it does, including a plain payment read, while 34 of these 45 nodes run on an ordinary profile API key. And these nodes carry destructive flags, an optional idempotency key, and a canvas around them, so a refund can sit behind an approval task in Mattering Productivity and a settlement sweep can run on a schedule with no agent involved at all.
Which nodes need an organization level credential?
Eleven of the 45. Mollie gates the settlement, balance, invoice, organization, profile, and onboarding APIs on an advanced access token, the organization level credential an Admin creates in the Mollie Web App, and a profile API key starting with test_ or live_ will not authenticate them. The affected nodes are Mollie: List Settlements, Mollie: Get Settlement, Mollie: List Settlement Payments, Mollie: List Balances, Mollie: Get Balance, Mollie: Get Balance Report, Mollie: List Invoices, Mollie: Get Invoice, Mollie: Get Current Organization, Mollie: List Profiles, and Mollie: Get Onboarding Status. Each says so in its own description on the canvas, so you find out where you are standing rather than after a 401. The other 34 nodes work with an ordinary profile API key.
Can an AI agent move real money with this?
It can, which is exactly why the connector labels the nodes that do. Seven are flagged destructive: Mollie: Create Payment Refund moves money back to the shopper with no un refund, Mollie: Cancel Payment Refund and Mollie: Cancel Payment and Mollie: Cancel Subscription are terminal, Mollie: Delete Customer and Mollie: Revoke Mandate cascade into cancelling that customer's mandates and subscriptions, and Mollie: Create Subscription schedules charges against an existing mandate. Creating a payment, a customer payment, or a payment link charges nobody at call time, so those are the natural surface to hand an agent, along with all 30 read nodes. The recommended pattern is read freely, write behind a condition or an approval task, and fill the idempotency key on anything that must not happen twice.
Does creating a subscription charge the customer straight away?
It can, and this is the sharpest edge in the connector. A Mollie subscription bills against a mandate the customer authorized earlier, so unlike a hosted checkout there is no second approval between the call and a real charge, and Mollie documents no refund of payments already collected when a subscription is cancelled, so treat those as a separate refund decision. Mollie's reference pages do not state what the first charge date is when the start date is omitted, so the node is classed destructive on the conservative reading and its description tells you to set a start date explicitly. Do that, set the number of times if the subscription should end by itself, and keep the node behind an approval step rather than a bare trigger.
How do test mode and live mode work?
There is one host and no environment field. Mollie issues a test key alongside the live key in the Mollie Web App, and for a profile API key the prefix decides which data you reach: test_ reaches test data, live_ reaches live data, at the same base URL. Organization level advanced access tokens are the documented exception to that rule, since their mode comes from a testmode request parameter or the scope chosen when the token was created rather than from the value. Either way a mode selector on the credential could only ever disagree with the credential sitting next to it, so the connector does not offer one. Most of the catalog can be exercised in test mode first: the payment, refund, customer, mandate, subscription, link, and chargeback nodes all work there, including the destructive ones, which is the safe way to rehearse a refund or a subscription workflow before pointing it at real customers. The exception is one Mollie states itself, that its API endpoints related to business operations do not support test mode, so the settlement, balance, and invoice nodes read live data whichever credential you hold.
What are Mollie's API rate limits?
Mollie publishes no fixed number, so this page will not invent one. What Mollie does document is the mechanism: limits are calculated per endpoint and per method from observed traffic, a GET and a POST on the same resource sit in separate buckets, and test mode limits are lower than live. The current state arrives on every response in the RateLimit-Policy and RateLimit headers, and a drained bucket returns HTTP 429 with a Retry-After header. The nodes report the error on their output rather than retrying silently, so a workflow can wait and continue.
Can it receive payment status updates from Mollie?
Not as connector nodes. This catalog is the outbound API surface, and Mollie's webhook subscription management is deliberately not part of it. What you can do is let Mollie call Mattering. Mollie: Create Payment and Mollie: Update Payment both take a webhook URL, so point it at an inbound webhook trigger on a Mattering automation and a status change runs that workflow, which can then call Mollie: Get Payment to read the authoritative state. Note one documented quirk while building that loop: updating a payment does not itself trigger a webhook call.
Put Mollie to work inside your workspace
Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.
All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Mollie is a product of its respective owner; Mattering is an independent platform.