Mollie
PaymentsConnect AI agents to Mollie to run the full payment lifecycle: create hosted checkout payments and payment links, issue refunds, track chargebacks, and manage customers, mandates, and subscriptions for recurring billing. Agents also reconcile payouts through balances, settlements, and Mollie fee invoices.
What This Integration Enables
Payments are the one workflow where a wrong automated action is not a data problem but money in motion. This integration takes that seriously across Mollie's full lifecycle: agents create payments with hosted checkout URLs, generate shareable payment links for invoices and donations, capture authorized amounts, and run recurring billing end to end with customers, mandates, and subscriptions. On the recovery side they issue full or partial refunds, track chargebacks as they land, and reconcile the money that actually arrives: balances, settlements, and Mollie's own fee invoices, matched payment by payment. The connector's dividing line is simple. Reading, listing, drafting, and reconciling run autonomously. Anything that moves money or cancels the right to collect it, refunds above threshold, mandate revocations, subscription cancellations, goes through a [human-in-the-loop](/concepts/human-in-the-loop/) gate with the case fully assembled. Agents do the lookups and build the audit trail; a person owns the decision. Connector capabilities are built and verified against Mollie's official API.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Refunds that carry their own audit trail
A refund request arrives from support in [Zendesk](/integrations/zendesk). The agent calls Get Payment to confirm the payment is paid, checks the remaining refundable amount, and looks for open chargebacks on the same payment. Below the threshold, the refund executes and the ticket updates. Above it, the case goes to the finance channel with the customer's payment history attached, and Create Refund runs only on approval. Every refund now answers the auditor's question before it is asked: who approved this, and on what basis.
Invoicing through payment links
An invoice is issued upstream in [Xero](/integrations/xero). The agent calls Create Payment Link with the amount and reference, then emails the customer their hosted payment link through [Gmail](/integrations/gmail-service). It watches List Payment Link Payments for completion; paid links reconcile against the invoice automatically, and unpaid links past the due date trigger a polite reminder with the same URL. When a link is superseded, the agent archives it with Update Payment Link rather than deleting it, keeping the reporting trail intact.
Settlements reconciled the day they land
When a payout appears in List Settlements, the agent pulls List Settlement Payments to break it into the individual payments, refunds, and chargebacks it contains, then posts the breakdown to the ledger and logs each line with [Google Sheets](/integrations/google-sheets). Get Balance Report and List Balance Transactions cover the money still in flight, and List Invoices matches Mollie's fees to the deductions. Month-end reconciliation becomes a review of exceptions the agent already flagged, not an archaeology project.
Human-in-Loop Highlight
Revoke Mandate cancels a customer's authorization to be charged, and Mollie is explicit about the consequences: pending subscription payments fail, subscriptions using the mandate are canceled, and the revocation cannot be undone. Getting consent back means getting the customer through checkout again. So when the chargeback watch finds a second dispute from the same customer, the agent does not revoke on its own. It assembles the case and asks the billing owner: "Customer cst_4Kd has filed 2 chargebacks in 90 days totaling EUR 118. They hold a valid mandate and an active monthly subscription. Revoke the mandate and end the subscription, or keep billing and dispute the chargeback?" One option protects revenue; the other stops the bleeding. That trade-off belongs to a person, and the agent's job is to make the decision take thirty seconds instead of an afternoon of lookups.
Agent Capabilities
56 actionsPayments
5- Create Payment Creates a payment and returns the hosted checkout URL. Leave the method empty to let the customer choose. The entry point of the payment lifecycle.
- List Payments Lists payments newest first with cursor pagination. Used in monitoring and reconciliation runs.
- Get Payment Retrieves a payment with status, paid, remaining, and refunded amounts, and optionally its refunds and chargebacks. The verification step before any money moves.
- Update Payment Updates a payment's description, redirect URL, webhook URL, or metadata while it is still open.
- Cancel Payment Cancels a payment that is still cancelable, such as an open bank transfer or an authorized card payment.
Refunds
5- Create Refund Refunds a paid payment fully or partially; omitting the amount refunds the full remaining refundable value. Runs behind the approval threshold in this connector.
- List Payment Refunds Lists all refunds on a specific payment. Used to prevent double refunds.
- Get Refund Retrieves a refund's amount, status, and settlement linkage.
- Cancel Refund Cancels a refund while it is still queued or pending. Once it reaches processing it cannot be stopped, which is why refunds are gated before creation, not after.
- List All Refunds Lists refunds across all payments. Used in reconciliation and refund-rate reporting.
Chargebacks
3- List Payment Chargebacks Lists the chargebacks on a specific payment. Used when investigating a disputed order.
- Get Chargeback Retrieves a chargeback's disputed amount, settlement impact, and the reason reported by the bank or card scheme.
- List All Chargebacks Lists chargebacks across all payments. The feed behind daily dispute monitoring.
Captures
3- Create Capture Captures an authorized card or Klarna payment, transferring reserved funds. Used in ship-then-capture flows.
- List Captures Lists the captures on a payment.
- Get Capture Retrieves a capture's amount, settlement amount, and status.
Payment Links
6- Create Payment Link Creates a shareable hosted payment link with a fixed or open amount. Used for invoices, donations, and ad hoc collection.
- List Payment Links Lists payment links newest first.
- Get Payment Link Retrieves a link's amount, expiry, archive state, and URL.
- Update Payment Link Updates a link's description or archives it so it can no longer be paid while remaining in reporting.
- Delete Payment Link Permanently deletes a payment link; it stops working immediately and cannot be restored. Archiving is preferred; deletion runs only in reviewed cleanup.
- List Payment Link Payments Lists the payments made through a specific link. Used to track who paid a reusable link.
Customers
7- Create Customer Creates a customer record, the prerequisite for single-click and recurring payments.
- List Customers Lists customers newest first.
- Get Customer Retrieves a customer's name, email, locale, and metadata.
- Update Customer Updates a customer's details; only provided fields change.
- Delete Customer Permanently deletes a customer, revoking all mandates and canceling pending subscriptions. Cannot be undone; routed through human approval.
- List Customer Payments Lists all payments linked to a customer. Used to build the customer history behind refund and dispute decisions.
- Create Customer Payment Creates a payment for an existing customer; with the recurring sequence type, a valid mandate is charged without customer interaction. Used for on-demand charges.
Mandates
4- Create Mandate Creates a mandate recording consent obtained outside Mollie's checkout, such as a signed SEPA authorization.
- List Mandates Lists a customer's mandates with their status. Used to confirm chargeability before recurring billing.
- Get Mandate Retrieves a mandate's method, status, and consumer details.
- Revoke Mandate Revokes a customer's charging authority; dependent subscriptions are canceled and the revocation cannot be undone. The gated action in this connector.
Subscriptions
7- Create Subscription Creates a recurring charge against a customer's valid mandate at a set interval. The start of automated recurring billing.
- List Customer Subscriptions Lists one customer's subscriptions.
- List All Subscriptions Lists subscriptions across all customers. Used in revenue and dunning runs.
- Get Subscription Retrieves a subscription's status, amount, interval, remaining charges, and next payment date.
- Update Subscription Updates a running subscription's amount, interval, charges, or mandate. Used for plan changes without re-onboarding.
- Cancel Subscription Cancels a subscription so no further charges are created. Confirmed by a person when triggered from an automated workflow.
- List Subscription Payments Lists the payments a subscription has produced. Used to check which recurring charges succeeded before dunning.
Payment Methods
3- List Enabled Payment Methods Lists the methods enabled on the profile in checkout order, filterable by amount. Used to validate what a customer can actually pay with.
- List All Payment Methods Lists every method Mollie offers regardless of profile settings. Used for discovery and configuration checks.
- Get Payment Method Retrieves a method's display details, limits, and issuers.
Balances
4- List Balances Lists the organization's balances with available and pending amounts per currency. Requires an organization access token.
- Get Balance Retrieves a single balance with amounts and payout settings; pass primary for the main balance.
- Get Balance Report Retrieves a summarized balance report over a period, grouped by status balances or transaction categories. Used in cash position reporting.
- List Balance Transactions Lists individual balance movements: payments, refunds, chargebacks, payouts, and fees. The line-item feed for reconciliation.
Settlements
3- List Settlements Lists payouts to the bank account, newest first. Requires an organization access token.
- Get Settlement Retrieves a settlement's status, total, and period breakdown; pass next or open to preview upcoming amounts.
- List Settlement Payments Lists the payments inside a specific settlement. The action that turns a lump-sum payout into ledger lines.
Invoices
2- List Invoices Lists the fee invoices Mollie issued to the organization. Used to reconcile fees against balance deductions.
- Get Invoice Retrieves a fee invoice's status, line items, and PDF link.
Profiles
2- List Profiles Lists the organization's website profiles, one per site or app accepting payments.
- Get Profile Retrieves a profile's details and review status; pass me for the current API key's profile.
Terminals
2- List Terminals Lists the physical point-of-sale terminals linked to the account.
- Get Terminal Retrieves a terminal's brand, model, serial number, and activation status.
Frequently Asked Questions
What can FlowRunner do with Mollie?
FlowRunner agents can run Create Payment, List Payments, and Get Payment in Mollie, plus 53 more actions.
Does connecting Mollie to FlowRunner require OAuth?
No. Mollie connects to FlowRunner with an API key, no OAuth flow required.
Can Mollie trigger a FlowRunner workflow automatically?
Mollie doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Mollie
$100 in credits. No card required. Connect in minutes.