Skip to main content
Use Lenient when your customers are high-value businesses, when churn is expensive, and when you’d rather give extra time and flexibility than cut access at the first sign of payment trouble.

​
Who should use this

  • B2B SaaS with enterprise or mid-market customers
  • Products where a churned customer is hard to win back
  • Services where your customers have their own payment approval cycles (e.g., finance teams that batch payments weekly)
  • Early-stage products where keeping customers happy matters more than strict collection

​
Settings

Policy knobValueWhy
Upgrade strategyAt period endNo immediate charges — simplifies the customer experience
Downgrade strategyAt period endSame — everything changes at renewal
Grace period14 daysTwo weeks gives enterprise finance teams time to act
Dunning retries4 (days +1, +3, +7, +14)Standard schedule
Plan changes while past_dueAllow everythingDon’t block customers from adjusting their plan even if payment is pending
Billing modeAdvanceInvoice at start of period
Max debtNoneNo cap

​
Apply

curl -X POST https://api.useplinth.com/v1/tenant/apply-preset \
  -H "Authorization: Bearer sk_test_DOCS_SHARED_KEY" \
  -H "Content-Type: application/json" \
  -d '{"preset": "lenient"}'
With all plan changes deferred to period end, customers won’t be charged anything extra mid-cycle for upgrades. This reduces friction but means upgrades take effect at the next renewal — make sure your UI makes this clear.