Disputes due Friday
Sarah Chen, operations manager at BigCo, asked which disputes needed a reply by Friday. Memtro returned the open chargebacks with case numbers, amounts and reply-by dates, so she could gather evidence before the deadline.
Which payments failed, and which disputes need a reply?
Braintree shows the transactions taken in a date window, with status, amount, order id, customer, card type and last four. It reads refunds, and disputes such as chargebacks with their amounts, case numbers and reply-by dates. It finds vault customers by name, company or email. When asked and granted, it can refund, void or capture a transaction, which moves real money and cannot be undone, gather evidence and submit or accept a dispute, and create, change or permanently delete vault customers. A window covers at most a year, and customers come back without phone numbers or payment details.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Braintree tool, reads what it needs, and answers with the source cited.
These tools change something in Braintree. 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 Braintree 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?
What did we take yesterday?
Which disputes need a reply by Friday?
What did we refund last month?
Refund £25 of order 1042 to the customer
Sarah Chen, operations manager at BigCo, asked which disputes needed a reply by Friday. Memtro returned the open chargebacks with case numbers, amounts and reply-by dates, so she could gather evidence before the deadline.
Dan Fletcher, finance lead at Acme Ltd, asked Memtro to refund £25 of a settled Northwind order after one item arrived damaged. Memtro refunded that amount to the customer's card, and Braintree may email the customer a receipt under the merchant's settings.
The teams that lean on Braintree most, a question each of them asks, and what they connect beside it.
A record in Braintree 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.
In the Braintree Control Panel, open Settings → API → API Keys and choose Generate New API Key.
Copy the Public Key, then View the Private Key and copy it. Keep the private key secret.
In Memtro, open Connections → Braintree, paste them into Public key and Private key, and set Environment to sandbox only for a sandbox account.
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 Braintree tools are the same everywhere.
Only when you ask, and only what it has been granted: refund a settled transaction in full or in part (moves money back to the customer); void an authorised or unsettled transaction (releases the hold); capture an authorised transaction (charges the customer); accept a dispute (the disputed amount is lost); add text evidence to an open dispute; remove a piece of evidence from a dispute before it is submitted; submit (finalise) a dispute with its evidence; create a vault customer; update a vault customer's name, email, company, phone or website; delete a vault customer and their stored payment methods (permanent). 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.
Public key, private key and environment. In the Braintree Control Panel, open Settings → API → API Keys and choose Generate New API Key.
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