#flo_code

1 messages ¡ Page 1 of 1 (latest)

sonic steepleBOT
obsidian skyBOT
#

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.

sonic steepleBOT
#

👋 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/1240727632392491092

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

forest lion
#

Instead of having your andriod app inform your backend when the payment is successful, why don't you use webhook events like payment_intent.succeeded instead?

fringe idol
#

because my backend wont implement webhook right away. It a "legacy" back-end, so I have to work with the current implementation.

#

I know it's not ideal..

forest lion
#

Gotcha

#

Right now we don't include the payment intent ID in the onPaymentSheetResult callback, but you could probably store it as a variable when you initialize the payment sheet and first grab the intent

fringe idol
#

The thing is that it's my backend who create the intent, and the send it to me, but it's not the same as the one on the stripe dashboard, I don't know why ?

#

for instance, this is the token my backend returns (pi_3PH8tbEWmUKDAHBS1RlgMvnQ_secret_4N6sNqUhOx0xWVtJstPZqGh2A), it is also the one I use in the callback of the createIntentCallback of the PaymentSheet.
But when I check my payment on the dashboard, this is the Id : pi_3PH8tbEWmUKDAHBS1RlgMvnQ

forest lion
#

Your backed is returning the client_secret not the Payment Intent ID - the Payment Sheet is initialized based on client secret, so if you want the ID you'd need to change your backend code to also return that

fringe idol
#

I am affraid, they won't be able to do that soon ...
There is no other way to access the paymentId (with a callback somewhere for instance)

forest lion
#

No, unfortunately there isn't a callback that I know of that'll include it - just temporarily you could truncate the client secret (remove _secret_123... ) to get the ID, but I'd strongly recommend you move off of that when you get the chance

fringe idol
#

Yeah, I thought about that I wanted to avoid it, but it seems I don't have the choice ..
But my back-end team is suppose to change that in the following months, and I have to ship the payment in production based on what is implemented today...
Thank you for your help !