#zeedz_api
1 messages ¡ Page 1 of 1 (latest)
đ 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/1337320993361760336
đ 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.
- zeedz_api, 3 days ago, 5 messages
Just wondering if there's a way to remove this, and the implications of having the setupIntent as 'off_session'
Because I see the line "Use on_session if you intend to only reuse the payment method when the customer is in your checkout flow." a lot, but I'm not sure what it actually means to have a setupIntent as offSession
hello! to clarify, do you want to save the payment method on your platform first so that you can clone it to any other connected account to charge?
Yes that's correct. The reason why I came to that was so I could own the customers on my platform account. If there's a way to do this and have the customer in a designated checkout flow thats preferable, but if thats not possible I'm happy to ratify the payment myself after the user clicks that 'pay' button on my site
not sure if that made sense mb
sorta, I'm a bit confused over the second half of the explanation, but I think it's alright.
Are you using the Payment Element?
(1) So I wanted to use just the normal checkout session and the stripe-hosted checkout page, but I don't think that's possible with connect + direct charges + owning the customers on the platform account. So I switched tact and created the setupIntent and am happy to collect the method first then charge rather than doing it all at once.
(2) Yes, I'm using the React library
<Elements
stripe={stripePromise}
options={{
clientSecret: paymentIntentSecret,
}}
>
<form onSubmit={handleSubmit}>
<PaymentElement />
<Button className='w-full mt-auto' disabled={!stripe}>
Submit
</Button>
</form>
</Elements>
or was that not the question... sorry theres just so much terminology haha
yep, it was what i was asking. Gimme a few minutes to test something out
So you can remove that text by disabling https://docs.stripe.com/js/elements_object/create_payment_element#payment_element_create-options-terms