Every refund checked against the system of record.
An agent success rate measures what the agent thinks happened. This measures what actually happened. The scan reads your recent refunds from the system of record and finds the ones that never settled, the ones still pending, and the operations that were refunded twice.
It runs where your key already is. We will never ask you to paste a provider credential into a web page.
export STRIPE_API_KEY=rk_live_... # a restricted, read-only key
npx @postcept/relay audit --limit 25Sampled 25 recent refunds on 189651a28d30.
Refund integrity: 88.0% of sampled refunds verified settled
verified 22, incomplete 2, duplicated 1
incomplete re_b2 Refund status is 'pending', not settled in the system of record.
duplicated re_d4 Another refund on this charge shares the same operation reference (duplicate).01
It runs on your machine
The relay reads your recent refunds with the key that is already in your environment. The key stays in that process. Postcept never receives it and has no account to store it in.
02
Only the facts are sent
Refund id, charge, amount, currency, status. No credential, no customer emails. Postcept scores those facts: did each refund settle, and was one operation refunded twice?
03
You get a rate and a signed badge
Verified refunds over sampled refunds, every false or duplicate completion, and an Ed25519-signed badge that anyone can verify offline against the published key.
The relay is open source, so you can read exactly what it sends before you run it. A restricted Stripe key with read access to Refunds and Charges is all it needs, which means the audit cannot move money even in principle.
Want this on every action, continuously?
Postcept verifies refunds, cancellations, and tickets across Stripe, Zendesk, and more, and re-checks them over time.