#umu_api
1 messages ¡ Page 1 of 1 (latest)
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1362194515686986000
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Express accounts generally use Destination charges, rather than Direct charges. Why did you choose Express? And why did you choose Direct charges?
We were using Express because the whole idea of transferring payment from the platform to the target connected account seems matching what we want to achieve i.e. a donation feature. But it turns out the Stripe processing fee is charged by the platform, so we wanna see if direct charge is possible without changing the account type from Express to Standard.
As I saw in https://docs.stripe.com/connect/accounts, direct charge is support for Express though it's not recommended.
Right, so ... it's not recommended for many reasons, all of which make the integration harder.
whole idea of transferring payment from the platform to the target connected account seems matching what we want to achieve
This is true of all three kinds of Stripe Accounts.
Yes, that's also the reason we are trying to switch to the Standard instead. But out of curiosity, I want to know is that possible to set up payment intent with direct charge for Express account?
It is possible, yes. I also think that Express Accounts are a great pairing for donations like this, but you likely want to use destination charges instead of direct.
But the main point is we would like the connected account to be charged for the processing fee instead of the platform.
Cool. You can reduce the amount you transfer to them to cover that.
At the same time, it's likely worth talking to Support about what you need to know to make sure this is supportable by Stripe, as donation platforms have requirements from our side - however, that's not something our team deals with/knows about.
Such as this: https://docs.stripe.com/connect/destination-charges?platform=web&ui=stripe-hosted&fee-type=transfer-amount#settlement-merchant I don't know who has to be the settlement merchant in the case of donations, but Support would know.
From the pricing doc https://stripe.com/en-ca/pricing though, the amount of processing fee can be calculated in many ways depending on the payment method. That's why I don't want to hard-coded a portion to reduce. And I don't see there is a way to automatically calculate the processing fee in th backend?
This leads to direct charge being the only path to go.
Those are Destination charges.
If you want to do Direct Charges, you do them like this: https://docs.stripe.com/connect/direct-charges
Can you share a Request ID showing the issue?
Only connected accounts with the card_payments capability can be directly charged.
That account doesn't have the card_payments capability as, when it was created, you didn't include that in the request.
Ok, it looks like I must specify stripe account for paymentIntents.create
{...},
{
stripeAccount: accountId,
}
and also loadStripe() in the frontend in order for direct charges to work for Express accounts.
Though, if we want to use direct charge so that the connected account will be charged for processing fee, would it be better for us to just switch to Standard account?
Yes, that's how it works for direct charges. Standard accounts are a lot for someone just trying to raise some money - even Express is more than most folks would care about.
That's assuming a large number of your users only do a few fundraisers.
Got it. Thank you so much for the support.
Of course!