fynn

[gusty garnet]

hi! I'd suggest writing to https://support.stripe.com/?contact=true with feedback. Posting here anonymously won't change anything more than writing in.

But yes, PaymentIntents don't support LineItems. We had the Orders API beta for that last year which was in the direction of what you want, but that is not being continued.

Generally the recommendation would be to

• use Checkout
• use one off Invoices with the Hosted Invoice Page for payment
• integrate a form of line item display/use a third party in a custom payment form

I know it's not great and I completely understand the pain point but as mentioned, we attempted so solve for this with Orders but that did not work out, and there is a workaround via Checkout and Hosted Invoice Page.

[spark socket]

Hi @gusty garnet , thanks for your reply.

The problem is that I can not use the hosted checkout page since there is a legal requirement to have an additional 'opt-in' checkbox for additional consent 'right of withdrawal' this is needed when selling digital products.

By law, this checkbox has to be implemented on the final checkout page. Unfortunately there is no option to add 'custom' checkboxes to the hosted checkout page, just the default ones 'terms of use & privacy policy.

Another workaround would be to start off every payment cycle with an invoice.

1. create an invoice (defaults to DRAFT state)
2. finalize the invoice to get the paymentintent id generated.
3. pass the client secret for the just generated paymentintent id to the user so she / he can pay for the issued paymentintent

This will lead to further much bigger issues down the line, since for every rendered payment element we will have abandonded invoices which are legal documents when it comes to taxes and accounting.

[gusty garnet]

I can't comment on the legal requirement but adding support for custom inputs like that in Checkout is very likely to happen and I believe might even have a beta if you ask about it to our support team, but either way it is something we would want to do in the future.

it we will have abandoned invoices which are legal documents when it comes to taxes and accounting
I'm not aware of legal issues with our default recommended integration of Invoices for several years now, I'm just a developer but if you have feedback and opinions on that about how it interacts in certain jurisdictions, best to raise it to the support team so they can raise the points with the product team owning Invoices. I'm not saying that to be flippant, we do and have heard feedback about this sort of thing and make changes, like making PDFs from Invoices immutable to comply with certain requirements, a few years back.