fwang

[peak lava]

Could be a number of things. Recommend reading this list of limitations. Likely it's one of those things: https://stripe.com/docs/customer-management#customer-portal-limitations

[finite siren]

reading..

btw.. fyi.. the product has a metered pricing model with 2 tiers

[peak lava]

Yeah that would be why

Usage based billing is one of the limitations in that list

[finite siren]

ah i see... is there a no-code way to subscribe user to the product?

I saw in the docs that a Payment Link can also create a subscription for a user, does that work for usage based pricing?

[peak lava]

Just to clarify, the customer portal isn't for enabling users to create new subscriptions

It's to manage existing ones

But you can use payment links for that: https://stripe.com/docs/billing/subscriptions/usage-based

[finite siren]

Oh I see... giving it a read

so at the high level, we'd redirect the user to the Payment Link to subscribe, and then we'd redirect the user to the Customer Portal to manage their subscription.

does that sound right?

[peak lava]

Correct

But keep in mind the customer portal limitations I linked above

[finite siren]

got it.. thanks @peak lava!

[peak lava]

No problem

[finite siren]

@peak lava had a look at the Payment Links. Is it possible to create a link for existing user?

i might be wrong... but the docs seems to suggest that a new Customer and a new Subscription object are returned on success

[peak lava]

Yeah they're really for new customers

If you need to manage existing customers, then it might make more sense to use Checkout instead

It's a low-code integration, but you can explicitly pass customer id

See: https://stripe.com/docs/billing/subscriptions/build-subscriptions?ui=checkout