Failed payments
On Friday the finance lead asks which Mollie payments failed this week. Memtro lists them with amount, method, description and customer, beside the ones that expired, so the team can contact each customer before the weekend.
Which Mollie payments failed, what a customer has paid and when subscriptions next charge.
Connect Mollie with a website profile's API key and Memtro reads that profile's payments with amount, status, method and amount refunded, customers, subscriptions with next payment date, and the refunds on one payment. It reads on demand and there is no hourly sync. When you ask, and once an administrator has granted the action by name, it can create, change or delete a customer, create a payment link, cancel an open payment or a subscription, and refund a payment or cancel a pending refund. Refunds move money back to the customer and become permanent after about two hours.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Mollie tool, reads what it needs, and answers with the source cited.
These tools change something in Mollie. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Mollie, choosing the same kinds; the tab shows Mollie's own steps. Each event can start a job, with the event as its input. Mollie signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Mollie is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Which payments failed this week?
Did the payment from Acme come through?
Which subscriptions are active, and when does Brightwave Ltd next pay?
Refund 20 euros of Northwind's last payment
Cancel Globex's monthly subscription
On Friday the finance lead asks which Mollie payments failed this week. Memtro lists them with amount, method, description and customer, beside the ones that expired, so the team can contact each customer before the weekend.
Sara Lindqvist asks Memtro to refund 20 euros of Northwind's last payment for a damaged item. Memtro finds the payment, refunds that amount with the description she gave, and Mollie sends it back to the customer's card. She has about two hours to cancel it before it is final.
The teams that lean on Mollie most, a question each of them asks, and what they connect beside it.
A record in Mollie is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
You need a Mollie website profile: an API key belongs to one, so connect once per profile
In the Mollie Dashboard open Developers → API keys and copy the Live API key for real payments, or the Test API key for test data. Organisation access tokens are not accepted
In Memtro open Connections → Mollie, paste the API key and connect. An administrator then grants refunds, cancellations and customer changes by name
Ask which payments failed this week
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Mollie tools are the same everywhere.
Only when you ask, and only what it has been granted: create a customer record in Mollie; refund a payment, fully or partly, to the customer; cancel a refund that is still queued or pending; create a payment link to share with a payer; cancel a payment that is still open; cancel a customer's subscription so no further charges are taken; change a customer's name, email or locale; delete a customer, cancelling its mandates and subscriptions. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
API key. You need a Mollie website profile: an API key belongs to one, so connect once per profile.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Mollie, choosing the same kinds; the tab shows Mollie's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time