Payment state per invoice
Every invoice carries its payment state — paid, failed, recovering — so nothing is inferred from guesswork.
- Failure states tracked per invoice
- Balances visible per customer
- Payment history alongside subscription state
Failed payments are a process, not a surprise
Cards expire, charges decline, invoices go past due. Floatless tracks every failed payment against customer billing state so recovery is a workflow — not a support fire.
Free during beta. No credit card required.
Floatless workspace
Billing review
PlansMonthly, annual, seat-based, usage-based
SubscriptionsActive, paused, upgraded, canceled
InvoicesDrafts, review, posted, downloaded
UsageMetered events and billable summaries
What is dunning management?
Dunning management is the disciplined process of recovering failed recurring payments: detecting the failure, retrying the charge on a schedule, telling the customer clearly and early, and deciding when the subscription should pause or cancel. Good dunning recovers revenue quietly — most failed payments are expired cards, not lost customers — and bad dunning churns users over fixable payment issues. The measure of a dunning process is recovered revenue plus how few customers it unnecessarily upset.
Retry with intent
Recovery attempts run against billing state, on a timeline an operator can see and explain.
- Retry attempts recorded per payment
- Recovery timeline per customer
- Failed, retried, recovered visible at a glance
Communication that keeps customers
Most failed payments are expired cards. Clear, early customer-facing communication recovers them without embarrassment.
- Customer portal for billing self-service
- Payment-method update without involving support
- Plain-language state instead of silent cancellations
Decide, do not drift
Pause, retry, or cancel is an explicit operator decision on subscription state — recorded in the audit trail.
- Subscription state changes are deliberate
- Audit trail of who changed what and when
- Dunning compliance workflows available for regulated flows
Recovery you can measure
Analytics show what failed, what recovered, and what it means for the month.
- Failed-payment and recovery views
- Revenue intelligence alongside dunning state
- Export via API for downstream reporting
Webhooks for your product
Let your product react — block a feature, send your own email — using billing lifecycle events.
- Webhook events for payment state changes
- Signed payloads with replay
- Stable event names under /api/public/v1
Positioning
How Floatless fits
| Option | Works well for | Floatless position |
|---|---|---|
| Doing nothing | Nothing to set up | Every expired card becomes churn |
| Manual chasing | Personal touch | Does not survive volume or vacations |
| Enterprise dunning suites | Large B2B revenue teams | Priced and shaped for companies with a collections function |
| Floatless | Small teams with recurring revenue | Dunning as part of the billing workspace, visible to operators, connected to the API |
See if Floatless fits your billing workflow.
Create a free beta workspace and test the workflow with your own plans, customers, and usage.
FAQ
Common questions
Does Floatless send dunning emails for me?+
Floatless tracks failed-payment state and retries, and gives you a customer portal for payment-method updates. Product-specific messaging can be driven through webhooks.
When should a subscription be canceled for non-payment?+
That stays an explicit operator decision. Floatless keeps the subscription state, retry history, and audit trail so the call is informed rather than automatic.
Can customers fix their own failed payment?+
Yes. The customer portal supports payment-method updates and viewing invoice state without a support ticket.
Do retries run automatically?+
Recovery attempts are tracked against payment state in the workspace; how aggressively to retry stays under your control.
Is dunning included during the beta?+
Yes. Dunning and payment recovery workflows are part of the workspace, free during beta.
Further reading