Test refunds, cancellations and plan changes against a simulated Chargebee that fails on purpose. In production, COLVO holds the API key, applies your limits and checks every result on your Chargebee site.
refund.create invoice_id (or payment_id = the invoice), amount_minor, currency → a refundable credit note
subscription.cancel subscription_id, mode: period_end | immediate → end_of_term | immediately (nothing credited)
subscription.pause subscription_id, resumes_at? → pause at the end of the term
subscription.resume subscription_id
subscription.cancel_undo subscription_id → removes the scheduled cancellation
subscription.change_plan subscription_id, price_id (item price), at: now | period_end
coupon.apply subscription_id, coupon_idThe agent never holds your payment keys — it proposes, COLVO decides and executes.
On Chargebee money goes back against an invoice, through the gateway that collected it. Mandates list the invoices that may be refunded; an agent that names another customer’s invoice is denied before anything is sent.
Every write carries Chargebee’s idempotency key. Chargebee keeps keys for 30 minutes, so COLVO never re-sends after that — a person checks instead.
Limits, approvals, pause and plan-change rules work the same; only the ids are Chargebee’s.
No — remove it. Only COLVO’s executor uses the key, encrypted per organisation.
Full-access, “Write key” subtype: it can create and update but not delete. A read-only key is refused.
Both. Start with your test site (yoursite-test); a live site is a separate connection.
COLVO uses the Product Catalog 2.0 API (item prices). Sites still on 1.0 are not supported yet.
Reference: Mandates & connections · Webhooks
Test your agent before it ships — and guard every real action once it’s live. In a safe copy of your world first.