Saturday's card takings
Priya Sharma, operations manager at Acme Ltd's café, asked what the till took on Saturday. Memtro listed Saturday's card transactions with totals per currency and picked out two refunds by time and amount.
What did we take on the card reader, and what reached the bank?
SumUp connects Memtro to your card takings. It reads transactions with time, type, status, amount, payment type and card brand, payouts to your bank with fees deducted, and your merchant profile. Card numbers, staff emails and bank details are never returned. When asked, and once an administrator has granted the action by name, it refunds transactions, creates and deactivates online checkouts, sends an amount to a card reader, saves customers, renames or removes readers and invites or removes team members. A refund moves money back to the cardholder and is permanent. An invitation emails the person.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right SumUp tool, reads what it needs, and answers with the source cited.
These tools change something in SumUp. 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.
Once SumUp 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.
What did we take on Saturday?
Any refunds this week?
How much did SumUp take in fees on last month's payouts?
Were there any chargebacks this month?
Refund £4.50 of this morning's 9:14 transaction, the oat milk was missing.
Priya Sharma, operations manager at Acme Ltd's café, asked what the till took on Saturday. Memtro listed Saturday's card transactions with totals per currency and picked out two refunds by time and amount.
Tom Reilly, café manager at Northwind, asked Memtro to refund £3 of a customer's order after a missing item. Memtro found the transaction by time and amount and refunded £3 to the customer's card. SumUp moved the money from the merchant balance, and the refund cannot be reversed.
The teams that lean on SumUp most, a question each of them asks, and what they connect beside it.
A record in SumUp 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.
Sign in at me.sumup.com and open Settings → For Developers → Toolkit → API Keys.
Create a key named Memtro and copy the secret key at once, as SumUp does not show it again. The Public Key cannot read anything.
In Memtro, open Connections → SumUp, paste the Secret API key and enter your Merchant code, the short code on your SumUp profile.
Ask your first question: what did we take on Saturday?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The SumUp tools are the same everywhere.
Only when you ask, and only what it has been granted: refund a card transaction, in full or in part (moves money back to the cardholder, permanent); create an online checkout for an amount, optionally with a SumUp payment page link; deactivate an unpaid checkout so it can no longer be paid (permanent); send an amount to a card reader for the customer to pay (takes a payment if they do); stop the payment showing on a card reader; save a customer record; edit a saved customer's details; rename a card reader; remove a card reader from the account (permanent until it is paired again); invite a person to the SumUp account with named roles (emails them); remove a team member from the SumUp account. 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. An hourly sync anchors recently changed SumUp records into memory as entities.
Secret API key and merchant code. Sign in at me.sumup.com and open Settings → For Developers → Toolkit → API Keys.
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