Stripe

Pushes every payment, refund, and subscription event into your books as it happens, drafts the customer reply when one is needed, and reconciles payouts against the bank for you.

Try Stripe in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Stripe integration

    • Describe the outcome and Ceven picks the right Stripe calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Stripe data, across all 415 of its actions.
  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Stripe access.
    • Per user and per environment credentials instead of shared keys.
  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Stripe, when, and on whose behalf.
    • The agent pauses and asks when Stripe is unclear instead of plowing ahead.
  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Stripe.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Stripe action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Stripe, and when to use it.

Create charge
Use this when a workflow needs to bill a customer outside the normal subscription flow, one-off purchases, fixed-fee add-ons, or settlements after a manual quote.
Refund charge
Issue a full or partial refund against a prior charge. Common path: dispute resolution, goodwill credits, or canceled-order automations.
Get customer
Pull the full customer record by ID or email, payment methods on file, subscription state, and the last 100 charges in one call. Use before refund or escalation flows.
Create customer
Provision a new Stripe customer when a deal closes in your CRM, with metadata pre-populated from the opportunity so the first invoice matches the contract terms.
List subscriptions
Pull every active, trialing, or past-due subscription, optionally filtered by price ID or customer cohort. Drives renewal-risk reports and dunning-batch builds.
Update subscription
Change plan, quantity, or trial end on an active subscription. Use for plan upgrades after a renewal call or pause flows during account holds.
Cancel subscription
End a subscription immediately or at period end, optionally prorating the unused balance back to the customer. Required leg of an offboarding workflow.
Create invoice
Draft an invoice with line items pulled from a quote or contract. Use for usage-based billing or one-time pro services charges.
Get invoice
Fetch a specific invoice's line items, taxes, and PDF URL, used when surfacing a copy into a help-desk reply or attaching to a renewal email.
List disputes
Pull every open dispute with reason code, evidence due date, and dispute amount. Drives the dispute-evidence prep workflow.
Submit dispute evidence
Upload customer communications, shipping records, and product descriptions to Stripe's dispute response. Auto-populates from the transaction's metadata where possible.
List payouts
Pull recent Stripe payouts with arrival date and amount, joined to the underlying balance transactions. Used for payout-to-bank reconciliation.
Search customers
Query Stripe by email, name, or custom metadata field. Used to deduplicate before a new-customer create, or to look up a record from a partial reference.
Webhook: invoice.payment_failed
Triggered on a failed recurring charge. Routes into the dunning workflow with the failure code and customer's communication preferences.
Webhook: customer.subscription.deleted
Triggered on cancellation. Routes into the offboarding workflow that revokes access, drafts the win-back email, and posts the loss reason into the CRM.

15 actions · scroll to see them all

Frequently asked questions

No. Stripe uses OAuth, not API keys, for this integration. When you click Connect, Stripe redirects you through their consent screen, you authorize Ceven's access, and Stripe issues us a refresh token scoped to the permissions you approved. We store the refresh token encrypted at rest and call Stripe's /oauth/token endpoint to mint short-lived access tokens for each agent call. You can revoke Ceven's access at any time from your Stripe dashboard's Connected Apps page, that immediately invalidates our refresh token without us being able to recover it.
Ceven pins to the Stripe API version that was current the day you connected, so a new Stripe version doesn't silently change the shape of the data we hand to your workflows. We bump pinned versions on a quarterly cadence with a 30-day deprecation window for affected workflows, and you'll get an in-app notification before any breaking change. If you need an earlier or later version for a specific workflow, set it in the action params, Stripe accepts the version as a request header.
Both. After connect, Ceven backfills the last 12 months of charges, customers, and subscription state into the workflow context so your first prompts have real data to work with. Webhook subscriptions for future events also fire immediately. The backfill respects Stripe's pagination, large accounts (10k+ subscribers) take a few minutes to complete and you'll see a progress indicator in the Integrations page. If you need a longer backfill, run a one-off list-charges workflow with the date range you need.
Any workflow that's mid-flight when you disconnect completes its current step using the last-valid access token, then pauses at the next Stripe-dependent step with an 'Integration disconnected' error. The workflow does not silently fail or skip steps, pause + alert is the default. Reconnecting Stripe resumes the workflow from where it paused, with the original prompt and parameters intact. If you don't reconnect within 14 days, the workflow auto-cancels and you'll get a summary of what was and wasn't done.
Yes, with a caveat. The OAuth connect flow above covers a single Stripe account, your own. If you're a marketplace operating Stripe Connect with hundreds or thousands of connected sub-accounts, you'll want to use the platform connect mode, which is on by request. It changes the auth flow to use your platform's secret key and lets agents act on behalf of any connected account via the Stripe-Account header. Email support@ceven.io to enable platform mode for your workspace.
Yes. Under Settings → Integrations → Stripe → Permissions, you can allowlist specific actions per agent. The default after connect is read-only on customers, subscriptions, charges, invoices, and disputes, plus write access on refunds, subscription updates, and dispute-evidence uploads. Create-charge and cancel-subscription are off by default for new workspaces because they're irreversible, turn them on explicitly per the agents that need them. Permission changes take effect on the next workflow run; in-flight workflows finish under the old permissions.
Stripe's live-mode limits are 100 read req/sec and 100 write req/sec per account, with burst tolerances. Ceven batches list operations into the largest page size Stripe allows (100), caches reference data (customers, products) for the duration of a workflow run, and queues write-heavy workflows behind a token bucket sized to your account's actual limit. If you're on Stripe's high-volume tier with custom limits, set the override in Settings → Integrations → Stripe → Advanced so we don't artificially throttle.

Related integrations

Alternatives to Stripe

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

Square logoSquarePayPal logoPayPalAdyen logoAdyen

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Stripe and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free