#marve_api
charred sirenBOT
👋 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/1351239928549478450
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
astral ridge
Hi 👋
No I don't think you can use Direct Charges in that scenario because you do not provide any Stripe dashboard access.
errant ibex
if we use embedded components? does that not work?
astral ridge
Have you tried it in test mode?
errant ibex
Good point, we haven't actually. Will try now. Just thought you might know before we do
But yes, will go ahead an try
Do you know if we can use destination charges with on_behalf_of if we're based in the US and our connect accounts are outside it? Yesterday we were told no, today maybe
astral ridge
I think the problem there you run into is the problem with Cross Border Payouts
errant ibex
Yes, exactly. Because of this we wanted to try direct charges with custom accounts, but everywhere it says it is not recommended. Is it possible but not recommended.
Then came across controllers. Can we really use whatever combination we want? Like losses_payments: stripe, fees_payer: application_custom, requirement_collection: stripe, dashboard_type: none? Support on the web has never mentioned
astral ridge
Some combinations are not compatible and unfortunately, we do a bad job at documenting which those are.
You just get error messages from the API when you try to create the Account
errant ibex
Okay perfect, will give it a try.
You can close this, will come back if any issues
Actually
Do you know who else I can ask about the combination docs? Stripe support maybe and then can escalate?
astral ridge
Which docs are you referring to when you say "the combination docs"?
charred sirenBOT
astral ridge
We can file a ticket to make it more obvious which combinations are and are not supported.
errant ibex
That would be great, thanks.
Would you also be able to file a ticekt to clarify the cross-border-payouts page?
We have been told numerous times that as we are based in the US, we won't be able to use on_behalf_of for destination charges if our connect accounts are based outside the US
After constant back and forth, we are indeed able to. I think stripe support is mixing up payouts with connect account balances maybe?