Who cancelled this week, and which renewals failed?
Recharge shows your subscriptions by status, with product, price, interval, next charge date and any cancellation date and reason. It reads customers with their subscription counts and whether they are in dunning, charges with the error on a failure, and orders. A sync keeps subscription changes in memory. When asked and granted, it can cancel or reactivate subscriptions, change their date, quantity, price or interval, skip or unskip charges, and update customers. Refunding a charge or processing one now moves the customer's money and cannot be undone. Processed charges older than 90 days are not returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Recharge tool, reads what it needs, and answers with the source cited.
These tools change something in Recharge. 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 Recharge 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.
Recharge + MemtroWho cancelled their subscription this week?
Which renewals failed this week?
What is due to charge tomorrow?
Which customers are in dunning?
Skip next month's charge for Maya Okafor's coffee subscription
Maya Okafor, ecommerce manager at Northwind, asked who cancelled their subscription this week. Memtro listed each cancelled subscription with product, cancellation date and reason. She saw most reasons pointed at delivery timing.
Tom Reilly, customer success lead at Northwind, asked Memtro to skip December's charge for a customer travelling abroad. Memtro skipped that charge for her subscription, so she is neither billed nor shipped this time, and January's charge goes ahead as usual.
The teams that lean on Recharge most, a question each of them asks, and what they connect beside it.
A record in Recharge 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
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 Recharge merchant portal, a store administrator opens API tokens and creates a token for Memtro.
Give it read_store, read_subscriptions, read_customers and read_orders, and add only the write scopes you want Memtro to use: write_subscriptions, write_orders (skip, unskip, refund), write_payments (process a charge) or write_customers. Copy the token.
In Memtro, open Connections → Recharge and paste it into API token.
Ask "Who cancelled their subscription this week?"
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Recharge tools are the same everywhere.
Only when you ask, and only what it has been granted: cancel a subscription (no cancellation email unless asked); reactivate a cancelled subscription (billing resumes); change a subscription's next charge date; change a subscription's quantity, price, interval or charge limit; skip an upcoming charge for given subscriptions; unskip a skipped charge for given subscriptions; refund a processed charge in full or in part (moves money back to the customer); process a queued or failed charge now (charges the customer; Recharge Plus); update a customer's name, email, phone or tax exemption. 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 Recharge records into memory as entities.
API token. In the Recharge merchant portal, a store administrator opens API tokens and creates a token for Memtro.
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