#yassiney-invoice-paymentintent
1 messages · Page 1 of 1 (latest)
Hey @iron seal as that as I know yes we do
I really don't get why you use Invoicing though based on what you said
how can we process a payment of multiple items (toy1:5$, toy2:10$, and subscription:10$/mo)?
invoices was the only solution we found really
Well Invoices never support that either
Are you doing real subscriptions and using our Billing product and our Subscriptions API?
subscriptions API
- we add invoice items (of one time charges) using stripe.InvoiceItemParams.
- if there is a subscription, we call stripe.Subscriptions.New() to create it, which also auto-adds all previously create invoice items to the invoice and finalizes it.
- if there is no subscription we just call stripe.Invoices.New() to create one and finalize it manually.
we have been doing this for years without problems but recently Stripe decided to start charging our connect users for that!
(of course, will love to have a different solution, because the above takes 20s+ to process a single payment due to the multiple API calls to Stripe.)
gotcha
so for subs you should use https://stripe.com/docs/api/subscriptions/create#create_subscription-add_invoice_items would make your integration faster/easier
for the rest, why don't you just do a PaymentIntent for the sum in that case?
interesting
is that a new option for subscriptions?
and does that go through invoices API?
Subscriptions creates Invoices, so yes no change there. And it's new-ish it shipped last year
ah makes sense,
but that means our connect users will be charged the invoicing fees on top of payment fees?
Invoicing and Billing are separate products. If you use Billing you pay the Billing fee. The Invoices created by Subscriptions are not affected by Invoicing's pricing.
If you explicitly go and create your own invoice (what your example #3 does above) then yes you pay the Invoicing fee