#Dan Judge
1 messages · Page 1 of 1 (latest)
acct_1N7y90CplrA0tpjQ
acct_1N7y97CiR49UaHd1
acct_1N7y9ECZtuc9d3pO
Thanks @quiet turtle
acct_1N7y90CplrA0tpjQ was created by https://dashboard.stripe.com/logs/req_YodHtCPsjMrMZU
acct_1N7y97CiR49UaHd1 was created by https://dashboard.stripe.com/logs/req_Q6z2uRs65whCQz
acct_1N7y9ECZtuc9d3pO was created by https://dashboard.stripe.com/logs/req_PpyjMqpFoQo5V2
If that's not expected, you need to investigate on your end why you are sending these requests to Stripe.
I've seen those logs, what about a delay? Is there a delay before I can create an account link via the API after creating an account? Or should I be able to create the link immediately after creating the account?
Could this be something to do with the application being in a loop because the customer trying to onboard has already onboarded before even though I've deleted those previous accounts via the DELETE API?
Is there a delay before I can create an account link via the API after creating an account?
No
Or should I be able to create the link immediately after creating the account?
Yes
Your backend code is calling multiple times the POST /v1/accounts endpoint. You need to investigate on your end why.
From our point of view everything worked as expected: you called POST /v1/accounts three times, so we created 3 accounts.