CUSTOMER SUPPORT
Refund Fraud: Correlate Stripe Radar Flags to Refund History
When Stripe flags a charge as elevated-risk, checks whether the same customer or payment method has open or recent refund requests in Postgres and Intercom.
How it runs
The automated pipeline, trigger to output.
- TriggerStripe charge flagged elevated-riskStripe
- ActionQuery Postgres for related refund requestsPostgres
- LogicProceed only if Radar flag AND refund activity
- ActionTag and hold Intercom conversationIntercom
- ActionRecord fraud-review case in PostgresPostgres
- OutputAlert risk team in Microsoft TeamsMicrosoft Teams
What it does
Turns Stripe's own fraud signal into a refund-abuse early warning. When Radar rates a payment as risky, the flow looks backward at that customer's refund footprint — if they're also requesting refunds, that's a strong combined fraud signal worth holding.
When to use it
Use this when you already rely on Stripe Radar for payment fraud and want to connect it to your refund pipeline so card-testing and friendly-fraud rings that also abuse refunds surface in one place.
How it works
- 1A Stripe `charge.flagged` / elevated-risk event triggers the flow.
- 2Postgres is queried for any open or recent refund requests tied to the customer or payment fingerprint.
- 3A logic step requires both a Radar flag and refund activity to proceed; otherwise it exits quietly.
- 4When both fire, the matching Intercom conversation is tagged `fraud-review` and put on hold.
- 5A fraud-review case is recorded back in Postgres for audit.
- 6A Microsoft Teams message alerts the risk team with the correlated signals.
Set it up
What you configure once, before turning it on.
- 1Connect StripeCustomers, subscriptions, payments.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect IntercomConversations, contacts, articles.
- 4Connect Microsoft TeamsChannels, chats, files.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Customer Support workflows
Send a tailored Loom onboarding sequence on Front first-reply
When a new customer's first email lands in Front, this picks the Loom onboarding walkthroughs matching their plan and use case, builds a friendly sequenced reply.
Suggest the right Loom video by classifying Intercom message intent
Reads each new inbound Intercom conversation, classifies what the customer is trying to do, and surfaces the best-matching Loom walkthrough to the agent as an internal note.
Draft personalized fix-live replies for support to review
When a Sentry issue resolves, an agent reads each linked ticket's full thread and drafts a tailored 'your fix is live' reply per requester.
Close the loop with requesters when a Linear bug moves to Done
When a Linear issue created from a support escalation moves to Done after deploy, look up the originating Zendesk tickets and notify each requester that their reported bug is…
Reopen and notify Front conversations when their bug fix deploys
When a deploy resolves a Sentry issue, find the snoozed or closed Front conversations linked to it, reopen them, and send the customer a reply that the fix is now live.
Tell Intercom users their reported bug shipped after a Vercel deploy
On a successful Vercel production deployment, match the release's resolved Sentry issues to Intercom conversations and message each affected user that their reported issue is…
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.