Failed payments
Priya Sharma, finance lead at Acme Ltd, asked why payments failed this week. Memtro listed each failed payment with amount, method and the error Razorpay gave, and grouped them by reason.
Which payments failed this week, and why?
Razorpay connects Memtro to the payments on your own merchant account. It reads payments, orders, refunds, settlements, disputes, payment links and subscriptions over a date window, with amounts, status and failure reasons, and customers by name and email. When asked, and once an administrator has granted the action by name, it can create an order, a customer or a payment link, send or cancel a payment link, capture an authorised payment, which charges the customer, and refund a payment, which moves money. Card, bank and VPA details are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Razorpay tool, reads what it needs, and answers with the source cited.
These tools change something in Razorpay. 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, then add the address it shows as a webhook in Razorpay, choosing the same kinds; the tab shows Razorpay's own steps. Each event can start a job, with the event as its input, and can be remembered where you choose. Razorpay signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Razorpay 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, and why?
How much was settled to our bank account last month?
Which disputes need a response before Friday?
Which payment links are still unpaid?
Refund half of payment pay_29QQoUBi66xm2f
Priya Sharma, finance lead at Acme Ltd, asked why payments failed this week. Memtro listed each failed payment with amount, method and the error Razorpay gave, and grouped them by reason.
Tom Reilly, account manager at Northwind, asked Memtro to create a payment link for BigCo's workshop fee and send it to their finance contact. Memtro created the link, then had Razorpay email it to the customer on it. The email reached BigCo and cannot be recalled.
The teams that lean on Razorpay most, a question each of them asks, and what they connect beside it.
A record in Razorpay 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 Razorpay Dashboard, open Account & Settings → API Keys and choose Test or Live mode first.
Generate a key and copy the Key Id. The Key Secret is shown once, on the pop-up, so download or copy it then. Regenerating the key stops this connection working.
In Memtro, open Connections → Razorpay and paste the Key Id and Key Secret.
Ask your first question: which payments failed this week, and why?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Razorpay tools are the same everywhere.
Only when you ask, and only what it has been granted: create an order; create a payment link (Razorpay does not notify the customer); send or resend a payment link to its customer by email or SMS; cancel a payment link; capture an authorised payment (charges the customer); refund a payment, fully or partly (moves money); create a 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.
Key Id and Key Secret. In the Razorpay Dashboard, open Account & Settings → API Keys and choose Test or Live mode first.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Razorpay, choosing the same kinds; the tab shows Razorpay's own steps. 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