#tujardinerobaby_code
rich spireBOT
đ 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/1326208444000374927
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
sudden zephyr
Hey there, taking a look at this
tropic dagger
Okay, if you need a deeper explanation let me know
sudden zephyr
The issue at the core is where the payment methods are being created by Stripe.js, platform vs connected account?
You need to specify the the connected account context to use when initializing Stripe.js with the stripeAccount option: https://docs.stripe.com/js/initializing#init_stripe_js-options-stripeAccount
tropic dagger
I know everything done from stripe-js is being created on the platform account. I just want to know if its possible to use stripe-js to access to connected account's resources
sudden zephyr
This will cause the Stripe.js-controlled API calls to happen using direct charge patterns, using your platform PK + stripe-account header to operate on the connected account.
sudden zephyr
I know everything done from stripe-js is being created on the platform account. ...
Yep, you can do this using the stripeAccount option at initialization, as i said