Stripe
Connect Stripe via Nango OAuth to ingest business signals.
The Stripe connector ingests business signals — payment failures, disputes, and subscription changes — via Nango OAuth polling. These events provide context about how code changes correlate with business outcomes.
Setup via Nango
Stripe is connected through Nango, which manages OAuth tokens and provides a proxy API.
- Configure Stripe OAuth in Nango Dashboard
- Add a Stripe integration in your Nango dashboard
- Complete the OAuth flow to connect your Stripe account
How It Works
The poll worker runs every 5 minutes and:
- Discovers active Stripe connections via Nango
- Fetches recent events using Stripe's Events API (proxied through Nango)
- Filters for supported event types
- Stores signals with extracted entities
- Enqueues memory processing
Supported Events
| Event | Signal Category | What's Captured |
|---|---|---|
charge.failed | business | Amount, currency, failure code, failure message |
charge.dispute.created | business | Amount, currency, dispute reason |
customer.subscription.created | business | Plan name, subscription ID |
customer.subscription.updated | business | Previous and new status |
customer.subscription.deleted | business | Subscription ID |
invoice.payment_failed | business | Amount, currency |
Events not in this list are silently dropped.
Entity Extraction
The Stripe connector extracts:
- Customer ID as a
userentity (e.g.,cus_XyZ123)
This allows Mneme to correlate payment issues with specific customers across signals.
Configuration
Stripe is configured via Dashboard → Connectors → Stripe. Enable/disable the connector from the dashboard.