#goup_api
sage valveBOT
đź‘‹ 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/1324742799815348290
đź“ť Have more to share? Add more details, code, screenshots, videos, etc. below.
plain pilot
đź‘‹ happy to help
formal finch
Hi!
plain pilot
you no longer need to use the Standard, Express and Custom accounts
we have now more granular configurations of Accounts
but I don't think you will have the choice of not showing the full Dashboard
for Direct Charges you need to give access to the full dashboard
formal finch
Yes we can use controllers, I haven't tried this but it seems that a configuration like
losses.payment: stripe
fees.payer: account
requirement_collection: stripe
dashboard_type: none (or express if possible)
would correspond to our needs
formal finch
for Direct Charges you need to give access to the full dashboard
is there no way around it ? because if not then it means you cannot create card imprints without using Standard accounts (or something alike)
well at least not possible without letting the funds transit through the platform, but that's a responsibility our client does not want
plain pilot
Yes we can use controllers, I haven't tried this but it seems that a configurati...
that's not possible
plain pilot
is there no way around it ? because if not then it means you cannot create card ...
unfortunately there isn't
formal finch
that's not possible
🤔 how come ? reading the doc it does seem like a viable configuration, it's just that the dashboard type would have to be none for compatibility with the other fields
formal finch
for Direct Charges you need to give access to the full dashboard
wait that's weird, I'm pretty sure I remember creating a direct charge with checkout towards an express account
plain pilot
this is not recommended at all
formal finch
sorry which part ?
plain pilot
to use Direct Charges with Express Accounts
we use to give that access for select merchants in the past but we no longer accept that
sage valveBOT
formal finch
If DIrect charges do end up working with the configuration I gave above or with Express accounts, what would be the risks ?
Because it is a huge issue if the end receiver of the payment has full access to the dashboard, as they would be able to manually capture the funds held within the card imprint
shy juniper
Hi taking over here
formal finch
Good afternoon!
shy juniper
They technically work, but that pattern is highly discouraged. It can cause issues. Some of which are:
Addressing disputes becomes increasingly difficult through the dashboard.
Express account are unable to address disputes through their own limited dashboard, so it has to be done by the Platform. As a business scales it is unreasonable and time-consuming to check every single account to find the right charge.
Platforms have to cover for negative balances of their Express/Custom accounts.
Refunds for Direct Charges come from the connected account’s balance and Stripe fees (which are paid by the connected account for Direct Charges) are not returned, making it more likely for a connected account to have a negative balance. Platforms are responsible for the negative balances of their Express/Custom accounts, so whenever there’s a negative balance we have to hold a reserve from the Platform’s available balance.
These charges aren’t compatible with Radar, which is a major blocker for European accounts.
A Platform’s Radar rules only apply to their own charges, not charges directly created on their connected accounts. This is a problem because Direct Charges are subject to the connected account’s rules but Express/Custom accounts cannot actually set their own Radar rules.
Platforms can’t easily get any metrics (like decline and conversion rates) that represent payments across all their connected accounts.
Because this information is distributed across many accounts, it takes more work to gather all the data. Metrics are much easier to calculate and track when the Platform can access the information in one centralized place.
Email Receipt customization is limited.
Email receipts that are sent for Direct Charges reflect the settings of the connected account. As a result, a Platform can’t make changes like opting to include a support phone number in the receipt since this setting is not available for connected accounts.
It can be difficult to predict expected fee behavior.
formal finch
For disputes I don't think it would be much of an issue in our use case, as we would only trigger payment capture when we are 100% sure that the service was provided and there was no issue. Therefore we would not have to deal with refunds which I believe is what the main concern is in disputes (please correct me if I'm wrong)
If instead of creating express/custom accounts, I created accounts with the configuration I gave above, negative balances would not be an issue anymore right ?
shy juniper
Not sure exactly
Also above is not an exhuastive list
I just want to be clear that we heavily discourage this pattern
It can cause issues
But ultimately it's your decision if you want to proceed
formal finch
Okay
is Radar mandatory ? I'm very new to stripe and I think this is the first time I read about it
Our users would be mostly european I believe
shy juniper
The above is referring to custom radar rules which is not mandatory
That's something you'd pay extra for
formal finch
Okay thanks
And about fee behavior, are we referring to fees that stripe would collect for using those services with the options I mentioned ?
shy juniper
Fee behavior in general we don't know much about in here
That's something you'd need to ask the support team for more info on
We just help with api questions in here
We really don't know much about fees in here or even account configurations
formal finch
Okay okay, so would it be better to just contact support and discuss with them everything I've mentioned so far ?
shy juniper
They'd know more about fees
But they may not know as much as us about the technical part of things
This discord is for asking api questions. We know those things the best
But if you have questions about fees (ie which account pays which fee and how much) then support would know best