#pitxardo_api
1 messages ¡ Page 1 of 1 (latest)
đ 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/1255147221834399815
đ Have more to share? Add details, code, screenshots, videos, etc. below.
Hey there, can you share an example request ID where you get this "no such setupintent" error?
yes, these are the values generated by our back-end when the Setup Intent was created:
stripeAccount = acct_1LHndwDSyVrA4ZKz
stripeCustomerId = cus_QMCsVr57aNsx4O
clientSecret = seti_1PVUScAP8I9LfBKlEOgTVDUa_secret_QMCsAXlhcfi4kaPIVEIlRrdktgvPg0w
Then we use the clientSecret and stripeAccount to call collectBankAccountForSetup from our front-end, and this is the response:
{type: 'invalid_request_error', code: 'resource_missing', message: "No such setupintent: 'seti_1PVUScAP8I9LfBKlEOgTVDUa'"}
Can you get the request ID like req_123 from the request-id response header?
Ah, actually, here: https://dashboard.stripe.com/test/logs/req_cNaC5RNy3fCHw4
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
You're creating that setup intent on your platform account, on the connected account
if you're using these with stripeAccount client side for direct charge patterns, you need to use the stripe-account header server side too, when you create the setup intent
I mean, when you created the setup intent, you need to indicate the same (matching) connected account there that will be used for confirmation
https://docs.stripe.com/connect/authentication#stripe-account-header
I see
I will try that and see what happens
did anything change recently? because this was working until recently
It looks like until recently your requests involved a 3rd party: https://dashboard.stripe.com/test/logs/req_nBDOxC3ypEeeSr
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
but using that header or not (direct charge or on your account) seems to vary per request
then, Stripe directly for ACH
Gotcha, in that case your direct requests appear to be missing that header when needed
It looks like you did use it for some requests yesterday, which encountered errors related to payment method configurations: https://dashboard.stripe.com/test/logs/req_YY20S2XMzGumSA
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.