#kipo.maniac
1 messages · Page 1 of 1 (latest)
Hello kipo.maniac, we'll be with you shortly! 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.
• https://discord.com/channels/841573134531821608/1162109100851732520, 6 days ago, 2 messages
Yeah, unfortunately the limitation you will run in to here is that Invoices create their own PaymentIntents (and can't be assosciated with existing PaymentIntents) but Invoices don't support our separate auth and capture flow
You may be able to do separate auth and capture with a payment intent, take payment as normal, then create an invoice that is paid off with a credit note though I am unsure what that would look like to the user on the actual invoice
We do also have receipts on our PaymentIntents, they look different from our Invoices but may be sufficient for your purposes https://stripe.com/docs/receipts
Hmm interesting. It looks like we can customize the 'description' field on receipts, but I'm assuming that's a simple text field. Would it be possible to display separate line items on that receipt?
Alternatively, do you think it would be a bad idea to attach metadata to the PaymentIntent so that we could generate our own receipts on our end?
Ah, unfortunately receipts can't have line items like that. And yes, attaching metadata and generating your own receipts is definitely a viable option https://stripe.com/docs/api/metadata
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.