Invalid API Key provided

[CodingwithTea]

I have followed all the steps and created a cloud function for a Payment Intent.
Once Payment Intent is received successfully using the Test Account Secret Key. An issue arose when I started initPaymentSheet. The payment sheet tried to open but then crashed, and the error message is below.

StripeException( error: LocalizedErrorMessage(code: FailureCode.Failed, localizedMessage: Invalid API Key provided: pk_test_***********_KEY, message: Invalid API Key provided: pk_test_***********_KEY, stripeErrorCode: null, declineCode: null, type: invalid_request_error) )

This Function is causing issues, although I have declared Test Publishable API Key in the main.dart as suggested.

`
Future _handleCardPayment(String clientSecret) async {

try {
  await Stripe.instance.initPaymentSheet(
    paymentSheetParameters: SetupPaymentSheetParameters(
      paymentIntentClientSecret: clientSecret,
      merchantDisplayName: 'Coding with T',
    ),
  );
  await Stripe.instance.presentPaymentSheet();
} catch (e) {
  rethrow;
}

}`

[remonh87]

you are using the publishable key for your cloud function. You need to make sure that you use the server key. Also keep in mind to inject that key securely

[CodingwithTea]

I have contacted the Stripe Team, but just to let you know that this issue is not with the payment intent. Payment Intent is being created successfully without any issue using my cloud function, and I am successfully returning clientSecret.
Issues arise when I call this method.
await Stripe.instance.presentPaymentSheet();

[CodingwithTea]

This is the response i got from them.

Hi Taimoor,

Thank you for providing the update regarding the response from the Flutter_Stripe support team.

I understand how frustrating this situation can be, and I empathize with your challenges. However, I want to clarify that the error message you are seeing, which indicates "Invalid API Key provided," is coming from the client side, rather than Stripe's servers. This suggests that the issue lies in the integration with the Flutter package.

As noted in my previous email, the message states that the API key being utilized is incorrect. The error message shows you are using a publishable key ending with “_KEY” in your request, which looks to me like a placeholder or a default value instead of a publishable key. I understand that you hardcoded the publishable key from the Stripe Dashboard into your main.dart file, however the error message states the usage of a publishable key ending with “_KEY” which indicates that the hardcoded publishable key was not passed in to the request.

Given that the Payment Intents are being created successfully under your account, we can rule out issues with the Payment Intent itself or your server-side configuration.

To further help troubleshoot the issue, I recommend first checking your codebase or config/settings of your integration, that there is no default publishable key already set or if a string ending with “KEY” exists anywhere in your integration. It might also be helpful to set a breakpoint where you make the API call to ensure the API persists at request time. Furthermore I would recommend testing directly with one of our mobile SDKs (Android[1]/iOS[2]) to test in a sample app if you encounter the same behavior.

At this point, I recommend reaching out to the Flutter_Stripe support team again and pushing for further assistance, as they would have the necessary tools and context to help resolve the integration issue effectively.

If you have any further questions or need additional clarification, feel free to reach out!

Cheers,
Jim

[remonh87]

I will contact stripe internally because it is somewhere in their mobile sdk as I checked our codebase intensively and the stripe ones and this particular error is raised by the stripe ios checkout package.

[CodingwithTea]

Any Update? Or should I use the API to move along?

[remonh87]

I really cannot help here unfortunately it is an error raised by the stripe internal sdk and have no idea how to reproduce this.

[CodingwithTea]

Anyone?

[CodingwithTea]

Ok, thanks for the update.

…

On Thu, 8 May 2025 at 18:43, Rémon ***@***.***> wrote: I will contact stripe internally because it is somewhere in their mobile sdk as I checked our codebase intensively and the stripe ones and this particular error is raised by the stripe ios checkout package. — Reply to this email directly, view it on GitHub <#2142 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A5AD5X7TWMFPTPG7WIV5TGL25NNRBAVCNFSM6AAAAAB4MFRLAKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMBXGYZTQNA> . You are receiving this because you authored the thread.Message ID: <flutter-stripe/flutter_stripe/repo-discussions/2142/comments/13076384@ github.com>