Lena runs a SaaS business with about £50,000 in monthly recurring revenue. Her revenue is the model investors love — predictable, contracted, repeating. Her finance team can forecast next month's cash flow within a few percent. The product is steady. The customers are steady. The growth is gradual and modeled.
The settlement, on the other hand, is not on the same calendar. Card recurring sometimes fails on the first attempt, sometimes succeeds on a retry, sometimes settles T+2, sometimes T+3 across a weekend. Renewals that land on a Friday show up in the bank account on Tuesday. Renewals that land on a Monday show up Wednesday. The MRR number on her dashboard is solid; the bank balance that tracks it lags it, in ways that vary by week.
For a subscription business, this mismatch is a low-grade tax. The model is supposed to deliver predictability. The infrastructure underneath delivers something close to predictability, but never quite the same shape as the revenue.
Where the predictability breaks
Three things break the link between recurring revenue and recurring cash on a card-network rail.
The first is failed cards. Customer cards expire, get reissued with new numbers, get declined for limit reasons, or get blocked by issuing banks for routine fraud monitoring. Most subscription processors run retry logic to recover the failed payment, but the retry happens days after the original renewal date — meaning the cash arrives on a different schedule from the MRR booking. Finance teams either model "expected cash from MRR with a percentage drop and a delay buffer", or they reconcile manually each month.
The second is settlement timing variance. T+2 across a normal week is a 4-business-day window depending on which day the renewal falls. Add a public holiday — a long weekend, a national holiday in the processor's banking jurisdiction, a year-end break — and the variance widens. A subscription that renewed on December 23rd may not settle until January 2nd. The MRR is the same; the cash flow is not.
The third is the cumulative effect on the finance function. A subscription business with thousands of monthly renewals processes thousands of small settlement events each month, and the timing of each is independent. The aggregate is roughly predictable; any specific window is not. The finance team's monthly close ends up reconciling timing rather than substance — answering "where is the gap between booking and bank?" instead of "is the business healthy?"
How Spondula's gateway handles recurring billing
Spondula's payment gateway processes recurring payments the same way it processes one-off payments: peer-to-peer between the customer's wallet and the merchant's wallet, settling in seconds, with no T+2 settlement window held by an intermediary. A renewal on the network is not a card-network authorisation that has to clear through a multi-day chain — it is a direct transfer from one wallet to another, confirmed and settled in the same moment.
This means the merchant's MRR and the merchant's cash track each other on the same calendar. A renewal that processes on Tuesday at 3pm appears in the merchant's wallet at Tuesday at 3pm. A renewal at 2am on a Sunday appears at 2am on a Sunday. There is no offset between when the booking is registered and when the cash is in the wallet.
For Lena, this means her MRR and her bank balance do not need separate forecasts. The chart of recurring revenue is the chart of recurring cash. The finance team's reconciliation work shrinks because the timing variance disappears. Card-failure dynamics still exist — customers do still cancel, change their wallets, or fail to top them up — but the timing of successful renewals stops being a separate variable to model.
Join the conversation.
0 comments · Be respectful, be specific, be useful.
Be the first to comment.