#reverie-payouts

1 messages · Page 1 of 1 (latest)

iron wren
glossy sorrel
#

Oh wow thanks I didn't see this

#

This looks like exactly what I need though

iron wren
#

try it out and let me know if you're still having trouble creating an external account

glossy sorrel
#

Yeah for sure ty

iron wren
wanton mason
#

I think I may have found a bug with this. I ran the curl command indicated here: https://stripe.com/docs/treasury/moving-money/payouts#financial-accounts-as-external-accounts on an account in production that was fully set up but didn't have the financial account set as the external account. The financial account was actually added twice and so now the custom connect account has duplicate external bank accounts. I checked my terminal and confirmed that I only ran the curl command one time

iron wren
wanton mason
#

Yea there are two requests in the logs

#

do you want both?

iron wren
#

yep, both would be good

wanton mason
#

Ahhh, and interesting enough there's a 3rd one on the 4th of this month, that came through as a 200 but seemingly didn't link the financial account as the external one

#
  1. Came in on the 4th of August. 200 for linking financial account as external account, but some other operation must have failed because the account wasn't linked req_mB3Bxr1oDLHEmc
iron wren
#

let me know what's the request id for 2. and i'll take a look

wanton mason
#

whoops I was looking at the "from your platform" API logs

#

here's the "from this account"

#

^^second is the classier link sorry haha

#

But hand to god I ran one curl command, and now there's two of the same external bank account, same routing and account number and same fingerprint

iron wren
#

hmmm, i see one request made from curl, and the other one is made using the stripe-node library

#

are you using the stripe-node library in your server code?

wanton mason
#

Sorry for the delayed response! We're using the stripe-node library on our backend, yes

iron wren
#

i think....maybe something may have triggered your code in the backend?

wanton mason
#

I literally only ran the curl command

#

I suppose it's possible that someone else on our team ran the same command from the backend? But for the same custom connect account seems unlikely