Skip to main content

​
New Features

​
1. Subscription Payment Retries

Failed subscription renewal payments can now be retried automatically to recover revenue, with no integration work required. Enable it from Settings → Recovery, set a recovery window, and Dodo Payments retries the renewal on a smart schedule until it succeeds or the window closes.
Recovery Settings page with the Enable Payment Retries toggle on and a Recovery window (days) field
How it works
  1. A subscription renewal payment fails and the subscription moves to on_hold.
  2. If the decline is retryable (a soft decline such as insufficient funds or a temporary network error), the next attempt is scheduled automatically.
  3. Retries fire off-session on a back-off schedule, bounded by your recovery window.
  4. On the first successful retry, the subscription returns to active and the next billing date is advanced as normal.
Retry schedule Retries back off progressively, anchored to the time the failed invoice was created. Up to 8 attempts are made, as long as they fit inside your recovery window:
Only soft declines are retried (e.g. insufficient funds, generic decline, processing or network errors). Hard declines end the retry chain immediately, since retrying won’t change the outcome.
This complements the existing recovery tools — Subscription Dunning emails the customer to update their payment method, while Payment Retries silently re-attempts the existing one. They work well together. Learn more: Subscription Payment Retries | Subscription Dunning

​
2. Business Proration Settings

You can now set default upgrade & downgrade behavior once at the business level instead of passing proration parameters on every plan change. These defaults apply whenever a customer changes their plan from the customer portal, and you can override them per product collection.
Default upgrade & downgrade behavior settings in the dashboard with separate controls for upgrades, downgrades, and payment failure
Each direction (upgrade and downgrade) has two independent controls, plus a shared payment-failure policy: When the new plan starts (effective_at) How the customer is charged (proration_billing_mode) If the customer’s payment fails (on_payment_failure) Per-collection overrides Every product collection can override any of these defaults. Each field is independent — leave it on Inherit from business to follow the business default, or set an explicit value to override it for that collection only.
Upgrade & downgrade behavior override section on a product collection, with each field defaulting to 'Inherit from business'
Each setting resolves in this order:
A per-request value passed to the Change Plan API (proration_billing_mode, effective_at, on_payment_failure) always takes precedence over both the collection and business defaults. The new settings only change what happens when no explicit value is supplied — which is the case for all customer-portal plan changes.
Learn more: Subscription Upgrade & Downgrade | Product Collections

​
3. Collect Business Name for B2B Invoices

B2B customers can now have their legal business name rendered on the invoice instead of the buyer’s personal name. When a valid Tax ID is supplied at checkout, you can also collect the associated customer_business_name so the invoice reflects the purchasing entity.
Checkout page with the 'Purchasing as a business' toggle enabled, showing Business Name and Tax ID Number fields
When the customer selects Purchasing as a business at checkout, they’re prompted for both a Business Name and a Tax ID Number. The business name appears on the invoice only when all three conditions are met:
  1. The transaction is B2B (b2b = true)
  2. A tax_id is present
  3. A non-empty customer_business_name is supplied
Otherwise the customer’s personal name is used. Collecting it at checkout Set customer_business_name directly, and/or enable allow_customer_editing_business_name to let the customer enter or edit it on the checkout page alongside their Tax ID:
Where it applies
customer_business_name cannot be set without a tax_id. Sending a business name with no Tax ID is rejected. Clearing the tax_id also clears the business name, since the two are coupled on the invoice.
Surrounding whitespace is trimmed, and whitespace-only values are treated as an explicit clear — so stored data always matches what’s rendered on the invoice.
Learn more: B2B Payments | Invoice Management | Checkout Session

​
Bug Fixes & Improvements

  • Minor bug fixes and stability improvements across the platform.
Last modified on September 22, 2026