#linqisnice_unexpected
harsh valeBOT
👋 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/1267781546551803934
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
glad pecan
👋 happy to help
would you mind sharing the request ID of the Checkout Session? https://support.stripe.com/questions/finding-the-id-for-an-api-request
grizzled shuttle
I'll see if I can access it, not sure I can immediately access the Stripe account, sec!
yes ok im in
harsh valeBOT
grizzled shuttle
where do i find the checkout session id?
here's the payment id py_1Pez4uQHwUK2JlBYB6ECQqNU
I can probably check the logs for the checkout session wait
cs_live_b1a06YPSMHPSdSriJGcKYXmnp8IUFltYVm7Nx8B1gqM8zyMak4ohUrT7SL
this might be it?
storm spade
yes. Well that is a Detination Charge so it uses the platform branding. If you want it to use the connected account branding, use the on_behalf_of parameter.
https://docs.stripe.com/connect/destination-charges?platform=web&ui=stripe-hosted&destination-or-on-behalf-of=on-behalf-of
grizzled shuttle
I think I was told not ot use on behalf of with standard accounts (or maybe it was destination charge). Is that correct? Are there any other implications of using on behalf of?
storm spade
yes it's not normal to use Destination with Standard because it means your platform is liable for refunds/chargebacks but you have limited ability to recoup losses/control the Standard accounts. But it's possible/allowed if you are familiar with doing it
grizzled shuttle
Ok, is there more I can read on that specific combination or why that is the case with on behalf of?
There is no other way to achieve that then?
I'm so confused honestly
i feel like I've been told multiple times the exact combination of account type and charge type and ultimately that was destination charge with standard
but ur suggesting I shouldn't really be doing that?
and if I didnt use destination charge, I wouldn't need to use on behalf of?
because ur answer seems to imply that the combination of destination and standard is the issue, nothing to do with on behlaf of
storm spade
the reason the branding is your platform is because you are using Destination. Doesn't matter what account type
destination -> platform branding
direct -> connected account branding
destination + on_behalf_of -> connected account branding
grizzled shuttle
ok, i'm 99% sure i've been told here twice or so that I should be using destination with standard. So what gives? and why does destination cause this "issue"?
storm spade
destination -> platform liability for refunds/chargebacks
direct -> connected account liability for refunds/chargebacks
destination + on_behalf_of -> platform liability for refunds/chargebacks
and why does destination cause this "issue"?
becaues the use case of Destination is platforms like e.g. Uber where the customer is paying/interacting with a platform, not the "driver" etc who jsut recieves some of the funds later
grizzled shuttle
Ah ok. Maybe our business model wasn't clear then...
Basically, we're a property manager. Property owners use our platform to handle all things their property, but can also integrate a checkout session (developed by us) on their website.
and send payment links with emails
so i guess technically there's a direct transaction between the customer and the property owner
but maybe there was a misunderstanding when i was told to use destination
storm spade
you're free to use whatever charge flow makes sense to you, the main thing is to understand the differences and implications