#rajvi_best-practices

1 messages ¡ Page 1 of 1 (latest)

quick salmonBOT
#

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

📝 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.

umbral prawn
#

Hi there

#

Now one of our merchants is asking us to integrate with Stripe's "confirm a payment intent" endpoint to confirm payment intents that they create in their environment.
Not sure if there's a misunderstanding here. I think they are asking if Twilio can update its Stripe integration so it uses PaymentIntents instead of Charges

#

Do you have a request ID for the request that returned that error?

warm scaffold
#

No, they are asking us to integrate with Stripe's confirm payment intent, to confirm the payment intent which they have created in their environment

#

request id from my testing: req_Dunblh3W18X2X2

umbral prawn
#

Hm, I think some things are getting mixed up on your end

#

The request above is a request to confirm pi_3PvKoADw7cot0mC22Unj6cN9. This PI is a valid PI but does not exist on either your user's Stripe account nor the Twilio platform connected to that Stripe account. PI pi_3PvKoADw7cot0mC22Unj6cN9 was created on September 4 on a totally separate Stripe account owned by Twilio

warm scaffold
#

so that account is owned by Twilio but not connected to Twilio platform, am I understanding correctly?

umbral prawn
#

Correct

#

That's why the "No such payment_intent" error makes sense in this case

warm scaffold
#

got it

#

now lets say there is a Twilio user's stripe account or any account which is connected to Twilio Platform which had created payment intent by their own and I am trying to retrieve/update/confirm payment intent, do I need to pass any additional parameters in the request other than payment intent id?

umbral prawn
#

Other than the stripe-account header and the account's ID (which you should be familiar with already), no

#

If you're confirming the PI client side, you'll also need to pass StripeAccount and the accunt ID client side