#knuppi_api
vivid larkBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1247887708760571994
đ Have more to share? Add details, code, screenshots, videos, etc. below.
thorny trench
When trying to call your API, I get the error:
I0605 14:17:51 _util <stripe:128> message='Request to Stripe api' method=post url=https://api.stripe.com/v1/payment_intents/pi_3POImoPokNd7NxTB0V6QaEFl/confirm
I0605 14:17:52 _util <stripe:128> message='Stripe API response' path=https://api.stripe.com/v1/payment_intents/pi_3POImoPokNd7NxTB0V6QaEFl/confirm response_code=404
I0605 14:17:52 _util <stripe:128> error_code=resource_missing error_message="No such payment_intent: 'pi_3POImoPokNd7NxTB0V6QaEFl'" error_param=intent error_type=invalid_request_error message='Stripe API error received'
stripe._error.InvalidRequestError: Request req_szk7xpjqPu0ivr: No such payment_intent: 'pi_3POImoPokNd7NxTB0V6QaEFl'
silk pelican
hi there!
that PaymentIntent exist, but it was created on a different account
looks like your Stripe-Account header is set to the wrong account.
thorny trench
When I'm setting breakpoints in the code, it looks like I'm indeed setting the correct stripe_account
silk pelican
the PaymentIntent was created by the connected account acct_****NxTB. but the failed request was made on acct_****RhmC
thorny trench
the failed request is done with stripe.PaymentIntent.confirm?
silk pelican
yes
thorny trench
Oh, hmm. then perhaps my code is working, but my test case is broken
silk pelican
that's possible. but to summarize: the account confirming the PaymentIntent has to the be same one that created it.
thorny trench
Yes, that makes perfect sense
I just did another test
"intent_id":"pi_3POIwYPokNd7NxTB1MFlpAXf"
Are you able to check that everything went A-OK?
It looks good from my POV
silk pelican
I confirm the creation and confirmation were successful!