Stripe errors: exact messages and their fixes

5 errors

Stripe error messages, A to Z

• Neither apiKey nor config.authenticator provided

  stripe-node throws it when new Stripe() gets an empty key, such as STRIPE_SECRET_KEY unset at build time. Invalid API Key provided means Stripe rejected it.

• No signatures found matching the expected signature for payload

  Stripe "No signatures found matching the expected signature for payload": the body was parsed before verification or the whsec_ secret is wrong. Use req.text().

• No such price: 'price_...'

  Stripe says No such price when the price ID is not in the account or mode of your secret key, often a test price with a live key. Use that mode's price ID.

• SubtleCryptoProvider cannot be used in a synchronous context

  Stripe throws "SubtleCryptoProvider cannot be used in a synchronous context" in Supabase Edge Functions. Verify with constructEventAsync instead.

• The payment_method_types parameter is no longer supported

  Stripe API 2026-09-30.endive removed payment_method_types, and stripe-node 23 pins it. Delete the param, or pass allowed_payment_method_types instead.

How to use it

How to use this index

Look for the text your app, build log or browser console printed, without the parts that change between projects: table names, IDs, routes and URLs. The list is sorted by that text.

Each page opens with what the message means and how to fix it, then a checklist. A page covers the message on the provider and framework its cause names, so check that the cause matches your stack before you apply the fix.

Supabase errors · Vercel errors · Next.js errors · All provider errors