Fintech Firms Are Buying Crypto Infrastructure, Not Building It

Financial technology firms adding crypto capability faced a build or integrate decision across several layers. The answers converged. The sector-level shift described here is observable in the published terms of a regulated crypto payment provider with fiat settlement.

What almost nobody builds

Liquidity for conversion. Sourcing at competitive spreads requires either inventory and market making capability or relationships with those who have it. Building it before having volume spends engineering effort on a solved problem.

Chain infrastructure. Running nodes across many networks, handling reorganisations, monitoring for deposits. Operationally heavy and entirely undifferentiated.

Compliance screening. Sanctions and risk data are bought, not built.

What firms do own

The ledger. The record of what each user is owed. Owning it keeps the product flexible and the provider replaceable.

The user experience. Where differentiation actually lives.

The compliance decisions, as distinct from the screening data. Who to onboard, what to escalate, what to report.

The licensing question underneath

The determining question is whether the firm needs its own authorisation or can operate under a partner’s.

Holding crypto for users is custody and requires the permission. Exchanging on their behalf is another. Introducing users to a provider who does both may leave the perimeter with the provider. Merchants encounter this on the acceptance side, where a platform set up for client account handling carries the obligation.

It is not a technical question. It is about who has the contractual relationship with the user and who controls the assets.

Firms that get a legal view before building save considerably more than the cost of the advice.

What to require from a partner

Authorisation covering every service they perform, verified on the register, held by the entity in your contract.

An interface supporting your model: sub-accounts or a ledger mapping to your users, signed callbacks, protection against duplicate processing.

Settlement in the currencies and countries your users need, which is usually the binding constraint.

Reporting that reconciles daily without manual work.

A written allocation of compliance responsibility.

The term firms under-negotiate

Notice period. Ninety days on a partner embedded in the payment flow is not enough to migrate.

Firms negotiate the rate and accept the rest as standard. The rest is where the operational risk sits.

The build sequence that works

One corridor, one asset, end to end including failure cases and reconciliation. Prove it. Then add assets, then corridors.

Building a general abstraction over several providers before operating one at volume encodes assumptions that turn out to be wrong. Verify rather than infer. Collect & Exchange appears on a public register that takes five minutes to read.