Stripe预授权支付报错：No such SetUpIntent（v16.1.1）排查求助

Let's work through the possible causes and fixes for this error, based on your code and problem description:

1. Validate the Client Secret & Environment Match #

• First, confirm the clientSecret you’re passing is exactly the value returned by your backend when creating the SetupIntent. Stripe’s client secrets start with seti_test_ (test mode) or seti_live_ (live mode) — make sure this prefix matches your frontend’s publishable key environment (test keys pair with test secrets, live keys with live secrets).
• Don’t mix up the SetupIntent ID (format: seti_xxx) with the client secret! These are distinct values, and only the client secret should be used for frontend confirmation.

2. Check if the SetupIntent is Already Consumed or Expired #

• SetupIntents can only be confirmed once. If it was already successfully confirmed, canceled, or has expired (Stripe auto-expires them after 24 hours), reusing its client secret will trigger this error.
• Head to your Stripe Dashboard → Payments → SetupIntents, look up the corresponding record, and check its status. If it’s not requires_payment_method or requires_confirmation, you’ll need to generate a new SetupIntent.

3. Debug Parameter Flow in Your Code #

• Add a log statement to print the full clientSecret right before calling stripe.confirmSetupIntent. Ensure there are no extra spaces, truncated characters, or typos in the value.
• Verify that clientSecret isn’t being overwritten or set to an empty string somewhere in your code before reaching this block.

4. Update the Stripe Android SDK #

• Outdated SDK versions can cause compatibility issues with Stripe’s API. Make sure you’re using the latest stable version. In your app-level build.gradle, update the dependency:

  implementation 'com.stripe:stripe-android:latest.stable.version'
  

Quick Validation Steps #

1. Create a fresh SetupIntent via your backend, log the client secret, and use this exact value directly in your frontend test code to rule out data corruption during transmission.
2. Double-check that your backend’s secret key matches the environment (test secret for test mode, live secret for live mode) — even if you verified this before, a second check never hurts!

内容的提问来源于stack exchange，提问作者Naseer Attari