#adrklu_best-practices
trim forgeBOT
👋 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/1369234767215591467
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
quiet owl
👋 happy to help
in order to help you out, you should start by looking at what type of charges better suits your use case https://docs.stripe.com/connect/charges
once we figure this out, we could that find the best onboarding configuration and go through the integration steps
rigid oyster
Appreciate that, I guess my question is, would direct charges appear only on the relevant account, whereas destination charges appear on both, with the funds going to the destination, or the platform account if not specified?
quiet owl
no in both cases you would see the charges on your platform account
actually not really
in the case of direct charges you would see that their was an application fee that is tied to a Direct Charge
you can see what objects are created where exactly here https://docs.stripe.com/connect/direct-charges?platform=web&ui=stripe-hosted#flow-of-funds-with-fees for the Direct Charge
and here https://docs.stripe.com/connect/destination-charges?platform=web&ui=stripe-hosted#flow-of-funds-app-fee for the Destination Charge
again don't worry about this yet
just try to see which type of charge suits your use case by reading the comparison table in the first link I shared
rigid oyster
Thats the difficult part, as I'm really unsure what suits us - essentially we are acting as both accounts, we wont be charging application fees or anything of that sort since the funds will flow into the same payout destination in the end.
The whole point here is to change the branding of the hosted checkout session and sent invoice emails, and have a place to do reporting on for the specific transactions being put through this newly branded connect account.
quiet owl
in that case why go the connect route?
why not just create a new account?
and you can add it to your org https://docs.stripe.com/get-started/account/orgs
rigid oyster
As this will be a recurring theme, we want it all to be managed from one API key
quiet owl
how are you deploying this?
on 2 different websites?
the API key by itself isn't really a big issue
rigid oyster
Yes separate sites
quiet owl
then you can easily set environment variables
and use that to store the secret and publishable keys
rigid oyster
i think im confusing myself and you haha, essentially we have 2 lead gen sites, but the underlying site (a job management platform) is the same - the server calling this api will be the same but we just want to rotate branding based on some business logic saying where this job came from.
we also have incredibly high direct debit limits as the products are expensive, the reason for connect is it nicely inherits all those account limits
quiet owl
we also have incredibly high direct debit limits as the products are expensive, the reason for connect is it nicely inherits all those account limits
that's not an issue, and not necessarily true
do you have an Account Executive at Stripe? or a direct contact?
rigid oyster
We had one over a year ago, but they left the company, since then we haven't had one.
quiet owl
ok what I suggest to do is the following
rigid oyster
Thank you for your patience so far
quiet owl
contact https://support.stripe.com/?contact=true and ask them about whether (from a pricing perspective) using connect is better than creating a new account under an organization and whether you would inherit the debit limits that you already have if you create a new account under the organization
I really think that the org route is better suited for you
rigid oyster
as in, org route and then flipping API keys when necessary?
quiet owl
but I want you to see this from all angles before you decide on which approach to use
quiet owl
as in, org route and then flipping API keys when necessary?
yes exactly
the org would give you the ability to centralize reporting as well
so I'm not sure about the pricing
rigid oyster
I assume it'd also let me filter by acct.
quiet owl
that's why I think it's better to speak to someone at the support level
quiet owl
I assume it'd also let me filter by acct.
exactly
rigid oyster
Much appreciated tarzan
I'll reach out to them, did you want me to dm you the outcome just for your knowledge after the fact?
quiet owl
you can come back to this thread and then we can discuss integration steps if needed