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.
Only 35% of cross-border retail payments are credited to the recipient within one hour, against a G20 target of 75% by 2027.
— Bank for International Settlements, CPMI 2024 cross-border payments monitoring survey, 2025
What changes for a subscription business
Three things change for a subscription business running renewals on Spondula's gateway.
Cash-flow forecasting becomes simpler. The MRR number from the billing system and the cash number from the bank reconcile to the same calendar, with no settlement-timing variance to model. CFOs spend less time explaining the gap between booked revenue and available cash.
Renewals across time zones and weekends process at the same speed as renewals on a Tuesday morning. A subscription business with global customers — different time zones, different weekend conventions, different banking holidays — does not see settlement timing variance because the customer paid at an inconvenient hour. Settlement is independent of the calendar.
And the finance team's monthly close becomes structural rather than reconciliatory. Less time on "where is this lag from?", more time on "what is the business actually doing?" The finance function focuses on the substance of the business rather than the artefacts of the payment infrastructure.
What about cross-border subscribers?
Subscription businesses with international customers face a sharper version of the timing problem on card rails. A US-based subscriber renewing on a UK SaaS account triggers a cross-border card transaction, which adds FX margin and often extends settlement timing to T+3 or longer. The merchant's MRR booking is in their home currency; the cash that arrives is in their home currency too, but converted at a rate they did not see and arriving on a calendar they cannot predict.
On Spondula, an international subscriber renews in seconds, the same way a domestic one does. The merchant chooses what currency to hold in — USD-S, GBP-S, EUR-S, or any combination — and converts between them on their own schedule. The cross-border layer of complexity that compounds settlement-timing problems on card rails simply does not appear on a network-settled rail.
Subscription businesses live on predictability. The settlement infrastructure underneath them should match — not approximate it with a few days of timing variance baked into every renewal.
Spondula's gateway is open for launch partners — SaaS businesses, content subscriptions, membership services, and any recurring-revenue business whose finance team has built the timing variance of card settlement into their monthly reconciliation work. The waitlist is the starting point.
Frequently asked questions
How does recurring billing work on Spondula?
Recurring payments on the Spondula network process the same way as one-off payments: peer-to-peer between the customer's wallet and the merchant's wallet, settling in seconds. The customer authorises the recurring relationship once, and subsequent renewals process on schedule with the same instant settlement. There is no separate card-recurring rail with its own timing.
What happens if a customer's wallet does not have enough balance at renewal?
The renewal does not process. The network notifies both parties, the merchant's billing system flags the failed renewal, and the customer can top up their wallet to retry — much like a failed card payment, but without the multi-day retry window and without the merchant being exposed to settlement-timing variance during the retry process.
Can I run Spondula recurring billing alongside my card-based subscriptions?
Yes. Most launch partners run both during a transition period — card-based subscriptions for customers who want to pay by card, Spondula recurring for customers with a wallet on the network. The two coexist in the merchant's billing system, and the merchant migrates volume as their customer base adopts.
What about international subscribers with different currencies?
The merchant chooses what currency to hold their settled value in — USD-S, GBP-S, EUR-S, or any combination. International subscribers settle in seconds across borders, and the merchant decides when (and at what rate) to convert between currencies. There is no forced FX margin extracted at the moment of each renewal.
Does Spondula's recurring billing handle cancellations and upgrades?
Yes. The recurring relationship between customer and merchant on the Spondula network can be cancelled, upgraded, or modified the same way it can on any modern subscription platform — the difference is in how the settlement of each renewal works, not in how the subscription lifecycle is managed. Onboarding covers the specific integration paths.
Spondula is a global payments network. It is not a bank, exchange, investment platform, or broker. Availability, pricing, and Operator coverage vary by country. Bitcoin rewards depend on real network activity and are not guaranteed. See our terms and conditions for full details.
