TL;DR

Payment Notifications is a finance workflow that chains Stripe + Slack to automate a common task. Receive a Slack message for every successful payment, failed charge, and subscription cancellation in real time. Once configured, it runs through Claude Code, Cursor, Windsurf or any MCP-compatible AI agent.

💳💬

FinanceBeginner

Payment Notifications

Receive a Slack message for every successful payment, failed charge, and subscription cancellation in real time.

5 min setup, real-time payment visibility2 MCPs required

How it works

💳Stripe

💬Slack

Automated

1Listen for Stripe charge.succeeded events2Format message with amount, customer, plan3Post to #revenue Slack channel+2 more steps

Hostable — runs in your browser2/2 MCPs hosted

Run with MCPizy

New

Execute this recipe in your browser — no local install, no Claude Code. Streams results live.

Whitelisted MCPs: perplexity, notion, anthropic, openai, tavily, firecrawl, coingecko, stripe, slack, github, gitlab, linear, resend, sendgrid, elevenlabs, shopify, sentry, posthog, supabase-mcp, context7, deepwiki~4k tokens · ~$0.012 est.

Why this combo?

Stripe fires events the moment money moves; Slack gets them to the right people instantly. This combo is the fastest way for a whole team to feel the pulse of revenue without everyone needing a Stripe login or checking a dashboard.

Without this workflow

Check the Stripe dashboard periodically to see what happened. Missed a churn event over the weekend. Finance notified a week later.

With MCPizy

Every payment, failure, and cancellation posts to Slack the second it happens. The whole team knows MRR in real time.

Business value

Concrete ROI — not marketing fluff.

Time saved

Sales and ops teams see new MRR in real-time — celebrate wins, catch churn risk within minutes

Workflow steps

1
Listen for Stripe charge.succeeded events
2
Format message with amount, customer, plan
3
Post to #revenue Slack channel
4
Alert #alerts on charge.failed events
5
Daily MRR digest at 9 AM

Use cases

Celebrate every new subscription in a #revenue Slack channel
Immediately alert the team when a payment fails so customer success can act
Daily morning MRR digest so the whole team starts the day aligned
Instant notification on subscription cancellations for retention follow-up

MCPs required

💳

Stripe

Stripe MCP Server

View

💬

Slack

Slack MCP Server

View

Agent prompt (copy into Claude Code)

This prompt is the workflow. Paste into Claude Code, Cursor, or Windsurf.

You are monitoring Stripe payment events and posting summaries to Slack.

On every new payment_intent.succeeded webhook:
1. Call stripe.retrieve_payment_intent(id) to get amount, customer, product
2. Call stripe.retrieve_customer(customer_id) to get email and plan
3. Post to Slack channel #payments: ":moneybag: New payment: $AMOUNT from CUSTOMER_EMAIL for PRODUCT_NAME"
4. On payment_intent.payment_failed, post to #alerts with retry count and link to Stripe dashboard
5. On customer.subscription.deleted, post to #churn with subscription age + MRR lost

At 09:00 daily (cron), post today's MRR digest (net new MRR, failed charges, cancellations) to #revenue.

Reply only with a summary after posting.

Trigger & credentials

How this workflow fires and what env vars you need.

.env.example

WebhookTrigger

POST /webhook/stripe (events: payment_intent.succeeded, payment_intent.payment_failed, customer.subscription.deleted) + daily cron 0 9 * * *

💳Stripe· 2 vars

STRIPE_SECRET_KEYGet key

Your Stripe secret API key

e.g. sk_live_...

STRIPE_WEBHOOK_SECRETGet key

Webhook signing secret

e.g. whsec_...

💬Slack· 3 vars

SLACK_BOT_TOKENGet key

Slack bot OAuth token with chat:write

e.g. xoxb-...

SLACK_REVENUE_CHANNEL

Channel for successful payments

e.g. #revenue

SLACK_ALERTS_CHANNEL

Channel for failed charges

e.g. #alerts

One-command deploy

Install everything — MCPs, prompt, env template — in a single call.

$ mcpizy recipe install stripe-slack-payment-notifications

✓ Installs all 2 MCP servers
✓ Writes prompt to ~/.mcpizy/prompts/stripe-slack-payment-notifications.md
✓ Generates .env.example in current directory
✓ Ready to paste into Claude Code

Requires mcpizy CLI v1.1+ — install via npm i -g mcpizy.

Quick install (MCPs only)

5 min setup, real-time payment visibility

$ mcpizy install stripe && mcpizy install slack

More Finance recipes

💳📝

Invoice Auto-Documentation

Every Stripe invoice is automatically documented in a Notion database with amount, customer, and payment status.

🦎💬

Crypto Price Alerts

Monitor cryptocurrency prices and receive Slack alerts when assets cross custom thresholds or drop more than 5% in an hour.

Frequently asked questions

What is this workflow?

Payment Notifications is a finance automation that uses Stripe + Slack together via the Model Context Protocol. Receive a Slack message for every successful payment, failed charge, and subscription cancellation in real time.

How long does setup take?

Setup takes around 5 min setup, real-time payment visibility. You install the required MCP servers with `mcpizy install stripe && mcpizy install slack`, connect your accounts, and the workflow is ready to run.

What does this workflow change in practice?

Sales and ops teams see new MRR in real-time — celebrate wins, catch churn risk within minutes.

Which MCP servers do I need for this?

You need 2 MCP servers: Stripe (mcpizy install stripe), Slack (mcpizy install slack). All are installable in one command via the MCPizy CLI and configured in your `.claude.json` or `.cursor/mcp.json`.

Does this work with Claude Code, Cursor, and Windsurf?

Yes. The workflow runs with any MCP-compatible AI agent — Claude Code, Claude Desktop, Cursor, Windsurf, VS Code with Copilot, and custom agents built on the MCP SDK. The MCP servers are identical across clients; only the config file path (`.claude.json` vs `.cursor/mcp.json`) changes.

Start building this workflow

Install the required MCPs from the directory and automate this in 5 min setup.

$ mcpizy install stripe && mcpizy install slack

💳Install Stripe 💬Install Slack

Free to install. Connect your accounts and this workflow runs itself.