#scubastereo
1 messages · Page 1 of 1 (latest)
Yes, you will need to also provide the ID of the connected account to the stripeAccount parameter when initializing Stripe.js https://stripe.com/docs/js/initializing#init_stripe_js-options-stripeAccount
The direct charges doc you are looking at should likely has an example of this in its snippets if you ctrl+f for "stripeAccount"
Thanks a lot for that! I was worried this wasn't possible. I'll try it out
Looks like that works! I have another question related to the flow of things in the quick start detailed here: https://stripe.com/docs/payments/quickstart
Would it be better to ask in dev-help for a new thread?
Keep asking here please, asking again in dev-help is usually for when you don't have an active thread
Okay thanks again. The guide has you immdiately create a PaymentIntent so that you can create a payment element. The problem is that my user won't have entered Shipping details by that point and I won't have a shipping or a tax amount yet. Is there any guidance to updating the PaymentIntent/capturing a different amount later or am I simply going to have to wait until the user does enough steps before creating the payment element?
You can update PaymentIntents and their amounts, so you could disable the button that submits your form until after the shipping and tax have been calculated (might also want to have server side logic to check those just in case).
We also do have a beta that would allow you to create payment intents later if you are interested https://stripe.com/docs/payments/defer-intent-creation-confirm-server