joshglazebrook

[mortal fjord]

Hello

Yeah that would be a good way to go.

If you are just using Invoices to collect payment methods then that would be the recommended route.

[native phoenix]

So I'm offering subscriptions (monthly), but for some customers I want to let them pay via invoice (for larger customers, etc). But I want to be able to charge a "setup fee" in those instances, so not necessarily just for collecting payment methods.

[mortal fjord]

How are you collecting payment methods for your Subscriptions currently?

[native phoenix]

But since I've been relying on the customer.subscription.updated/customer.subscription.created events, it breaks as subscriptions with send_Invoice start in the active state automatically

[mortal fjord]

Like what integration flow do you use?

[native phoenix]

Oh i'm using elements

[mortal fjord]

Ah okay, Payment Element?

[native phoenix]

Yep

select plan -> create subscription -> pass back payment intent for subscription -> collect via payment element. But for subscription plans that I want to invoice the customer, it's really just select plan -> create subscription

But in the case I want to also charge a "setup fee" my plan is to just make a one off invoice for that and wait for that invoice to be paid in addition to the customer.subscription.update/created event saying the sub is "active"

[mortal fjord]

Yep that works. You can either use a one-off Invoice or you could just create a PaymentIntent directly