#dan-burke
1 messages · Page 1 of 1 (latest)
Still looking in to this. That call looks valid and your account's configuration seems to be correct for what you are trying to do here at first glance at least.
Can you quickly try doing that same call without the destination charge portion? You should totally be able to do destination + ACH but I am wondering if this is a connect configuration thing
I just did some testing and found that it works fine if I remove the "on_behalf_of" parameter
the connected account i'm trying to send to is in Argentina
Is it that Argentina-based connected accounts can't accept US bank account payments?e
lmk if you'd still like me to do what you asked as well
Oh that could definitely be it. Checking in to if ACH is available there
Yeah looks like it is only available for US accounts. on_behalf_of makes the connected account the merchant of record so restrictions on their account apply https://stripe.com/docs/payments/ach-debit
Good catch!
The weird thing is, via using PaymentIntents and "confirming" directly via the API, I was able to complete a similar charge with on_behalf_of present
gonna try to grab a request id for you
well here's the payment id:
pi_3MF235Cw67GoJ0rW1zu1wpmu
Apologies, that may be me misunderstanding what restrictions apply here. Thanks for that example. Taking a better look at this
Oh, the destination account there appears to be US. Going to double check this, sorry
Ah yeah. I'm getting the same error now. Alright I guess I just need to not use onbehalfof
Thanks for the help!
Of course! Glad we could figure out what is going on here