Most buyers focus on MRR and churn, ignoring the revenue leakage hidden in failed payments. Here is how to audit payment infrastructure to protect your valuation.
Deal Alert AI is reader-supported. We earn commissions from affiliate links at no cost to you.
This post is based on a video from our Deal Alert AI YouTube channel. Watch the original or read the full breakdown below.
In the world of online business acquisitions, buyers are often so captivated by the gloss of monthly recurring revenue (MRR) that they overlook the cracks in the foundation. We see it constantly at Deal Alert AI: buyers are quoted a price based on revenue multiples, but they rarely stress-test the actual collection infrastructure. The result is a purchase where the reported MRR looks healthy on paper, but the cash flow in the bank account significantly lags behind due to "soft churn." Soft churn occurs when a subscription lapses not because the user quit, but because their credit card failed to process. This is not a technical error; it is a business leak that erodes your return on investment (ROI) every single month.
To understand the magnitude of this risk, you must distinguish between hard churn and soft churn. Hard churn is a deliberate departure by the customer. Soft churn is an accidental failure in the billing cycle. Industry benchmarks suggest that for many SaaS companies, 5% to 10% of involuntary churn is attributable to failed payments. If you are acquiring a company with $100,000 in MRR, that percentage represents $5,000 to $10,000 in lost revenue every month. Over a 12-month holding period, that is $60,000 to $120,000 gone, lost to a problem that is often entirely fixable. If you do not account for this in your due diligence, you are effectively paying more for the business than it is worth.
The core issue is that most SaaS sellers do not have sophisticated dunning processes in place. Dunning is the series of automated emails or messages sent to customers when a payment fails. If a company relies on its payment processor's default, basic email notification, it is leaving money on the table. Modern, high-performing SaaS companies use dynamic, multi-step dunning flows that update expired cards, send multiple reminders with varying urgency, and offer alternative payment methods. The absence of these tools is a red flag that the seller has never truly optimized the revenue retention engine. As a buyer, you need to view the payment failure rate not just as a technical metric, but as a direct indicator of operational negligence or opportunity for quick wins.
We scan Empire Flippers, Flippa, Acquire.com and Quiet Light daily — scoring every listing. Start free.
Before you even look at the payment processor, you must understand the specific metrics that define involuntary churn. The most critical metric is the "Failed Payment Rate." This is the percentage of total recurring transactions that failed on the first attempt. A healthy SaaS company should aim for a rate below 5%. If the seller presents a rate above 7%, you should be alarmed. Another key metric is the "Recovered Charge Rate," which measures how many failed payments were successfully recovered through the dunning process. A high recovered charge rate indicates a robust dunning system, while a low rate suggests that even when customers want to stay, the friction is too high.
It is also crucial to look at the "Net Revenue Retention" (NRR) in the context of payment failures. NRR includes expansion revenue, contraction, and churn. If a company’s NRR is near 100%, but their gross churn is high, it might be masking a payment issue. You need to ask for the granular data on why customers are being cancelled. If a significant portion of the churn reason is tagged as "Card Declined" or "Payment Failed," you are looking at a software problem, not a product problem. This distinction is vital because a software problem can often be fixed in days, whereas a product problem can take months or years and may be unsolvable.
Furthermore, consider the "Time to Recover." This metric tracks how many days it takes from the initial payment failure to the successful retry or customer intervention. Best-in-class companies recover payments within 24 to 48 hours of the failure. If the data shows that it takes 7 to 14 days to recover a payment, the customer is likely to have already forgotten about the subscription or found an alternative solution. In these cases, the dunning process is too slow to be effective. You must analyze this timeline to determine if the current infrastructure is capable of supporting the scale of the business you are buying.
The choice of payment gateway is a major determinant of payment failure rates. Not all gateways are created equal. Some providers have higher approval rates for certain card types, regions, or transaction sizes. During due diligence, you must identify which processor the business is using—Stripe, Braintree, PayPal, or a regional processor. Each has a different architecture for handling retries and fraud checks. For example, Stripe’s built-in dunning is relatively basic compared to specialized third-party tools. If the seller is using a basic setup, the potential for improvement is high, but the work required to implement it is also high.
You must also investigate the fraud rejection rate. It is common for newer SaaS businesses to have overly aggressive fraud filters that block legitimate customers. This is known as "false positives." If the fraud rejection rate is higher than 2%, it is likely that you are losing good customers. As a buyer, you can ask for a sample of payments that were flagged as fraud and manually reviewed by the seller. If you find that valid charges were blocked, this is a leakage point you can address immediately after acquisition. It is a low-cost, high-impact fix that can boost revenue without any marketing spend.
Additionally, the integration method matters. Is the business using hosted checkout, where the customer is redirected to the gateway’s site, or embedded checkout, where the payment form is on the business’s domain? Embedded checkouts generally have higher conversion rates and better retention because they keep the user within the experience and allow for more granular tracking of where the failure occurred. If the business uses a legacy, outdated integration that does not support modern tokens or the latest security standards (like 3D Secure 2), you are facing a technical debt. This technical debt will manifest as higher failure rates and higher customer support load, as customers call in confused about why their cards are being declined.
The dunning process is the heartbeat of payment retention. A weak dunning process is the single biggest reason for high involuntary churn. When you audit a target SaaS business, you need to map out the exact sequence of events that occurs after a card is declined. A robust system should immediately detect the failure and attempt a retry after a short delay. If that fails, it should send an email with a link to update the card. This email should be sent immediately, not the next day. If the customer does not update the card, the system should send follow-up emails at regular intervals, increasing in frequency and urgency.
Look for the inclusion of "Card Update Links" in the dunning emails. These are links that take the user directly to a secure page where they can enter a new card number without having to log in or navigate through the account dashboard. This reduces friction significantly. If the emails do not contain these links, or if the user has to go through a complex payment flow to update the card, the drop-off rate will be high. You must test this flow yourself during due diligence. Create a test account, use a card that is set to fail after the first charge, and see how the system responds. Does it send an email? How soon? Is the link working? This simple test can reveal serious operational gaps.
Also, check for "Smart Dunning" features. Advanced SaaS platforms use machine learning to predict when a card will fail or to optimize the timing of retries. For instance, if a customer consistently uses a card that has a low limit, the system might attempt to charge on a different day or send a notification to update the card before the limit is reached. The absence of such intelligent features is not a deal-breaker, but it should be factored into your post-acquisition roadmap. You will need to budget for either upgrading to a better tool or hiring a developer to build these features. This cost must be subtracted from the potential revenue increase you expect to gain from fixing the payment failures.
It is easy to dismiss payment failures as a minor annoyance, but the financial impact is substantial and quantifiable. To calculate the true value of fixing payment issues, you need to project the revenue loss. Start with the total MRR. Multiply this by the current involuntary churn rate. This gives you the monthly revenue lost to failed payments. Next, estimate the improvement you can achieve by implementing a superior dunning process. Industry leaders often see a 50% to 70% reduction in involuntary churn after optimizing their payment infrastructure. Apply this reduction to your calculated loss figure. The resulting number is your "Available Upside."
For example, if a SaaS company has $50,000 in MRR and a 10% involuntary churn rate, they are losing $5,000 per month, or $60,000 per year, to failed payments. If you can reduce involuntary churn to 4% through better dunning, you save 6% of MRR, which is $3,000 per month, or $36,000 per year. This $36,000 is pure profit because you are not spending money to acquire new customers; you are rescuing existing ones. When you have your own data or browse listings on Flippa or Empire Flippers, you can use this formula to adjust your offer price. If the seller is unaware of this leverage, you can negotiate a lower price based on the cost to fix these issues, or keep the upside for yourself as a buyer.
Do not forget to factor in the cost of customer support. Every failed payment often results in a support ticket. Customers are confused and angry. They want to keep their service but cannot pay. Supporting these customers consumes staff time and distracts them from serving paying customers. If the business has a small support team, a high payment failure rate can stall their ability to handle onboarding questions or feature requests, indirectly affecting hard churn. Therefore, the financial impact is not just direct revenue, but also operational efficiency. Quantifying this operational drag adds another layer of justification for demanding a discount or a higher post-close investment.
Beyond the dunning logic, the underlying technical infrastructure plays a pivotal role in payment success rates. You must assess whether the SaaS application is integrated with the latest payment security standards, specifically 3D Secure 2.0 (3DS2). This protocol adds an extra layer of verification for card payments, which can reduce fraud and, paradoxically, improve approval rates by building trust with card issuers. If the business is using an older version of 3D Secure or no 3D Secure at all, you are facing a higher risk of failures due to issuer fraud controls. Migrating to 3DS2 can take weeks of development time and integration, which is a significant cost to consider.
Tokenization is another critical factor. Does the system properly token customer card details? This means storing a secure reference to the card rather than the card number itself. If the system is not properly tokenized, or if tokens expire too quickly, customers may be forced to re-enter their card details more often than necessary. This friction can lead to abandonment. A well-designed system should ensure that tokens are refreshed automatically when a new card is issued by the bank, a process known as card updater. If the business does not use card updater, every time a customer issues a new card with the same bank (which happens frequently), the subscription will fail. This is a silent killer of retention that many buyers do not realize exists until after they have taken over.
Recurring billing architecture is also subject to review. Is the business using a native recurring billing model, or are they using one-off charges scheduled via cron jobs? Native recurring billing handles retries, proration, and logic complexities automatically. Scheduled one-off charges are fragile. If a server load spikes or a database transaction fails, the charge might simply not happen, and there is no built-in mechanism to retry it. This architectural weakness creates a high "silent drop" rate where revenue is lost without any error notification to the user or the admin. Discovering this architectural flaw during due diligence is a massive red flag that suggests the engineering team may lack depth or best practices in SaaS development.
Armed with this technical and financial analysis, you are in a strong position to negotiate the purchase price. The most effective strategy is to present quantitative evidence. Create a one-page document outlining the current payment failure rate, the projected revenue loss, and the cost to remediate the issue. Present this to the seller. Most SME (Small and Medium Enterprise) sellers are operators; they care about efficiency and revenue. When you show them that they are leaking money due to technical negligence, they are often willing to lower the price to account for the fix. Alternatively, they may agree to keep their current developer on retainer for a month post-close to ensure the transition of the payment systems is smooth.
If the seller is non-responsive to these technical concerns, or if the infrastructure is so broken that the fix costs more than the business is worth, you should walk away. There is no shame in passing on a deal that has fundamental structural issues. The market is full of opportunities. Use platforms like Deal Alert AI to filter for listings that show signs of mature technical infrastructure, such as high revenue retention and low ticket volume. A seller who ignores your questions about payment dunning is telling you that they have not looked under the hood of their revenue engine. That is a sign of complacency, which often leads to further hidden problems.
Another negotiation tactic is the "Earn-Out" structure. If you are unsure of the true extent of the payment recovery potential, you can structure the deal with a portion of the purchase price tied to hitting specific revenue milestones. For example, you pay 80% upfront and 20% post-close, contingent on the recovered revenue reaching a certain threshold. This transfers the risk of the payment failure fix to the seller. If they are confident in their system, they will accept. If they are not, or if the system is weak, they will likely be open to a lower upfront price knowing they have to put in the work to earn the rest. This aligns incentives and protects your capital while you work on optimizing the payment flow.
To ensure you do not miss these critical details, use the following checklist during your due diligence phase for any SaaS acquisition. This list covers the technical, financial, and operational aspects of payment processing. Use it as a standardized tool for every deal you review. Consistency in your due diligence will save you from costly mistakes and help you identify the true value of the business.
Once you have closed the deal and taken ownership of the SaaS business, your first task should be to implement the optimizations identified in due diligence. Start with the easiest wins. If the seller was using a basic email provider for dunning, switch to a specialized service like Churn Buster, Upstream, or RevRec. These tools integrate seamlessly with Stripe and others and offer AI-driven dunning sequences that have been proven to recover lost revenue. This switch can often be done in less than a week and may yield immediate results. You will see the metrics of recovered charges start to climb, providing you with tangible proof that your acquisition strategy is working.
Next, focus on the technical architecture. If the business lacks card updater, work with your developers to implement a service that automatically detects new card tokens. This is a complex task that requires deep integration with the payment provider’s API. Budget for external developer help if your internal team is not proficient in this area. This phase may take a few weeks to a few months, depending on the complexity of the legacy code. However, the long-term benefit is a significant reduction in involuntary churn that is sustained over the life of the business. This is where the real value creation happens for buyers.
Finally, establish new KPIs for the business. Add "Involuntary Churn Rate" and "Recovered Charge Percentage" to your weekly dashboard. These metrics should be monitored with the same intensity as MRR and CAC (Customer Acquisition Cost). By keeping a close eye on these numbers, you can detect any regressions in payment performance early. If the failure rate spikes, you know immediately that something has changed, whether it is a new payment processor policy, a bug in your app, or a change in your customer base. Proactive monitoring allows you to act before the revenue leak becomes a flood. This disciplined approach to payment analysis is what separates successful acquisitions from failed investments.
In conclusion, the analysis of SaaS payment failure rates is not a niche technicality; it is a core component of business valuation. In the competitive landscape of online business acquisitions, edge is everything. By understanding the mechanics of involuntary churn, auditing the technical infrastructure, and negotiating based on hard data, you position yourself as a sophisticated buyer. You are not just buying revenue; you are buying an asset that you can immediately engineer for greater profitability. As you continue your search for the next investment, remember that the numbers on the surface are only the beginning. The real value lies in the details of how that revenue is captured, retained, and recovered. Use this knowledge to your advantage, and you will deliver exceptional returns on your capital. The next profitable deal is out there, waiting for someone who knows how to look under the hood.
We scan Empire Flippers, Acquire, Flippa, and Quiet Light daily. The best sub-$500K businesses are gone within 48 hours.