Project: c3502b62 App: PartagePourboire (Stripe Live), app03dec2277b Stripe account: acct_1UJV0pDP4Gr8JUhn (Live, card_payments active, no pending requirements) Flutter web (purchases_flutter 9.16.1) configures fine with the app's public key and the paywall shows my two Live products (monthly price_1UKe7HDP4Gr8JUhns0Ln15Hk, yearly price_1UKe7HDP4Gr8JUhnnvLDX2vY), both Published. When starting a purchase, POST https://api.revenuecat.com/rcbilling/v1/checkout/start returns 422: {"code": 8142, "message": "Stripe account setup error: Stripe rejected the checkout session configuration."} Stripe Managed Payments is not enabled. Stripe Business details, public details, Checkout settings and Tax settings show no warnings. No POST /v1/checkout/sessions appears in my Stripe logs. What does error 8142 mean here, and which Stripe setting is being rejected?
Stripe Billing web checkout fails with error 8142 (checkout/start returns 422)
Stripe API logs (filters cleared) show only GET /v1/products and GET /v1/prices from RevenueCat (200). When the purchase starts, there is no POST /v1/checkout/sessions and no failed request on the Stripe side, so the 422 seems to be raised before any call to Stripe.
+6Hey
Matt from RevenueCat here! I’ve taken a deeper look into this, and I believe I’ve found what is happening here.
Error 8142 means Stripe rejected the Checkout Session while RevenueCat was creating it. In this case, Stripe is returning a resource_missing error because the Stripe Price sent with the request does not exist on the Stripe account being used for that checkout.
There are two things happening here:
- The checkout attempts are using your sandbox RevenueCat public API key. That sandbox app is connected to your Live Stripe account, so these requests create the Checkout Session in Stripe Test mode. That is why the failed
POST /v1/checkout/sessionscalls do not appear in your Live Stripe logs. With Test mode enabled in Stripe, those failed requests should be visible.
- The Stripe Prices sent in these failing requests were created on a different Stripe account from the one currently connected to RevenueCat. That is why Stripe is returning "No such price."
For a Live checkout, configure your app with the production public API key for your Live Stripe app in RevenueCat, and make sure the packages in your current Offering use the Live Stripe Prices from that same connected Stripe account.
These errors are only coming from the sandbox configuration, which is a healthy sign that the Live configuration is not hitting the same issue.
I hope this helps explain what is happening! If you make those changes and still see the error, please let me know and I’d be delighted to take another look.
Thanks!
Thank you very much matt-heaney,
You correctly identified the source of the problem. It’s now resolved.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.