Test refunds, cancellations, product swaps and discount codes against a simulated Recharge account that fails on purpose. In production, COLVO holds the API token, applies your limits and checks every result in Recharge.
refund.create payment_id = the charge, amount_minor, currency → a refund on the charge
subscription.cancel subscription_id, mode: immediate → cancels now: no further charges
subscription.change_plan subscription_id, price_id = product variant, at: now → swap from the next charge
coupon.apply subscription_id, coupon_id = discount code → on the subscription’s address
Not on Recharge: cancel at period end, pause / resume, undo a cancellationThe agent never holds your payment keys — it proposes, COLVO decides and executes.
Recharge takes no idempotency keys and refunds carry no note. If an answer is lost, COLVO never re-sends — it opens an incident and a person checks the charge.
Recharge cancels now: the next charge and box don’t happen. A proposal to cancel “at the end of the period” is refused before anything is sent.
Limits, approvals, allowed products and allowed discount codes work the same; only the ids are Recharge’s.
No — remove it. Only COLVO’s executor uses the token, encrypted per organisation.
read/write on Subscriptions, Payments and Discounts; read on Orders and Customers. COLVO warns about any other scope.
Recharge reports refunds as a total per charge, so COLVO checks the charge’s refunded total — exact for the usual one refund per charge.
Yes — connect the store itself as a separate Shopify connection for order refunds and cancellations.
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.