#billibala
1 messages · Page 1 of 1 (latest)
👋 happy to help
Unfortunately that's not possible
the PaymentIntent won't be created until the customer pays
Bummer. But thank you for the clarification.
Do u know if using "invoice" will work?
When I create a new invoice, the returned invoice object does contain a ID-filled payment intent object.
I assume I can then pass payment intent ID to my own UI with Stripe Elements
yes one-off invoices can be used in that case
correct
@stiff latch just be aware that this workaround might leave you with an ungodly amount of finalized / unpaid invoices, depending on how many customers will not actually pay but leave your custom checkout page
Yeah... I am working on a consumer checkout flow. Definitely wanna avoid sending consumer an invoice and all these complciations.
i am facing exactly the same problem, unfortunately there is no solution.
i spent the past week implementing ALL available options / workarounds and numerous support sessions, unless we finally get support for 'line_items' 'invoice_creation' 'post-payment invoicing within the create payment intent api there is no solution.....
thus, preventing us from implementing the payment elements the way the´re supposed to work (custom checkout flow)
Gotcha... similar situation here. Spent a couple of days experimenting invoice and checkout session.
"Checkout Session" is definitely a good candidate for me. We already have a custom checkout flow using Stripe Elements in place for a year or so. But looking for ways to reduce my maintenance load + speed up development.
hmm, thats good to hear, in my case i can not use the checkout sessions since there is jurisdictions in my country regarding to "digital products" which requires me to have an additional chechbox on the final checkout page, which is aswell not possible..... could be all so simple
did you experiment with paymentintent metadata already?
Yup. We use "metadata" dictionary to store some IDs to help cross referencing data objects.
yeah, i mean everything is already there, it just seems it´s one or the other, intially it sounded like "payment elements can do everything as the checkout sessions" but in a more flexible / cusomizable way, which is obviusly not true...
took me a week to figure that out....
The amount of nuances among different payment flows are insane. I am amazed you "only" spent 1 week.
you are absolutely right, unfortunately these nuances are crucial for us to actually get this stuff going in a sane way of doing things
i looked into paypal again, so simple to just have 'line_items' etc.. but the UX is just not comparable to stripe, i really want to use stripe it just feels and looks nicer