RevenueCat: Stripe transaction revenue is not being correctly reported
Timeline of updates
- resolved
Data has been backfilled and will be corrected in charts, subscriber lists, and scheduled data exports (aka ETLs) as those systems are refreshed throughout the day. Customers with scheduled data exports will automatically get the new, corrected transactions in their next export. For other integrations (webhooks, etc) if you would like to know specific details with regards to the impact on your project please don’t hesitate to reach out and we can answer questions or concerns. We apologize for any inconvenience caused and will be following up with additional end-to-end testing coverage to prevent similar issues in the future.
From RevenueCat’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.revenuecat.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by RevenueCat, started 2023-10-04 03:49 UTC, resolved after 11 h, 1 update(s).
- Title
- Stripe transaction revenue is not being correctly reported
- Vendor
- RevenueCat
- Date
- URL
- https://rewindex.com/company/revenuecat/incidents/j42527sw048n
RevenueCat profileRecent RevenueCat incidentsAll outages on October 4, 2023RevenueCat in October 2023MarkdownJSON