ONE TIME PURCHASE PROBLEM

Hey ​@maikelgalvao,

Could you clarify what you mean by “supplier” here? For context, the App Store / Play Store fully control who owns what and RevenueCat just reflects what the store says.

For one-time / non-consumable products, a given store account (sandbox Apple ID / Google test account) can only purchase a specific product ID once. After that, the store will just return the existing purchase, which is why it looks like the payment is “automatically validated” with no new charge. So that’s expected, both in sandbox and production.

If you need users to be able to buy the same thing multiple times (for different suppliers or use cases), you’d either want to use consumable products and track that mapping on your backend, or use distinct product IDs. To see a “fresh” purchase flow in sandbox for a one-time product, you’d need to use a different test account or a different product ID.

When you say I need new IDs, are you referring to the ID configured in the Play Console dashboard or the IDs sent in the purchase request? Isn't it RevenueCat that dynamically generates payment IDs?

Yes, those product IDs (like fee_tier_3, fee_tier_10, etc.) are exactly what I was referring to, those are configured in your Google Play Console/Apple Store Connect.

From what I understood, if you're trying to test the same non-consumable product multiple times in sandbox:

• you don't need new product IDs
• you need a new sandbox test account (different test Apple ID or Google test account)
• the store won't let the same account buy the same non-consumable product ID twice

If you actually need different “suppliers” to each purchase the same tier independently in production:

• you'd need separate product IDs per supplier (e.g., fee_tier_3_supplier_a, fee_tier_3_supplier_b)
• or use consumable products instead

And as for transaction/payment IDs, RevenueCat doesn't generate them. Those are created by Apple/Google when a purchase happens and we just validate and track them.

!-->