Stripe + Eru
Connect your billing data to see how customers, subscriptions, and revenue map to your CRM, product, and support systems. Reconcile the numbers that matter.
What Eru reads from Stripe
Eru connects to Stripe via API key (read-only) and accesses your billing data through the Stripe API. It discovers your specific configuration—products, prices, metadata fields—rather than assuming a generic setup.
Customers
Customer records with email, name, metadata, and payment methods. Eru maps Stripe customers to entities in your other systems using email, metadata fields, or pattern matching.
Subscriptions
Active and cancelled subscriptions with status, plan, quantity, and billing cycle. Eru tracks MRR, understands prorations, and maps subscription states to your internal definitions.
Invoices and charges
Invoice history and individual charges. Eru uses this for revenue reconciliation—comparing what was billed to what your database thinks should have been billed.
Products and prices
Your product catalog and pricing structure. Eru understands which products map to which tiers or features in your system.
Payment events
Failed payments, refunds, disputes. Eru surfaces payment friction as a potential churn signal and tracks resolution.
How Eru maps Stripe data
Stripe data is structured but often disconnected from your other systems. Eru builds the connections.
Customer identity resolution
Stripe customers need to map to your internal accounts. Eru looks for connections: email addresses matching CRM contacts, metadata fields containing your internal IDs, domain patterns linking to company records. Each mapping gets a confidence score.
Revenue definition alignment
What Stripe calls "MRR" might not match your definition. Eru learns your specific calculation: which subscriptions count, how to handle trials, whether to include add-ons. It documents the mapping explicitly.
Product-to-feature mapping
Stripe products and prices map to features or tiers in your application. Eru discovers these relationships so you can analyze usage by plan or track feature adoption by pricing tier.
Common use cases
Revenue reconciliation
Compare Stripe MRR to database MRR to CRM deal values. Catch discrepancies automatically with scheduled Truth Checks.
Churn signal detection
Combine payment failures and downgrades with usage and support data to identify at-risk accounts before they cancel.
Billing-product alignment
Verify that customers on specific plans have access to the right features. Catch entitlement mismatches.
Financial reporting
Build a reliable revenue foundation for board reports. Know that the numbers match across systems.
Example: MRR reconciliation check
Setup
1. Create a restricted API key
In Stripe Dashboard, create a restricted key with read-only access to Customers, Subscriptions, Invoices, and Products. No write permissions needed.
2. Connect in Eru
Enter the API key through Eru's secure credential form. The key is stored encrypted and never sent to the AI.
3. Eru explores your data
The agent samples your Stripe data, discovers your product catalog, and identifies metadata patterns used for linking.
4. Map to other systems
Eru proposes mappings between Stripe customers and your other data sources. Review and approve the relationships.
Other integrations
Connect Stripe to Eru
Reconcile billing with the rest of your data stack.