ViablyViably
Stripe

Stripe payments in Slack, with the customer attached.

Point a Stripe webhook destination at your relay endpoint and every charge, invoice and subscription change arrives as a card a person can read. Each one is verified against Stripe's signature, kept in the ledger with its full payload, and attached to the customer it came from.

Add to SlackSee the relay
#payments — Slack
💸
Viastripe
Payment succeeded — $480.00
CustomerDunder Mifflin
PlanViably+ Annual
Invoice#1042
MethodVisa •• 4242
Connect itCreate a Stripe Transactions relay in Viably, paste its URL into Stripe, and copy the signing secret back
What you needAccess to Developers, Webhooks in your Stripe dashboard
Up and running in2 minutes
On your planEvery plan, metered by event volume
Where it landsThe channel you route payments toThe relay ledger, payload and allThe contact's timelineThe revenue reportReceives events
What arrives

The four events worth sending, and what each one is for.

Stripe will happily send you everything it has. These are the ones that change what somebody does that day, and Viably formats each into its own card so nobody has to read raw JSON in a channel.

charge.succeeded

Every successful transaction, whether it came through Checkout or your own integration.
AmountCustomerProductMethodCurrency

charge.failed

The one worth acting on the same day. Viably can spawn a follow-up task so somebody reaches out while the sale is still recoverable.
Decline reasonCustomerAmountProduct

invoice.paid

Enriches the charge card with who the customer actually is, which is also what the contact record is matched on.
NameEmailPhoneCountry

customer.subscription.updated

Fires when a subscriber sets their plan to cancel, early enough for your customer care team to do something before the period ends.
Scheduled cancellationPlan changePeriod end
Recovery

The most valuable event Stripe sends you is the one that failed.

In most teams it lands in a dashboard nobody has open, gets retried twice, and is written off by the end of the month. Viably posts the customer, the product, the amount and the decline reason into the channel that cares, and can open a task assigned to the person whose job it is to win the sale back.

  • Cards a person can read

    Amounts show in the currency they were charged in, the product is named, and the important fields sit at the top of the card.

  • An ending, attached to the event

    Turn on a spawn rule and a failed charge or scheduled cancellation becomes a task with an owner and a due date for the recovery.

  • Verified before it reaches you

    Every request is checked against the Stripe signing secret you pasted in. Each card in your channel is an event Stripe actually sent.

#payments — Slack
Attribution

The payment already knows who paid it.

Viably matches a charge to a contact on the email address, so the person who filled in your form in March and paid in June is one record rather than two. That match is what lets the revenue report say which source, which campaign and which landing page actually earned the money.

ViablyViably
The Viably contacts dashboard, showing the acquisition funnel, revenue by source, a capture trend, and the contact table
  • One person, every touch

    Forms, enquiry emails, in-app events and payments all land on one contact, matched by email, with the source that first brought them in.

  • Lifetime value without a spreadsheet

    Charges add up on each contact. Sort by lifetime value to find your best customers, or check the leaderboard.

  • The payload stays readable

    Every event stays in the relay log exactly as Stripe sent it. Search it, read the raw body or replay it.

Delivery

Retries, batching and a log you can replay.

The relay behind this integration is the same one that accepts events from anything else you point at it. A burst of charges folds into one card instead of nine, a delivery that fails is retried with backoff, and nothing is dropped quietly.

How the relay works
ViablyViably
The Viably webhook relay, showing endpoint health, event volume over ninety days, and the searchable delivery log

Priced on the events, so the bill follows the business.

A busy month is a question of how many charges landed, and that is exactly what Viably counts. The Free plan carries a monthly event allowance that covers most early-stage volume, and Viably+ raises it for businesses taking payments all day.

14 days
Viably+ trial.
Seats on every plan
$7
per day, billed annually
3,000
Events each month
The Viably relay log, showing Stripe deliveries with volume over ninety days
The Viably relay controls, showing retries, manual replay, CSV export and event analytics
The Viably contacts dashboard, showing revenue by source and the acquisition funnel
Every charge Stripe sent, where it went, and the delivery report, kept long after the channel message has scrolled away.
FAQ

Questions about the Stripe integration

What does the Stripe Slack integration do?
It posts your Stripe charges, failed payments and subscription changes to a Slack channel as cards anyone can read. We match each payment to a contact by email, so you see who paid and where they first came from. A failed charge can also open a task, so somebody follows up the same day.
How long does it take to get Stripe events into Slack?
A couple of minutes. You create a relay endpoint in Viably, paste its URL into your Stripe webhook settings, and pick the events you care about. There is no server to deploy and no code to write.
Which Stripe events are worth sending?
Successful charges tell you the business is working, failed charges are the ones worth acting on the same day, and subscription updates tell you when plans change. Viably formats each into its own card rather than dumping raw JSON into the channel.
Does a payment tell me anything about the customer?
Yes. The payment attaches to a contact keyed on the email address, so the person who filled in your form in March and paid in June is one record. That is what lets the reporting say which channel earned the revenue.
Do I need Stripe's CLI or a tunnel to test this?
No. The endpoint is a public URL from the moment you create it, so you can send a test event from the Stripe dashboard and watch it land in Slack immediately.
Can a failed payment create a task automatically?
Yes. A relay endpoint can spawn a task when an event arrives, so a declined charge or a scheduled cancellation lands on the board with an owner and a due date instead of scrolling out of the channel.
What happens if Slack is down when an event arrives?
The event is still accepted and still written to the ledger, and the delivery is retried with backoff. You can also replay any event from the log by hand once you have fixed whatever was wrong.
Can I send Stripe events without using Slack at all?
Yes. The endpoint, the ledger, the contact record and the revenue report all work with no Slack workspace connected. Routing to a channel is an output you may never turn on.
Read the full guideStripe Webhook to Slack Setup
Go deeper

Where this leads next

Recover lost sales with Slack webhooks

How we chase failed Stripe charges from Slack while the customer still wants to pay.

Webhook to Slack

The relay itself: retries, batching, replay, and the log every event is kept in.

CRM and contacts

Where a charge becomes a customer with a history behind them.

More integrations

Connect something else

Everything lands in the same record, so the second service you connect takes less setting up than the first.

Slack

@Via coordinates tasks and automations in your Slack channels. Natural language support and emoji-triggered shortcuts.

Google Search Console

Google Search Console and analytics plugged into your MCP and automation workflows

GitHub

Viably spawns issues, draft Pull Requests to help fix bugs and search console findings, and reports merging status to your channels

Ready when you are

Put the money in the room.

Create a Stripe relay, paste the URL into your webhook destination, and send a test event from Stripe to watch it land.

Add to SlackSee pricing
SignalRecordOwned work
  • Free to start
  • No credit card required
  • Powers on when you need them