By Ilya Podoynitsyn, CEO of FinHarbor
In 2025, stablecoins moved an enormous sum on-chain, by some counts close to $35 trillion. Yet when McKinsey and Artemis Analytics stripped out trading, treasury rebalancing and automated contract loops, genuine end-user payments came to roughly $390 billion. That gap tells the whole story of crypto-acquiring. The headline number proves the rails exist; the smaller, faster-growing figure shows where real commerce is happening, and why turning blockchains into a payment method is an infrastructure problem rather than a widget.
The distinction is easy to miss, because the most visible part of any crypto checkout is the button: pick a token, scan a QR code, confirm. For a merchant, though, accepting the token is the trivial step. Everything the button hides is the actual work: compliance screening, currency conversion, settlement, reconciliation and reporting, all of it performed reliably, at scale, and inside a regulatory perimeter. A provider that ships only a payment widget has solved a small slice of the problem and left the merchant to handle the rest alone.
Much of the confusion comes from importing intuitions from the card networks. Visa and Mastercard run closed, permissioned systems, and inside that loop sit decades of accumulated machinery: issuer-to-acquirer relationships, guaranteed settlement, dispute arbitration, chargebacks, a built-in liability framework. The merchant rarely thinks about any of it, because the network absorbs it.
Public blockchains work the other way around. They are open, permissionless and final. A confirmed transaction is irreversible, settles peer-to-peer and answers to no central operator. That gives merchants real speed and reach, but it also means none of the card network’s guarantees come for free. There is no chargeback, no built-in arbitration, no counterparty to call when funds arrive from a sanctioned wallet. So the infrastructure provider has to rebuild those protections on top of rails that were never designed to offer them: risk scoring, monitoring, settlement assurance, reconciliation.
Settlement timing makes the difference concrete. Traditional acquiring runs on deferred, batch-based cycles. Funds are authorised in seconds, but they reach the merchant’s account on a delay, usually T+1 to T+3, and sometimes T+7 or longer in cross-border and high-risk segments where rolling reserves are standard. Every day in that cycle is working capital the merchant cannot use.
Stablecoin rails invert the model. Settlement happens at T+0: value moves and finalises on-chain in seconds, around the clock, with the blockchain itself acting as the source of truth. Worldpay already settles with merchants in real time on this basis, up to 50% faster than legacy rails. For a merchant, T+0 is liquidity, not a feature. Capturing it, though, takes orchestration: conversion at the moment funds arrive, treasury logic, and reconciliation that maps every on-chain transaction back to an invoice. Speed without that plumbing just moves the complexity somewhere else.
For PSPs, crypto-acquiring is not only about adding another payment method. It is also a way to serve merchants operating internationally, reduce settlement delays, and capture transaction volume that would otherwise move outside traditional payment rails. The challenge is delivering all of that without re-architecting the core platform.
This is where the distinction between an acquirer and a software provider matters. FinHarbor does not acquire merchants. We supply the crypto-processing software that PSPs, banks and payment platforms run themselves. Our clients deploy it on their own infrastructure, under their own license, and use it to onboard and acquire their own merchants. The platform keeps the regulatory relationship and owns the customer; we provide the engine underneath, and a client can be live with it in as little as two weeks.
The crypto-processing software is deployed on-premise and fully white-label, so nothing in it carries our brand. From there, the platform’s merchants customise their own checkout: a drop-in widget they brand as their own, or a custom interface built on the same API when they want full control of the experience. Either way, crypto runs through the same accounting, reconciliation and reporting logic as fiat, so there is no parallel stack and no fragmented data. Settlement, compliance, FX and checkout each sit as a separate module a client can configure, swap out or extend. The idea is to work around a platform’s existing systems rather than force it to rebuild around us.
On open rails, transaction monitoring is the protection that matters most. Because blockchain payments are irreversible, screening cannot wait until after the fact; once tainted funds land, there is no clean way to send them back. That is the role of Know Your Transaction (KYT): scoring the on-chain history of incoming funds, checking counterparties against sanctions lists, and flagging exposure before a payment is accepted.
The risk is far from theoretical. Chainalysis estimates that illicit addresses received at least $154 billion in 2025, with stablecoins now accounting for 84% of that volume. Illicit activity still sits below 1% of all on-chain flows, but a single tainted inflow can freeze a merchant’s funds or trigger a regulatory headache. We embed wallet screening, KYT and sanctions checks straight into the payment flow at FinHarbor, connected to each client’s existing risk framework, which keeps the PSP in full control of its own AML policy and client data.
Crypto-acquiring has moved from a niche checkbox to a serious global payment rail, and the regulatory ground beneath it is finally setting, from MiCA in Europe to clearer stablecoin rules across the major financial hubs. As that clarity arrives, the question for PSPs and platforms stops being whether to accept crypto and becomes how well they can run it: how quickly funds settle, how cleanly compliance is handled, how little of the machinery a merchant ever has to see. Stablecoin payments are still a small share of global volume, but the trajectory is no longer in doubt. The providers who lead the next phase will be the ones who treated acceptance as an operational layer from the start, and the merchants moving onto these rails now will gravitate toward partners that built for reliability rather than for a demo.


