Description
Recurring Payments and Dunning for Perfex CRM
Recurring Payments and Dunning for Perfex CRM is the automated sequence of retries and emails that chases a payment that failed. It is the part no option inside Perfex covers today – see the table below – and it is where the money is.
Stripe, in its own engineering post on Smart Retries, writes: “Twenty-five percent of lapsed subscriptions are purely due to payment failures.” Recurly’s published churn benchmarks put the overall churn rate at 3.60%, of which 1.25 points are involuntary – revenue lost to a card that failed rather than to a customer who decided to leave – and Paddle puts involuntary churn at 20-40% of overall churn. That share is what a dunning engine exists to win back.
Features
- Two modes, both usable on the same install. Auto-charge a recurring invoice – Perfex keeps generating its recurring invoices exactly as it does today, with your numbering and your items, and the module collects each one the moment it appears. Subscription plan – the module owns the clock, builds the period’s invoice from a plan you defined, then charges it.
- One switch for everything. Turn on Auto-charge every recurring invoice and any customer with a saved default payment method is collected automatically, with no subscription to create by hand.
- Charges at a sensible hour. Collections are placed at a configurable local hour (2 a.m. by default) in the subscription’s own timezone, which is what card issuers expect from a
subscription merchant. - Respects part payments. A retry collects what is still owed, never the original amount again.
- Charge now, from the subscription screen, behind its own staff permission – with an honest message when the engine refuses rather than a claim that money moved.
- The invoice is never edited. The document exists and carries its final number before any money is requested, and a decline never modifies it. That immutability is what makes retries safe.
