#ganesh-gawali_docs

1 messages · Page 1 of 1 (latest)

hardy aspenBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1468609912887054439

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

split cliff
#

Hello! Taking a look 🙂

#

Since you're using a mobile integration, you must confirm the payment client-side (step 3) but you do have the option to manually capture the payment on the server-side afterwards (step 4).

naive vortex
#

okay

#

Want to avoid step 3 so 1st manually capture then step 2 and directly step 4 will this work?

split cliff
naive vortex
#

okay

split cliff
#

Just so you're aware, the server-driven integration does not work with tap to pay.

naive vortex
#

okay. then the server drivern option will not work for us

#

My code of tap to pay is working perfeclty fine till CollectPaymentMethod. on ConfirmPaymentIntent the SDK is throws an error - {
"code": "PAYMENT_ERROR.DECLINED_BY_STRIPE_API",
"message": "You did not provide an API key. You need to provide your API key in the Authorization header, using Bearer auth (e.g. 'Authorization: Bearer YOUR_SECRET_KEY'). See https://stripe.com/docs/api#authentication for details, or we can help at https://support.stripe.com/."
}

Stripe API Reference
split cliff
#

Can you please share the request ID for this failure?

naive vortex
#

okay

hardy aspenBOT
umbral spear
#

hey there are you still around?

#

I was helping you look into this with my colleagues yesterday

#

With the context that your integration is successfully getting connection tokens, connecting to readers, and collecting payment method details to attach to payment intents, i can see that most things are working as expected.

#

This was from one of you payment intents yesterday that I looked up

#

You can see the external IP address your reader used there, by the way

#

So, where is this breaking?

#

My suspicion is that there is a problem with your app/navigation state that is impacting your Stripe Terminal SDK instance between collectPaymentMethod and confirmPaymentIntent

naive vortex
#

It is breaking in ConfirmPaymentIntent

umbral spear
#

Yes I understand that

#

It would also be useful to add some diagnostic logging around where you call initialize() for the terminal SDK to see if you're unexpectedly re-initializing.

naive vortex
#

Okay will try getIsInitialized()

naive vortex
#

what is the use of this - getIsInitialized()

umbral spear
#

I want to see if the instance recognizes itself as being initialized or not at the time you call confirm

naive vortex
#

okay