#1cyFir3
dull trellis
naive birch
you have to pass StripeAccount on the frontend as well when initialising the library https://stripe.com/docs/connect/authentication#adding-the-connected-account-id-to-a-client-side-application
out of interest are you only using Direct here because I mentioned it? what were you doing before? What do you do for accounts not in Malaysia, how do you integrate?
keen tulip
It works when I pass stripe account id.
Before, I only use destination charge payments using on_be_half_of field so I didn't need to pass stripe account id.
naive birch
ok, well note using Direct changes a lot of things really(for example the connected account now is liable for refunds and disputes whereas with Destination it was you), so be sure to understand the impact
I just said Direct because I assumed it's what you used. But you can still do Destination charges with MY accounts. You just can't take application fees. There's no perfect solution here really, it's a limitation
keen tulip
Thanks for the explanation. I will look into more.
One more question though. How can I do destination charge without application fee?
I removed application_fee_amount field when the payment is created but it still gives me the error.
naive birch
what's the error?
keen tulip
Stripe doesn't currently support application fees for platforms in SG with connected accounts in MY.
naive birch
do you have the request ID req_xxx for that? (https://support.stripe.com/questions/finding-the-id-for-an-api-request)
keen tulip
req_nVHVkWzw7QQa3I
naive birch
you did pass a fee : https://dashboard.stripe.com/test/logs/req_0Q6Foo53QR1Ukq