Refund gate for AI support agents · Stripe
Let your AI support agent refund, not overspend.
Your bot calls one endpoint. Small refunds that fit your policy go through on their own. Bigger ones get a one-tap Approve on the right person's phone. Every Stripe refund is logged with who approved it and why.
- ✓ Agent never holds refund rights
- ✓ Rules run on the real charge
- ✓ First answer wins, no double refunds
- ✓ Audit log finance can export
Live demo · no sign-up
Ask for a refund. Watch the policy decide.
You play the customer. Ava, an AI agent, calls the same Countersign engine your bot would, against a sandbox ledger. Over $50, the approve card lands on the phone: scan the QR code with yours and tap Approve.
Support chat · you are Sam, the customer
Sample data: a sandbox ledger, no real money
Approver's phone
Audit log · live
append-onlyEvery request, rule result, decision and refund shows up here.
Three steps, one snippet.
- 1
Connect Stripe with a restricted key
Paste a key with Charges: Read, Customers: Read and Refunds: Write. We check each permission and tell you exactly which one is missing.
- 2
Pick a policy
Auto-approve under $X, inside N days, first refund only, never on a disputed charge, a monthly budget. Or paste your refund policy and GPT drafts the rules.
- 3
Give your agent the snippet
One HTTP call or the MCP tool request_refund. It answers approved_and_refunded, pending or denied, with a message the agent can relay.
The request
POST /api/v1/refunds/request
Authorization: Bearer cs_…
{ "charge_id": "ch_3P…",
"amount": 8900,
"reason": "Seats never used",
"ticket_url": "https://…/123",
"agent_reasoning": "Bought 9 days ago,
zero logins on the new seats." }The answer
{ "status": "pending",
"message": "This refund of $89.00 needs a
person's approval. Tell the customer a
teammate is reviewing it…",
"rule_trace": [
{ "rule": "auto_cap", "outcome": "route",
"detail": "$89.00 is over the cap" } ],
"status_url": "…/api/v1/refunds/rr_…" }A prompt is a request. This is a control.
Stripe's refund call has no approval step: any key with refund rights can refund any amount. Generic approval SDKs make you write the rules, wire the approver and call Stripe yourself. Countersign does one action, completely.
Holds the key, not your agent
The refund runs on our restricted key after approval, with an idempotency key. The agent cannot get around the gate.
Checks the real charge
Refundable balance, age, disputes and the customer's refund history come from Stripe, not from what the agent says.
An approve card built for refunds
Customer, charge, prior refunds, the agent's reasoning and the ticket, approvable in one tap from email on a phone.
A log finance trusts
Append-only: every rule result, approver, IP and Stripe refund id. Filter, export CSV, share a read-only link.
Works with the agent you already run.
All integrations →Priced per refund request.
A request counts when your agent submits it, auto-approved or routed. Annual billing gets two months free.
Free
$0/mo
forever
Try it on test mode, then 20 live refunds a month.
- ✓1 Stripe account
- ✓Unlimited test-mode requests (fair use)
- ✓20 live refund requests / month
- ✓1 approver
- ✓30-day audit log
Starter
$29/mo
or $290/yr
For a small support team letting one bot refund.
- ✓300 refund requests / month
- ✓3 approvers
- ✓All policy rules
- ✓1-year audit log
- ✓CSV export
Team
Most teams$79/mo
or $790/yr
Support leads under $200, finance above. Nobody waits.
- ✓2,000 requests / month
- ✓Unlimited approvers
- ✓Amount-tier routing
- ✓Escalation to a backup approver
- ✓Webhooks
- ✓3 Stripe accounts
Scale
$199/mo
or $1990/yr
Many brands, many Stripe accounts, an audit trail forever.
- ✓10,000 requests / month
- ✓Unlimited Stripe accounts
- ✓Audit log kept forever
- ✓Everything in Team
Questions
Does my AI agent get access to Stripe?+
No. The agent only gets a Countersign API key that can ask for refunds. Countersign holds a restricted Stripe key (Charges: Read, Customers: Read, Refunds: Write), encrypted at rest, and only runs the refund after your rules or a person say yes. A prompt injection cannot raise the cap, because the cap is not in the prompt.
What if the agent lies about the amount or the customer?+
Countersign ignores what the agent claims about the charge. It reads the charge from Stripe: the amount still refundable, the age, whether it is disputed, and the customer's earlier refunds. The rules run on that.
Can a refund go out twice?+
No. The first answer wins (a database lock), the refund carries an idempotency key, and Countersign reads the refundable balance again right before refunding.
Which agents work with it?+
Anything that can make an HTTP call or speak MCP: Intercom Fin, Zendesk AI, Gorgias, Freshdesk, Help Scout, Front, Crisp, n8n, Make, Zapier, LangGraph, OpenAI Agents SDK, Claude, Cursor, Vercel AI SDK, Mastra, CrewAI.
Can I try it without real money?+
Yes. The demo above uses a sandbox ledger. After sign-up, Stripe test-mode keys work fully and test requests do not count against the Free plan.
What counts as a request?+
Every refund request your agent submits, whether it was auto-approved, routed to a person or denied.
Give your bot a refund button with a countersignature.
Free with Stripe test mode. Live in an afternoon.