halvehenk

[vast ingot]

Can you share an example

[karmic panther]

When customer uses the customer portal to increase the quantity on his subscription, his payment goes to pending and the subscription status becomes "past_due"

[vast ingot]

Right, but can you share the ID of that Invoice (in_xxx)

[karmic panther]

I Sent it in DM

[vast ingot]

I don't accept DMs. Here is fine

[karmic panther]

in_1Nt9MlE0K7TdL1FyKqXW6seo

[vast ingot]

Taking a look!

[vast ingot]

Still checking

Ok, seems that this is expected albeit a little unintuitive. Updates via the billing portal, such as this one (https://dashboard.stripe.com/logs/req_xkLtEQGc4zRgdX) which triggered the new invoice/payment, default to payment_behavior: 'incomplete'. This is not configurable. As per the API reference:

Use allow_incomplete to transition the subscription to status=past_due if a payment is required but cannot be paid

In this case, as it was a SEPA payment method, we treat the initial payment as unpaid whislt it's in processing state.

[karmic panther]

Is there any setting we can change in or billing portal that will prevent the state going past_due?

[vast ingot]

There is not unfortunately. This is just an unfortunate side effect of async PMs

[karmic panther]

Is there an alternative to the billing portal we can use to let clients be able to update their quantity that does not have this sideeffect?

[vast ingot]

You'd need to build your own UI where you can pass the payment_behavior param with your update call

Portal doesn't support that today. It's valid feedback I'll share internally

[karmic panther]

Ok, thanks for the help. Will look into it. Start by not allowing customers to update quantity through portal.

Is there an issue or ticket i can subscribe to if this could be implemented in the billing portal?