What came in through Paystack this week, and which payments failed?
Paystack connects Memtro to one business's payments. It reads transactions in a date window with status, amount, fees, channel, card type and last four and the customer, totals by currency, customers, refunds, disputes, payment requests and the available balance. When asked, and once an administrator has granted the action by name, it can add or rename a customer, create a payment link, raise or finalise a payment request, which may email the customer, send a reminder, archive a request and refund a transaction, which moves real money back. Amounts come in the lowest currency unit, such as kobo.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Paystack tool, reads what it needs, and answers with the source cited.
These tools change something in Paystack. 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 Paystack 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.
Paystack + MemtroHow much did we take through Paystack this week?
Which transactions failed yesterday?
Which disputes are awaiting our feedback?
Which payment requests are still unpaid?
Refund half of transaction 4099260516 to the customer
Sarah Chen, finance manager at Acme Ltd, asked which Paystack disputes needed a response. Memtro listed two awaiting merchant feedback, each with the transaction, the customer, the category and the due date, soonest first.
Dan Fletcher, customer success lead at Northwind, asked Memtro to refund half of a customer's order after a late delivery. Memtro refunded that amount on the transaction in Paystack, which moved the money back to the customer and cannot be undone.
The teams that lean on Paystack most, a question each of them asks, and what they connect beside it.
A record in Paystack 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)
Checkout.com
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 SenseIn the Paystack Dashboard, open Settings → API Keys & Webhooks.
Copy the Secret Key: sk_live_ for live or sk_test_ for test mode. Paystack has no read-only key, so connect it only where an administrator has agreed to full access.
In Memtro, open Connections → Paystack and paste it into Secret key. Test and live each need their own connection.
Ask your first question: how much did we take through Paystack this week?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Paystack tools are the same everywhere.
Only when you ask, and only what it has been granted: add a customer; change a customer's name; create a payment link for an amount (nothing is sent; the link is returned); raise a payment request (invoice), as a draft or emailed to the customer; finalise a draft payment request (the customer may be emailed); email a customer a reminder about a payment request; archive a payment request (it stops being listed or payable); refund a transaction, in full or in part (moves money back to the customer). 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 key. In the Paystack Dashboard, open Settings → API Keys & Webhooks.
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