Why banks and remittance firms stay on stablecoins once they start
Ran Goldi, Fireblocks
Moment at 58:06Episode 6 · Stablecoins Go Mainstream: Inside the New Payments Stack
Blockchain Infrastructure for Payment Providers
In short
Blockchain infrastructure for payment providers is the on-chain layer a regulated PSP, bank, or cross-border platform uses to settle payments with stablecoins under its own brand: stablecoin settlement, on/off-ramp orchestration, treasury and reconciliation, and 24/7 operations, wired into its existing product and license.
Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: October 2026
250+
projects shipped since 2016
Core
Chainlink contributor: CCIP cross-chain and oracles
$2B+
in assets secured through Safe across 120+ EVM networks
60+
production networks integrated
Trusted by teams building on-chain
Payment providers, banks, and cross-border platforms are watching settlement volume shift to stablecoin rails, and the ones that do not offer it lose the route to a competitor that does. Blockchain infrastructure for payment providers is the on-chain layer that lets a regulated provider settle payments with stablecoins instead of correspondent banks, inside its existing product and under its own license: on-ramp and off-ramp orchestration, a stablecoin issuer mix, cross-chain settlement, treasury and reconciliation into the core ledger, compliance hooks, and the 24/7 operations to run it.
Protofire builds and operates that layer. We are an engineering-led firm with 250+ projects shipped since 2016 and a core contributor to the primitives it depends on, so a provider can offer faster, cheaper settlement without standing up a web3 engineering organization first.
How stablecoin rails slot into a regulated provider's stack
The provider keeps its license, its core systems, and its customers; these seven layers wire stablecoin settlement into what it already runs.
01
Provider product & brand
The customer-facing payment product stays the provider's, on its own license, with the stablecoin machinery running behind the existing UX.
02
On/off-ramp orchestration
Route-by-route on-ramp and off-ramp integration so funds enter and leave in local currency, vendor-neutral rather than tied to one provider.
03
Stablecoin issuer mix
Integration across issuers such as Circle (USDC) and Tether (USDT), chosen per route and limited to the coins each corridor's rules allow (in the EU, MiCA-compliant e-money tokens only), so the product is not locked to a single coin.
04
Cross-chain settlement
Chainlink CCIP for moving value between networks without custom bridge risk, via the layer we help maintain.
05
Treasury, FX & custody
Float, rebalancing, and FX-exposure controls, with treasury keys behind Safe multisig under an authority matrix the provider controls.
06
Compliance & reporting
KYC, AML, and travel-rule hooks and regulatory reporting wired into the provider's existing compliance stack, inside its perimeter.
07
Core-ledger reconciliation
Every on-chain settlement reconciled back to the provider's core banking or ledger system, indexed via The Graph, so the books close cleanly.
01
Who this is for: PSPs, banks, and cross-border platforms
We build for regulated providers that move money and want stablecoin rails inside their own product. A payment service provider offering stablecoin settlement to its merchants and keeping the spread. A bank or digital bank adding stablecoin rails to its cross-border product under its own license.
A remittance or trade-finance platform whose importer and exporter customers already ask for stablecoin settlement. And a fintech that wants cross-border settlement inside its app without building a crypto engineering team. The common precondition, which we qualify on before building, is a regulated provider of record that owns the compliance perimeter, real volume on defined routes, and a core system we can reconcile against.
02
The problem: correspondent banking is losing the route
Correspondent banking moves an international payment through a chain of intermediary banks, each taking a fee and adding a delay, with money pre-funded in nostro accounts that sits idle in every destination currency. The World Bank puts the global average cost of sending a cross-border remittance at over 6 percent (source: World Bank Remittance Prices Worldwide), most of it in those intermediary hops.
Meanwhile the provider's own customers, importers, exporters, and trade businesses, increasingly settle in stablecoins, and they would rather do it inside a regulated provider they know than through a global app that does not know their market. Offering stablecoin settlement, though, means multi-issuer and multi-ramp integration, treasury and FX flows, reconciliation into an existing core, regulatory reporting, and 24/7 operations, the engineering the global infrastructure vendors will not prioritize for anyone but the largest platforms, and that a payment provider's own team cannot hire for at market speed. Every quarter of delay is route share handed to whoever integrates first.
03
What we build for payment providers
We build the full stablecoin payment layer and operate it if wanted. The core is stablecoin cross-border payment infrastructure: issuer and ramp orchestration, treasury and reconciliation, and cross-chain settlement, under your brand.
For an e-money institution whose customers hold euros in their own wallets, we build wallet-linked IBAN accounts: signed address binding, mint and burn orchestration and reconciliation against the token supply. Around it we bring the primitives a payment product runs on: Chainlink CCIP integration for cross-chain settlement, oracle integration for price and FX reference data, and Proof of Reserve where a stablecoin's backing has to be attested on-chain.
Where a provider wants its own dollar rather than a third-party coin, we build native stablecoin issuance and the broader tokenization infrastructure for regulated on-chain products. And once a product is live, managed on-chain operations keeps it watched and maintained 24/7.
You stay the licensed provider of record throughout; we are the engineering and operations partner, not a money transmitter, issuer, or custodian.
04
Start from a proven blueprint
Our blueprint library documents payment architectures already running at regulated institutions: the regime that permits each one, named institutions operating it, and which layers a provider owns, rents, or has us build. Six are drawn for payment and e-money institutions:
Stablecoin payout corridors
→Pay beneficiaries in stablecoins across corridors you already serve, from a funded float to an on-chain or local off-ramp payout.
Crypto acceptance, euro settlement
→Accept crypto and stablecoins at the till and settle merchants in euro with no crypto exposure, on the terminals they already have.
Wallet-linked IBAN accounts
→Bind an account number to an address the customer holds the keys to, so an ordinary SEPA transfer arrives on chain.
Euro stablecoin issuance
→Issue a euro e-money token in your own name under MiCA, with the reserve, monitoring and disclosure operation behind it.
Reserve-capped mint controls
→Make minting fail closed, with divided, rate-limited authority and supply reconciled against safeguarded reserves.
Euro e-money token distribution
→Put a euro stablecoin in your product on a licensed issuer's rails, with no issuance licence of your own.
05
An engineering-led partner on the rails payments run on
Protofire is an engineering-led blockchain development firm with 250+ projects shipped since 2016, across 60+ networks and 95+ protocols. The credentials that matter for a payment product are specific. We are a core contributor to Chainlink, including CCIP, the cross-chain messaging standard that moves value between networks, and the oracle layer for price and FX reference data.
We deployed Safe, the custody-governance layer that guards treasury keys, on 120+ EVM networks, where it secures $2B+. We build the subgraphs that make every settlement queryable for reconciliation and reporting, and from 2020 to 2024 we ran a top-3 indexer on The Graph by indexing rewards.
And we built the DEX core and subgraph for Swarm Markets, a BaFin-licensed DEX at launch where only KYC-verified wallets can trade, so we know the discipline a regulated payment product needs. The cross-chain, custody, indexing, and compliance layers a payment product is built on are ones we help maintain.
“The provider keeps its license, its customers, and its pricing; we build the rails, the treasury and reconciliation flows, and the operations that turn stablecoin settlement into a production payment product.”
Regulated, compliant on-chain finance, live
7,000+KYC-verified users on Swarm Markets, the DEX we built the trading core for
We built the DEX core and subgraph for Swarm Markets, a BaFin-licensed DEX at launch where only KYC-verified wallets can trade tokenized real-world assets, the regulated discipline a payment product needs to go live and scale.
Swarm MarketsView project →
FAQ
How do payment providers use blockchain for cross-border payments?
A regulated payment provider uses stablecoins as the settlement rail instead of correspondent banks. Incoming local currency is converted to a stablecoin at an on-ramp, the stablecoin moves across a blockchain to the destination in minutes, and it is either held as a digital dollar or converted back to local currency at an off-ramp. Around that path sits the production engineering: orchestration that picks the right issuer and ramp per route, treasury and FX management, reconciliation into the provider's core ledger, compliance hooks, and 24/7 operations. The provider stays the licensed party of record, and the blockchain is the rail, not the regulated entity. Protofire builds that whole layer into the provider's existing product. Which licensed rail carries each corridor, and who faces the customer as the regulated party, is the subject of our stablecoin payout rails guide.
Why offer stablecoin settlement instead of correspondent banking?
Stablecoin settlement collapses the chain of intermediary banks into a peer-to-peer transfer that settles on-chain in minutes, on weekends too, from one stablecoin float in place of an account pre-funded in every destination currency, while the final payout into a bank account still follows the destination bank rail and its hours. That removes intermediary fees and hops, frees the working capital tied up as nostro float, and gives the provider direct control over the product, its brand, its pricing, and which routes it supports. Blockchain rails are also transparent and auditable by design, which is what makes reconciliation and regulatory reporting tractable at scale. The work moves from banking relationships to engineering and operations, which is the part we own.
Does the payment provider stay compliant and in control?
Yes. The provider remains the licensed provider of record and owns the compliance perimeter, the customer relationship, and the pricing. We build KYC, AML, and travel-rule hooks into the provider's existing compliance stack rather than replacing it, and treasury custody runs through Safe multisig under an authority matrix the provider controls. We are the engineering and operations partner, not a money transmitter, a stablecoin issuer, an exchange, or a custodian, and we do not hold funds. Rail choice and program design follow the provider's regulatory reality, not the other way around.
What does Protofire build versus what does the provider run?
We build the on-chain layer: issuer and ramp integration, cross-chain settlement, treasury and reconciliation into the core, and compliance hooks, and we can operate it 24/7 after launch. The provider runs the licensed business: it owns the customers, the funds, the pricing, and the regulatory reporting. This separation keeps the provider in control of everything a regulator cares about while we own the part that is genuinely blockchain engineering, and it is why a provider can ship a stablecoin payment product without building a web3 organization first.
What is the difference between a payment provider and a money transmitter on stablecoin rails?
The payment provider is the licensed, regulated entity of record: it holds the money-transmitter or e-money license, owns the customer relationship, and is responsible for compliance and reporting. Protofire is the engineering and operations partner, not a money transmitter, a stablecoin issuer, an exchange, or a custodian, and we do not hold client or customer funds. We build the on-chain rails and, if wanted, operate them, inside the provider's license and compliance perimeter. The regulatory status stays entirely with the provider, which is what lets a licensed PSP or bank offer stablecoin settlement without changing what it is.
How does regulation like MiCA affect stablecoin settlement for providers?
Regulation shapes which stablecoins and rails a provider can use, and where. In the EU, MiCA sets requirements for the e-money and asset-referenced tokens a provider may settle in, and travel-rule and AML obligations apply to the transfers themselves. Since the EBA's transition period ended in early March 2026, a provider that holds e-money tokens for clients or transfers them on their behalf also needs a payment license, or a licensed payment partner, on top of MiCA. We do not give legal advice, and we do not set the perimeter: rail choice, issuer selection, and program design follow the provider's regulatory reality and its counsel, and we build the KYC, AML, travel-rule, and reporting hooks into the provider's existing compliance stack so the on-chain product operates inside that perimeter rather than around it.
Discussed on The Protocol Roundtable
All episodesGet a proposal
Tell us what you are building. An engineer reads it, we have a short call, and the written proposal follows within one business day.
Budget
I accept the
Privacy PolicyI agree to receive new research announcements as well as information about Protofire services and special offers
An NDA is available from the first message and can cover anything you share. How it works