#jast26

1 messages ยท Page 1 of 1 (latest)

sonic otterBOT
toxic rune
#

Hi there!

#

So you are already accepting payments, and now want to have invoices for these payments?

terse cobalt
#

well actually we are spinning up a new product, so we have a blank slate and a test account for now, but yes that would be the idea

#

we have got payments working with payment intents and stripe web elements

toxic rune
#

How do you want users to pay for the Invoices? On your website, in a Checkout Session, by email?

terse cobalt
#

checkout session with stripe web elements, ideally they should receive an email afterwards with an invoice, which is just a receipt on steroids for us. We do not have plans to integrate subscriptions or invoices with payment links at the moment

toxic rune
terse cobalt
#

would this work with web Payment Element as well?

tender plover
#

Hi there ๐Ÿ‘‹ jumping in as my teammate needs to step away. No, the parameter being used in the sample code shown there is exclusive to Checkout Session objects, you can't use it with a Payment Element integration.

To generate Invoices with a Payment Element integration, you would need to generate the Invoice first.

terse cobalt
#

hey Toby, no worries. Given we are so early that we are not even at MVP, shall we switch from Web Elements to Checkout? seems more powerful in general

tender plover
#

If it better fits your needs, that's a reasonable switch to make.

terse cobalt
#

We are just a bit confused on the overlap of the two products, i do not think we get the use cases right, could you recap? last stripe integration we built was in 2019 ๐Ÿ˜…

#

these statements are in a bit of contrast with each other

https://support.stripe.com/questions/payment-element-faq?locale=en-GB#:~:text=Payment Element allows you to,options (color%2Flogo).

Stripe Checkout uses Checkout Sessions to operate and does not use PaymentIntent/SetupIntent. It is designed for simpler use cases, i.e. single step flow with less need for control/customisation/branding. Stripe Checkout offers and collects more info, including delivery address collection, and shows a product list/order total and submit button, which the Payment Element does not.

tender plover
#

Is there something specific you're not clear on that I can help with? In general, both are for accepting payments. Checkout Sessions offer more prebuilt functionality, at the cost of losing the ability to control the UI that your customers see when paying. A Payment Element integration allows you to input our payment form into your site, allowing you to provide a more branded experience, but it requires that you build or implement more logic to accomplish the flow you want.

terse cobalt
tender plover
#

Fees aren't something we're as familiar with in this forum, we focus on helping developers work with our API and SDKs. I would recommend reaching out to our Support team to double check what fees will be charged, as they're more familiar with that than we are:
https://support.stripe.com/?contact=true
As far as I know, Invoicing does come with additional fees, but so does the feature to have Checkout Sessions generate Invoices.

This is our example of what an Invoicing integration looks like:
https://stripe.com/docs/invoicing/integration/quickstart
It mostly focuses on creating the Invoice, so you would still need to implement a way to accept payment. There are options on how to do that though. You can direct your customer to the Hosted Invoice Page url that is genreated, or you can use the Invoice's Payment Intent to initialize the Payment Element.

terse cobalt
#

ok toby many thanks, you have been extremely helpful, i will have a look. I also have another question about payment elements, should i ask it in this thread or open another?

tender plover
#

You can ask it here

terse cobalt
#

is it possible to prefill a web Elements payment with a saved / default paymentMethod?

tender plover
#

No, that's not supported.

terse cobalt
#

ok, many thanks have a good day