#michael_58664_48271
1 messages · Page 1 of 1 (latest)
hello! that's expected behaviour currently, unless the true value of the service provided is $0 e.g. for a trial, the Invoice amount due shouldn't be $0
usually the invoice is raised to get payment from the customer, a receipt is issued after receiving the payment from the customer.
We (Stripe) built a post-payment invoice feature because there are some businesses that require an invoice to adhere to regulatory requirements in the countries that they're in
Thanks for the feedback Alex. That is exactly what I need. Is there documentation available for integration?
you mean the post payment invoice? it's only available for Checkout and Payment Links currently and there's an extra cost for using it : https://support.stripe.com/questions/pricing-for-post-payment-invoices-for-one-time-purchases-via-checkout-and-payment-links
Find help and support for Stripe. Our support site provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
can you explain a bit on what why you're setting your Invoice to PaidOutOfBand? I would have thought that you would use the Invoice to collect payment
Customer captures card details to pay for item using PaymentElement in react (checkout form). If payment successful, I would not need to collect payment through invoice. I would think I can set the invoice to Paid at this point using PaidOutOfBand. If I don't do this, the invoice sits in draft state, and After an hour attempt to collect payment and fails. I then get an error that payment method is required. So It might be something I am doing wrong?
I think what you should try instead is to create an Invoice, then use the underlying PaymentIntent (for the Invoice) to collect payment using the Payment Element
That makes sense! I will give that a shot. Thank you for your assistance 👍
Hi Alex, just some feedback. Your idea worked perfectly! Just for anyone who sees this and has the same issue. Once again, thank you!!