#Am.D-error

1 messages · Page 1 of 1 (latest)

turbid python
#

hi! usually this means you mixed up your API keys.

vernal shuttle
#

can you check account id connected to that intent id ? @turbid python

turbid python
#

nope but you can since you called the API to create it really

#

looking at it you are using Connect, so probably you did not pass the right account ID on the frontend perhaps

vernal shuttle
#

i know , but i want to inform backend team about this issue
from the front end whatever backend sent is beiinng sent

#

so i need to know what is the account id connected to that PI to inform backend

#

this implementation is already done @turbid python

turbid python
#

it's not really scalable for you to ask Stripe support for that information all the time

#

I'd suggest syncing with your colleagues overall so that you can design a robust solution here(like have the backend send you the correct account ID acct_xxx that it used to create the PaymentIntent , along with the client secret)

vernal shuttle
#

i know you are right , but i want to inform backend , coz the backend team is saying we are sending the right account id.

#

the account id i mentioned is coming from backend @turbid python

#

which i belive it should be different from the one that payment intent is conencted to , that is the reaso ni am asking for the account id connected with that specific payment intent

turbid python
#

I know but it's not really scalable for you to ask Stripe support for that information all the time

#

your backend team called the API with the account ID, they know what it is

#

you should sync with them