Detect failed Stripe payments and drive dunning with AI

An Orkeste agent watches Stripe for failed charges, classifies the cause (insufficient funds, expired card, 3DS friction, fraud block), and proposes the right dunning step. Finance approves customer outreach before any email or pause goes out.

How the workflow runs

1. Detect failure: Agent listens to Stripe events for failed charges in real time.
2. Classify cause: Identifies cause: card, balance, 3DS, fraud, network error.
3. Propose next action: Suggests retry timing, email tone or account pause per cause.
4. Finance approves outreach: Finance approves the dunning step before any customer email.
5. Execute and log: Approved action is executed in Stripe and logged for cohort analysis.

Human-in-the-loop: No dunning email, account pause or retry storm fires without explicit finance approval per action.

Works with your stack

• stripe
• gmail
• airtable

Related workflows

• Reconcile Stripe payouts against Airtable records
• Send invoice reminders from Gmail with AI-drafted follow-ups
• Track subscription churn signals in Stripe with AI

Questions about this workflow

Does it replace Stripe's Smart Retries?

No. Smart Retries handles automatic retries; the agent layers on top to drive human-grade outreach decisions.

What about fraud cases?

Suspected fraud is held for finance review and never auto-emailed; the agent surfaces signals from Stripe Radar.

Can it pause subscriptions?

Only after finance approves the pause action. The agent never modifies subscription state autonomously.