All Integrations
PaymentsAvailable
Stripe + Corebee
Let your AI read Stripe and run refunds with policy guardrails
Connect Corebee to Stripe through Stripe Connect (OAuth). Your AI assistant can read payments, subscriptions, invoices, and disputes during a conversation, and execute write actions like refunds and subscription changes under per-org risk policies you control. Every action is signed with merchant-of-record metadata and written to an immutable audit log.
How to Set Up
- 1
Click "Connect Stripe"
From Settings → Integrations → Stripe, click Connect. Corebee starts the official Stripe Connect OAuth flow — no API keys to copy, no secrets to paste.
- 2
Authorize Corebee on Stripe
You're redirected to connect.stripe.com to sign in to your Stripe account and approve the requested scopes. Stripe issues Corebee a connected-account ID (acct_…) scoped to your business; Corebee never sees or stores your secret key.
- 3
You're connected
On callback, Corebee creates a stripe_connections row keyed to your org and the AI is immediately able to read transactions and — within the policy thresholds you set — execute refunds and other write actions with risk-based approval.
What You Can Do
Resolve refund and chargeback questions in one message instead of three escalations
AI handles 'what's my next invoice' and 'why did my card fail' without paging a human
Send a payment-method update link the moment a card decline triggers a support ticket
Approve high-risk refunds in Slack with full context: amount, customer history, and policy threshold breached
Audit every AI- or agent-initiated Stripe action against an append-only log for SOC 2
Frequently Asked Questions
How does Corebee authenticate with my Stripe account?
Through Stripe Connect OAuth. You sign in to Stripe directly; Stripe returns Corebee a connected-account ID (acct_…). Corebee never asks for, stores, or transmits your Stripe secret key. You can revoke access at any time from your Stripe Dashboard or with one click in Corebee.
What controls do I have over write actions like refunds?
Each org has a Stripe policy: an auto-approval refund cap (default $50), a review-required cap (default $500), a daily refund cap (default $1000), and switches for immediate-cancel, dispute-evidence submission, and HITL email recipients. Anything above the auto cap routes to Slack or email for human approval before Corebee calls Stripe.
Is my Stripe data secure?
Yes. Connect OAuth means we never see your secret key. All API calls go over TLS, full card numbers never leave Stripe, and every state-changing action is written to an append-only stripe_audit_log table with the actor (AI or human), policy decision, and Stripe response. We retain audit rows for seven years.
Does it support Stripe Connect platforms with sub-merchants?
Yes — that's the canonical mode. Corebee uses Connect Standard, so each merchant grants Corebee access to their own Stripe account and we make all calls with the Stripe-Account header. Test mode and live mode are isolated; a test connection cannot drive live API calls.
Can I use restricted API keys instead of OAuth?
OAuth via Connect is the default and recommended path. Restricted-API-key (paste-key) mode is being soft-deprecated over a 16-week window. Existing paste-key connections continue to work; new orgs default to OAuth and we'll prompt existing orgs to upgrade ahead of the cutover.
Related Integrations
Ready to connect Stripe?
Set up the Stripe integration in minutes. $99/mo flat — 30-day money-back guarantee.
Start Free Trial