The Stripe integration monitors your Stripe account for the payment events that matter most to your business. Payment failures and disputes arrive as Critical alerts; subscription changes and refunds are tracked so nothing slips through unnoticed.Documentation Index
Fetch the complete documentation index at: https://docs.logbrew.co/llms.txt
Use this file to discover all available pages before exploring further.
What you’ll see
- Payment failures:
payment_intent.payment_failed,invoice.payment_failed(Critical) - Disputes: a charge dispute has been opened (Critical)
- Subscription canceled: a customer’s subscription has been deleted
- Refunds: a charge has been refunded
- Successful payments: successful charges and completed checkout sessions (Info)
- Plus additional curated payment lifecycle events across the most common Stripe objects
Connect Stripe
Authorize with OAuth
LogBrew opens the Stripe authorization screen. Sign in to your Stripe account if prompted, then approve access for your live Stripe account.
Severity mapping
| Event type | LogBrew severity |
|---|---|
| Payment failed | Critical |
| Dispute created | Critical |
| Invoice payment failed | Critical |
| Subscription canceled | Warning |
| Refund issued | Warning |
| Payment succeeded | Info |
| Checkout completed | Info |
Live mode only
Notification defaults
LogBrew’s default notification setting is Critical only. This means successful payments (
payment_intent.succeeded, invoice.paid, checkout.session.completed) do not trigger a push notification by default. To receive notifications for all events including successful payments, go to Settings, Notifications and switch to All for your Stripe project.