subandi_api

[strong harbor]

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

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

[long cave]

(both are test accounts, but the same seems to happen in production as well)

[molten jay]

hi there!

what do you mean by "cannot be found"?

[long cave]

we do a request to e.g .https://api.stripe.com/v1/payment_intents/pi_3RaxplEByf5Mzg1L05QAybIw?is_stripe_sdk=false&client_secret=pi_3RaxplEByf5Mzg1L05QAybIw_secret_nF8ARPOTeniT1xQshNdptB6gL&key=pk_test_51OHSdZKepkzpxF3UAFoXkp4YGRE9lGZyQcGxp1Lf9qS35ocVeHXMQB64HGeo6QKQKvTRw97gNg8qAJlGkWWIpvpK00k1UDLDyW

and it says "not found". But we use a payment intent id we just got back from you seconds earlier

[molten jay]

can you share the request ID (req_xxx)? you can find it here https://dashboard.stripe.com/test/logs

[long cave]

here is the equivalent for a working / found payment intent https://api.stripe.com/v1/payment_intents/pi_3Ray1FELJmRcNL7B0CSjYZW7?is_stripe_sdk=false&client_secret=pi_3Ray1FELJmRcNL7B0CSjYZW7_secret_oJ4PcrVzCMhlvprf8M5MFDuse&key=pk_test_51ROwaLELJmRcNL7Bg2UUJvxvorp041SUqyFykZ4pz3gMSAYb7Q0K7dRTu5pYVCk6awrkUVdpPyDQgkjHEXPCAxLu00il1VLezR

sure, 1s

here we post, and get an intent back: req_zkp71MxR4VScSt

and here we request it: req_59HrwkJwDK879P and it says not found: req_59HrwkJwDK879P

[molten jay]

that's normal, you are trying to retrive it from a different connected account.
PaymentIntent was created on connected account that ends with zg1L
Then you try to retrive it on connected account that ends with xF3U

so you need to double check your code making these API requests.

[long cave]

ok thanks. I'm trying to reproduce something that happens in production, but you might be right this here is an issue with my local setup (I use multiple accounts). Is there a way to leave this "ticket" resting, and I can come back with actual live requests and you check those, too?

[molten jay]

it will be automatically closed when inactive. but feel free to reopen a new thread if needed.

[long cave]

ok will do thanks

ok I have a cleaner test. In req_TirBpSObEQkaug I created an intent. In req_XST4XdUwGzpjT1 it says it was not found. But there is also a request in between: req_XD5ccrByjX3Enu, that confirms this intent (before it is then not found).

[molten jay]

again, you are using different connected account ID.

in req_TirBpSObEQkaug, you set the Stripe Account header to acct_xxxxxxxxMzg1L
in req_XST4XdUwGzpjT1, it's set to acct_xxxxxxxxxxpxF3U

so it's completely normal that you get a "not found" error.

[long cave]

and which was used in req_XD5ccrByjX3Enu?

[molten jay]

acct_xxxxxxxxMzg1L

[long cave]

(for the get request, I can see the accounts in the logs, but not the posts)

[molten jay]

I recommend reading this guide about the Stripe Account header: https://docs.stripe.com/connect/authentication

[long cave]

thanks. I will. But I'm primarily trying to figure out what changed, since this worked flawlessly before.