Tomás runs an online retail business that, after six months on the platform, was placed in his card processor's higher-monitoring tier — a categorisation triggered by the industry he sells in, not by anything that had actually happened on his account. The terms of the tier include a 10% rolling reserve, held for 180 days from each transaction date.
Six months in, the reserve has accumulated to roughly £15,000. None of that money is reachable. It sits with the processor as a contingent buffer against chargebacks that, in his case, have not occurred. Zero disputes. Zero clawbacks. Just £15,000 of his own working capital, frozen by a model that assigned him to a tier on day one and has not revisited the assignment since.
£15,000 is what Tomás would otherwise be using for inventory, marketing, his own salary, or simply as a buffer against a quiet month. Instead, it is the cost of being categorised.
What rolling reserves actually are
A rolling reserve is a percentage of a merchant's settled volume that the processor holds back as a contingent fund for chargebacks. The terms vary — 5%, 10%, or higher; held for 90 days, 120, or 180 days from the transaction date — but the structure is the same. Money the merchant has earned, has settled, and which is technically theirs, is held in a separate account that they cannot access, while the rolling window stays open.
The practical effect is that a percentage of every month's revenue is invisible to the merchant for the next several months. On a steady-state business, the reserve eventually plateaus — once 180 days have passed, the oldest funds become available as new ones are held. But during the ramp period, and any time volume grows, the reserve absorbs working capital faster than it releases it. A growing merchant is always running with more of their own money frozen than freed.
This is common industry practice for merchants in categories that processors classify as elevated-risk — supplements, ticketing, travel, certain digital services, dropshipping, and any number of legitimate industries that processor risk models flag. It is also applied selectively to newer merchants, merchants whose volume grows quickly, or merchants whose transactions look unusual against an algorithm.
Why the reserve exists — and who actually pays for it
The reserve exists because card networks impose chargeback liability on processors. When a customer disputes a charge, the processor is on the hook to refund — and they price that risk by holding back a buffer from the merchant's own funds. From the processor's side, this is a sensible risk-management tool. From the merchant's side, it is an interest-free loan that they do not get to refuse.
The merchant pays for the reserve in three ways. The first is direct: working capital is frozen, so any business activity that needed that capital — inventory, hiring, growth investment — is constrained or has to be funded elsewhere. The second is interest cost: if the merchant funds the gap from a credit line, they pay interest on capital they technically already own. The third is opportunity: a merchant who would otherwise be growing the business with retained earnings is instead growing it with debt, or not growing it at all.
None of this appears as a fee on a processor invoice. It is the silent operational tax of being in a category the model considers risky.
Rolling reserves of 5% to 10% of monthly volume, held for 90 to 180 days, are common industry practice for merchants in categories card processors classify as elevated-risk.
— Common industry practice as published in card-processing terms across major providers
Account freezes and manual review — the same problem, sharper
Reserves are the predictable form of held funds. Account freezes are the unpredictable form. A merchant whose transaction volume jumps, whose ticket size changes, whose customer geography shifts, or whose industry classification gets re-scored, can find their account paused for "manual review" — a process that holds all settlement until a risk team has checked the activity, sometimes for days, sometimes for weeks.
The merchant cannot expedite the review. They cannot withdraw the funds. They cannot move to another processor without the funds being held there too, because the reasons for the review usually transfer with the merchant's profile. They wait, and they keep trading on capital they do not yet have access to.
Manual review is a smaller line item in the industry's overall picture than rolling reserves, but it is sharper when it happens. A merchant running a successful campaign whose revenue lands in a frozen account learns the cost of dependency on a single processor very quickly.
Why Spondula's gateway does not need a reserve
Spondula's payment gateway is built on a different settlement model. Payments move peer-to-peer between customer and merchant wallets on the network. There is no card-network authorisation step. There is no chargeback mechanism that imposes contingent liability on the processor. There is no risk pool that the gateway needs to fund out of merchant balances.
Because the chargeback risk does not exist on this rail, the reserve does not exist either. A merchant on Spondula's gateway sees the full settled value of every transaction in their wallet — instantly, in seconds — and that value is theirs to use. There is no rolling 10% buffer accumulating in a separate account. There is no manual-review window holding settlement on Friday's sales until next Wednesday. There is no tier system that puts a merchant on a longer settlement schedule because of the industry their business is in.
Spondula's gateway is not a specialist processor for high-risk industries. It is a payment network whose economics do not require the risk-tier model that card processors are built around. The same network, the same settlement speed, and the same access to one's own funds applies whether the merchant sells software, ceramics, supplements, subscriptions, or anything else legitimate.
Held funds are the most invisible cost of online payment processing — and the one that hits legitimate businesses hardest, because it does not depend on what they have done, only on what their model has been told to expect.
Spondula's gateway is open for launch partners — online retailers in any legitimate category, subscription services, marketplaces, and businesses tired of bankrolling a risk model with their own working capital. The waitlist is the starting point.
Frequently asked questions
Does Spondula hold any portion of merchant funds in reserve?
Spondula's gateway does not operate a rolling reserve based on industry category, transaction profile, or account age. Settlement on the network is peer-to-peer and instant, and the merchant's full settled balance is available in their wallet from the moment a payment confirms. The standard card-processor reserve model does not apply on this rail.
What if a customer disputes a payment?
Spondula payments do not carry the card-network chargeback mechanism. Disputes between buyer and seller are handled through the network's dispute-resolution process, which is structured around evidence and resolution rather than involuntary clawback. The merchant's settled balance is not exposed to the kind of unilateral reversal that card chargebacks impose.
Are there any merchants Spondula does not work with?
Spondula's gateway is open to legitimate businesses operating within the legal and regulatory framework of the jurisdictions they sell into. The network does not categorise merchants into risk tiers the way card processors do, but it also does not accept activity that is illegal, sanctioned, or otherwise prohibited under financial regulation. The application process is the starting point.
What about manual review for unusual transactions?
Spondula's network does not pause settlement for the kinds of transaction profiles that trigger manual review on card networks — large single orders, sudden volume changes, or shifts in customer geography. Compliance and fraud monitoring do exist on the network, but they are not designed around the card-network risk-pool model that produces routine merchant-account holds.
If I am currently in rolling reserve with a card processor, how do I migrate?
Merchants can run Spondula's gateway alongside an existing card processor during a transition period, shifting volume to the network as their customers adopt it. The funds held in reserve at the previous processor follow that processor's release schedule — Spondula does not control them. But going forward, new volume on Spondula does not feed a reserve. Onboarding covers the practical migration steps.
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.
