01 — Overview
Stripe’s dashboard is built for the people who configure payments. The people who handle refunds, credits and disputes every day usually need something narrower, with your own rules on top. Describe that tool and the Bench builds it on your Stripe account: a refund desk, a dispute evidence tracker, a failed-payment recovery queue.
Connect with a restricted key that can reach only the resources your tools use. Put a Sign-off on any action above a limit, such as refunds over $500 or credits over $1,000, and the Logbook records both people, the amount and the reason. Stripe data can sit beside your own orders from Postgres or tickets from Zendesk, so nobody switches between three tabs to make one decision. Test-mode keys power staging, so a new refund rule is tried on test charges before it touches real money.
02 — What you can do
Restricted keys
Connect with a restricted key that reaches only the resources your tools need.
Limits on money moves
Refunds, credits and plan changes above a threshold wait for a second approver.
Reasons on record
Every action stores who took it, the amount and a reason code in the Logbook.
03 — FAQ
Before you connect Stripe
Which Stripe key should we use?
Can we require approval for refunds?
Does Chamfer store card data?
Does this work with Stripe Connect?
04 — Pairs well with
Teams often connect these next
05 — Used in
Give support, finance and ops a safe way to look up and change production records, without console access.
Route refunds, discounts, vendor changes and releases to a named approver, with the diff and the decision on record.
Add the screen your SaaS tools are missing, like a refund desk on Stripe or a renewals board on Salesforce.
Queues for refunds, escalations and account changes, with the customer's full context and your approval rules.