Ask why a customer's payment was declined, and which Checkout.com disputes need evidence soon.
Connect Checkout.com with a secret API key and your account prefix, and Memtro reads payments and their history, disputes with evidence deadlines, reports and payment links. Card numbers, contact details and risk data are left out. It reads on demand, with no hourly sync. When you ask, and once an administrator has granted the action by name, it can create payment links and customer records, capture, refund or void an existing payment, which moves money and cannot be undone, accept a dispute, losing the amount, or attach evidence for someone to submit. New payments, payouts and transfers are refused.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Checkout.com tool, reads what it needs, and answers with the source cited.
These tools change something in Checkout.com. 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, choose the kinds you want, and Memtro registers its address with Checkout.com for you. Each event can start a job, with the event as its input, and can be remembered where you choose. Checkout.com signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Checkout.com 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.
Checkout.com + MemtroWhy was the Brightwave Ltd payment declined yesterday?
Which disputes are waiting for evidence, and when is each one due?
Has the refund on reference INV-7 gone through?
Create a payment link for £250 with reference ACME-1042
Refund £40 of the Northwind payment with reference NW-2291
On Monday the finance lead asks which chargebacks need answering. Memtro lists the disputes waiting for evidence with reason code, amount, the payment each is on and the evidence deadline, so the two due this week, both Northwind orders, are handled first.
A Northwind order arrived with one item missing and Sophie Turnbull in support asks Memtro to refund £40 of it. Memtro finds the captured payment by reference and refunds £40 to the cardholder, then checks the payment's actions until the refund shows as processed.
The teams that lean on Checkout.com most, a question each of them asks, and what they connect beside it.
A record in Checkout.com 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.
NetSuite
Ramp
FreeAgent
Holded
Mollie
QuickFile
Recurly
Airwallex
Maxio
Pennylane
Charity Commission (England and Wales)
FCA Register
Soldo
Spendesk
Lago
Recharge
Katana
Chaser
Unleashed
Printful
Orb
Quaderno
Donorbox
Avalara AvaTax
Billy
Cin7 Core
Codat
ComplyAdvantage
inFlow Inventory
Metronome
MRPeasy
Persona
Precoro
Printify
Rydoo
Saleor
Snipcart
Swell
Veeqo
Zuora
VAT Sense
PaystackIn the Checkout.com Dashboard open Developers → Keys and create a new key set for Memtro. Creating keys needs the Admin or Developer role
Select payments (view), payment search, disputes (view) and reports (view), and only if you want those actions payment captures, refunds and voids, dispute accept and evidence, Payment Links and Customers. Leave new payments, payouts and transfers off, then copy the secret key
In Settings → Account structure note your client id (cli_…). In Memtro open Connections → Checkout.com, paste the Secret API key and the Account prefix, the 8 characters after cli_, and connect
Ask which disputes need evidence this week
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Checkout.com tools are the same everywhere.
Only when you ask, and only what it has been granted: create a payment link for an amount, currency and reference (nobody is charged until someone pays it); create a customer record with an email and name; capture an authorised Checkout.com payment, in full or in part (takes the customer's money); refund a captured Checkout.com payment, in full or in part (money goes back to the customer); void an authorised Checkout.com payment before capture (releases the hold on the customer's funds); accept a Checkout.com dispute without contesting it (the chargeback stands); attach written evidence to a Checkout.com dispute (not submitted); update a Checkout.com customer's email or name. 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.
Secret API key and account prefix. In the Checkout.com Dashboard open Developers → Keys and create a new key set for Memtro. Creating keys needs the Admin or Developer role.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Checkout.com for you. 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