COLVO

Let your AI agent act on billing, with a guard in between

COLVO Guard sits between your agent and Stripe, Paddle or Chargebee. Every action is checked against your rules: allowed, sent for approval, or blocked. Then verified after it happens.

  • Rules, not hopeSet limits per action, amount and customer; anything above goes to a human.
  • Approve from Slack or emailThe alert opens the exact refund in COLVO; you confirm it there, signed in.
  • Verified afterCOLVO checks the provider to confirm what really happened.

Stay in the loop

Product news and tips about testing AI agents. Takes 10 seconds.

We’ll ask you to confirm your email first · never shared
Tests & guards AI agents onStripePaddleChargebee· the agent never holds your payment keys· EU-hosted · GDPR
How it works

Three steps, and the agent never touches the payment key

1

Connect the agent

Instead of calling the provider, the agent proposes each action to COLVO with one HTTP call. The payment key stays with COLVO’s executor, encrypted.

2

Set the mandate

Your backend says which customer, which actions and how much. Above your auto-allow line a person decides; anything outside the mandate is denied.

3

Guard decides, then checks

ALLOW, REVIEW, HOLD or DENY, from rules, not AI. Allowed actions run exactly once, then COLVO reads the provider back to confirm what happened.

See it in action

One refund, through the gate

The agent asks for a €240 refund. Your mandate auto-allows up to €100. Here is what happens next.

  • REVIEW: the refund waits, nothing has been sent to Stripe
  • The Slack or email alert opens the exact refund in COLVO, where you confirm it signed in
  • Sent once with an idempotency key, then read back from Stripe to verify it
What it catches

The mistakes that cost real money

Each one is a deterministic check against your mandate and the provider’s state. No AI decides the outcome.

×101
A timeout, a retry, and the same refund sent twice→ same request → one refund
REVIEW02
A €240 refund when your auto-allow line is €100→ waits for a person, confirmed in COLVO
DENY03
A refund on another customer’s payment→ blocked before it reaches the provider
DENY04
A plan or coupon your mandate doesn’t list→ outside the mandate, never sent
HOLD05
Something looks wrong and you hit pause→ the kill-switch holds every new action
VERIFY06
The provider doesn’t show what was sent→ a mismatch opens an incident
Without / with

The same agent, with and without a gate

Without COLVO

  • The agent holds your payment key: one bad prompt can refund anything.
  • A timeout and a retry can send the same refund twice.
  • “Done” means the agent said so.

With COLVO

  • The agent proposes; only COLVO’s executor holds the key.
  • One request, one operation: a retry never doubles a refund.
  • “Done” means the provider confirms it.
FAQ

Before you sign up

Short answers. If something doesn’t fit your setup, we’ll say so.

Does the agent need our Stripe key?

No. The agent only proposes actions. COLVO’s executor holds the key, encrypted at rest and never logged, and writes only when the mandate allows it or a person approves it.

How do approvals work?

An action above your limits waits as REVIEW. COLVO sends it to Slack or email with Approve… and Reject… buttons. They open that exact action in COLVO, where you confirm it signed in. Nothing is decided by the link alone.

Which providers does it work with?

Stripe, Paddle, Chargebee, Shopify and Recharge. Refunds on all five; cancellations, plan changes and coupons where the provider has them. Details per provider: integrations.

Can we try it without blocking anything?

Yes. In observation mode the agent keeps acting as today and reports each action. COLVO records what it would have allowed, sent for review or denied, and checks the result read-only.

Where is our data hosted, and what does it cost?

In the EU, in Frankfurt (Germany), with each organisation isolated in the database. Guard is part of the Guard plan; on a Free workspace we can switch it on for a pilot. Plans and prices: pricing.

Put a gate in front of the agent.

Product news and tips on running AI agents safely on billing. One email to confirm, unsubscribe in one click.

Keep me posted ↑
Stripe · Paddle · Chargebee· the agent never holds your payment keys· EU-hosted · GDPR