Monday’s failed payments and disputes, already written up
What failed since Friday and the reason Stripe gives, which disputes have clocks running, what the customer from Tuesday was actually charged. Refunds stage to the confirm screen and wait for you.
Every Monday costs half an hour of clicking: failed payments since Friday, the dispute with a deadline, the customer who emailed about a duplicate charge. Next Monday it resets.
A companion takes that half hour. It reads payments, disputes and customers freely and writes the summary. Anything that moves money stops in front of you with the amount and the exact charge on screen. Stripe publishes its own official MCP server for the bulk pulls.
| Job | The Stripe Dashboard | A Strawberry companion |
|---|---|---|
| Monday payments-and-disputes review | You click through it | Read and summarized for you; no approvals needed |
| Issuing a refund | You find, verify, click | Staged to the confirm screen; you approve the card |
| High-volume reconciliation | Exports and reports | Scheduled weekly read; bulk pulls through the official Stripe MCP server |
| API keys, payouts, bank details | You, alone | Untouched by design |
What can a companion read without asking?
Almost everything the Monday check needs.
It opens the Payments list filtered to failed since Friday, each customer page for the history, and the Disputes tab for evidence deadlines, then writes one summary: what failed and why, which disputes have clocks running, what the customer from Tuesday was charged.
That summary feeds the follow-up: dunning emails, the invoice chasing loop, the note to your bookkeeper. Drafting is companion work and sending is gated.
What a refund looks like before you click
The companion opens the payment, checks it against the customer’s claim on amount, date and card, and fills the refund form: amount entered, reason selected. Then it stops. You see exactly what is about to happen to exactly which charge before the confirming click.
The same gate covers cancelling subscriptions and anything else with a customer or a balance on the other end. Ask Always in Settings → AI permissions tightens it further.
What should stay manual?
API keys, webhook endpoints, payout schedules, bank details and account settings.
None is a recurring chore and all are catastrophic to get wrong. Mass refunds sit in the same bucket, because approving them as one batch is not a review.
Reconciliation is where a companion earns its keep: Stripe numbers against your books in Xero, payouts against your Mercury balance, every week, all reads, instead of whenever somebody remembers.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents