# RevenueCat: Incorrect subscriber details for customers with more than one RevenueCat promotional transaction

> RevenueCat status incident “Incorrect subscriber details for customers with more than one RevenueCat promotional transaction” on 2024-01-30: impact none (vendor’s label), 0 min, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/revenuecat/incidents/prmr3dfgjzp9
Last updated: 2024-01-30T06:30:00Z

- Impact (vendor’s label): none
- Status: resolved
- Started: 2024-01-30 06:30 UTC · Resolved: 2024-01-30 06:30 UTC · Duration: 0 min
- Updates: 1
- [Vendor status page: https://status.revenuecat.com/incidents/prmr3dfgjzp9](https://status.revenuecat.com/incidents/prmr3dfgjzp9)
- [Company: RevenueCat](https://rewindex.com/company/revenuecat.md)

## Timeline of updates

- **resolved** 2024-01-30 06:30 UTC: From 6:30 AM UTC on January 30th 2024 to 7:00 AM UTC on February 5th 2024, the subscriber details in the subscriber info endpoint (/v1/subscribers), the receipt endpoint (/v1/receipts) and the customer\_info field in events sent to Firebase Cloud Functions can potentially contain incorrect information for subscribers with multiple RevenueCat promotional transactions. This only impacts customers that have 2 or more RevenueCat promotional transactions. It does not impact unlocking of entitlements via the RevenueCat SDK, even if a customer has 2 or more RevenueCat promotional transactions. For impacted subscribers, the subscriber response would have the following incorrect values: \* The product\_id field in the entitlements section can be incorrect for entitlements that are unlocked via RevenueCat promotional transactions. \* In the subscriptions block, when there are multiple RevenueCat promotional transactions, only one will be in the block. Additionally, the key used (which is supposed to be the product identifier) can incorrectly be the product identifier for another promotional transaction for the customer. If you have any questions or concerns, please reach out to our support team. We apologize for any inconvenience caused, our test suite has been updated to ensure better coverage for multiple promotional transactions on the same subscriber.

_From the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._

## Cite this

Status incident (vendor impact label: none) posted by RevenueCat, started 2024-01-30 06:30 UTC, resolved after 0 min, 1 update(s).

- Canonical URL: https://rewindex.com/company/revenuecat/incidents/prmr3dfgjzp9
- Citation: RevenueCat, “Incorrect subscriber details for customers with more than one RevenueCat promotional transaction” (2024-01-30 06:30 UTC). Archived by Rewindex: https://rewindex.com/company/revenuecat/incidents/prmr3dfgjzp9 (CC BY 4.0).
- Markdown link: `[RevenueCat: Incorrect subscriber details for customers with more than one RevenueCat promotional transaction (2024-01-30)](https://rewindex.com/company/revenuecat/incidents/prmr3dfgjzp9)`


---
Canonical: https://rewindex.com/company/revenuecat/incidents/prmr3dfgjzp9 · Markdown: https://rewindex.com/company/revenuecat/incidents/prmr3dfgjzp9.md · JSON: https://rewindex.com/api/v1/companies/revenuecat/incidents/prmr3dfgjzp9 · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T17:43:43.033Z