Guide · Stripe

Move a Stripe agent from test to production

Restricted key, mandates from your backend, a week of observation, approvals, then auto-allow for the small stuff.

Updated Sep 30, 2026
This guide⏱ 15 min
Level
intermediate
You need
a Stripe account, an agent that passes its suite
Works with
Stripe

1 · The path in one look

  1. The agent passes its suite in COLVO Test.
  2. Connect Stripe with a restricted key.
  3. Your backend issues a mandate per conversation.
  4. Observe for a week — nothing changes for customers.
  5. Enforce with every refund going to a person.
  6. Raise auto-allow for what reviewers always approve.

2 · Connect Stripe with a restricted key

From the project page → Connections, paste a restricted key and the webhook signing secret. COLVO checks each permission read-only before saving and refuses unrestricted live keys. Only COLVO’s executor ever uses the key.

3 · Observe first

For a week the agent keeps acting as today and reports what it did to POST /v1/observations. COLVO records what it would have decided and checks Stripe. The Observations page shows would-be decisions and replies that disagree with Stripe.

4 · Enforce: one call replaces the Stripe call

Remove the Stripe key from the agent. Where it called Stripe, it proposes to COLVO. Start with auto_allow_up_to_minor: 0: every refund is REVIEW and a person approves it on the Approvals page.

5 · Raise auto-allow

After a week or two, look at what reviewers approve every time — usually small refunds on the customer’s own recent payment — and set auto_allow_up_to_minor to that level. Everything above still goes to a person.

Full code for Node, Python and n8n: Move your agent to Guard.

≠

Stop trusting the reply.

Test your agent before it ships — and guard every real action once it’s live. In a safe copy of your world first.

Move a Stripe agent from test to production · COLVO