barrelmaker_checkout-customization

[harsh quiver]

👋 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/1299392643335454761

📝 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.

• barrelmaker_code, 9 hours ago, 4 messages

[eager copper]

Hi there 👋 no, Checkout Sessions can't accomplish this. I don't think you can use manual capture with Subscriptions in general, but would need to double check that.

If you want to use Checkout Sessions, I do think a setup mode sesison would be the best approach. It would let you collect customer and payment method details to run your validation on before creating a Subscription for the Customer.

If you're open to using our Payment Element in your own UI, this flow would work well:
https://docs.stripe.com/payments/build-a-two-step-confirmation
(with a couple modifications to run Subscriptions through it rather than one-time payments)

[trail turtle]

Great thank you, I noticed that the embedded checkout when in setup mode is different than when the mode is subscription, where we cant see the products being purchased or a total about to be charged. Is there something I'm missing? If that's the case is there a way to inject a custom <button /> into the <EmbeddedCheckout /> component where I can run the custom validation and then complete the payment from within the embedded form?

Something like

<EmbeddedCheckout submitButton={(props) => <button onClick={
  // Run custom validation
  runValidations()

  // Complete payment
  props.submit()
} />} />

[eager copper]

Great thank you, I noticed that the embedded checkout when in setup mode is different than when the mode is subscription, where we cant see the products being purchased or a total about to be charged.
That's expected, because a Checkout Session with a mode of setup isn't processing a payment.

No, you can't inject your own code to run in a Checkout Session (yet), the flow I linked to using the Payment Element would be the best path for building a flow similar to that.

[trail turtle]

Cool cool, that "yet" is promising, is that something in the pipeline for a future version?

[eager copper]

Yup, we're working on a more robust checkout-like flow with more opportunities for plugging in extra logic.

[trail turtle]

awesome! do you happen to have a rough timeline for when that would be possible?

[eager copper]

That I don't, sorry

[trail turtle]

no problem, ty!