#johan
wintry herald
What issue are you facing? Can you share the request ID (req_xxx) of the error? Here’s how you can find it: https://support.stripe.com/questions/finding-the-id-for-an-api-request
runic bloom
perfect I will find that for you
hard troutBOT
runic bloom
sorry it took me a while to find it because i was in the wrong account here it is -> req_urfiTLLqyYM1aQ
gritty warren
Hi @runic bloom I'm taking over this thread
runic bloom
thanks a lot for your help
at the moment these type of transactions does not fail in our same region (EU) but when it's a customer from the US it fails with the error on that request ID object
gritty warren
Account debit is available in Australia, Canada, Europe, Hong Kong, Japan, New Zealand, and the US. Stripe supports Account Debits only when both your platform and the connected account are in the same region (for example, both are in Japan).
runic bloom
is there another way we can charge customers from all regions so we don't have that issue?
gritty warren
Is it about how to move funds from a connected account to platform?
runic bloom
yes!
gritty warren
OK, another way is to create a transfer reversal https://docs.stripe.com/api/transfer_reversals/create but you need to specify an existing transfer ID to do that
runic bloom
so do I need to create a transfer before doing the reversal? I'm not sure if I follow this approach
gritty warren
No, I mean you can use an existing transfer (assume you are using destination charge or separate charge and tranfer) to create a reversal
runic bloom
we're using payment intents
where we charge the connected account
and then we also create charges in some cases when we want to apply a fee to the connected account
but that only works for EU accounts, for other regions it gives that error
gritty warren
Do you have an ID of PaymentIntents that I can take a look?
runic bloom
sure
ch_3Onx7uPcHUrgcnQP0uzdgq2j
so our flow is the following:
a customer requests a refund, the refund is processed
in some cases we apply a refund fee depending on the date it was requested
the refund fee is applied in a separated charge using charges.create
but at the moment charges.create does not work for accounts of different region
we want to resolve that
gritty warren
Hmm, you are using direct charges on a custom account?
You shouldn't do that, you should use destination charge instead
runic bloom
what are destination charge? how can I use them?
gritty warren
runic bloom
I'm not sure if that will work. us (platform account) charge our connected accounts a fee using charges.create so the amount gets deducted from their stripe account balance directly
at the moment that only works for EU accounts, but it gives an error in other regions
how can we resolve that and avoid that error?
this would also error
gritty warren
You can specify on_behalf_of attribute for cross-region payments
runic bloom
I'm really sorry I'm not sure if I'm following. I can see the transfer_data parameter setting a destination field that contains a connected account
why is this?
so do I need to remove transfer_data field and add on_behalf_of instead?
gritty warren
If you are using destination charge, you should set transfer_data[destination], and also on_behalf_of if the platform and connected account are not in the same region
runic bloom
so say for example we have a connected account: "acc_test" and we would like to charge them a fee of 5 euro, what would be the object we need to pass to paymentIntents.create ?
that part confuses me because the transferdata[destination] is our connected account ID right?
gritty warren
https://docs.stripe.com/connect/destination-charges?lang=node#application-fee you can charge through application_fee
runic bloom
but we also want the amount itself
I don't think that approach would work for us?
we currently do this and it works perfect. we would like to have a similar approach for other regions. how do we do this?
gritty warren
I don't understand why it doesn't work for you. Can you elaborate?
runic bloom
let me find out a bit more and I will get back here with more details. thanks for the help!