Six-layer model of stablecoin payment infrastructure

Author: @richardbtaiche, Product Lead, Stablecoin Payments and Infrastructure

Summary and Introduction: The six-layer model of stablecoin payment infrastructure includes licensing and regulation, customer onboarding, custody and wallets, fiat deposit and stablecoin receipt, distribution and payments, and exchange (fiat-stablecoin swaps). Most fintech companies underestimate the complexity of implementing stablecoin payments; each layer presents unique regulatory and operational challenges, and the connections between layers are critical. Paxos, as a unified regulated platform, provides all six layers of service, helping companies reduce integration costs.

Almost all major fintech companies are attempting to incorporate stablecoins into their payment stacks. Most of them severely underestimate how complex this problem really is.

The common assumption is that stablecoin payments are a product decision: choose a token, add a wallet, connect an API. But in reality, it’s an infrastructure decision that involves licensing, identity verification, custody, settlement, exchange, and distribution. Any problem in one layer can halt the entire project.

This is especially important now because the window to treat stablecoins as experimental products is closing. Transaction volume has exceeded $30 trillion. Stripe enables merchants to accept stablecoin payments. PayPal offers PYUSD to millions of customers in over 70 countries. Stablecoin transactions between businesses and consumers more than doubled last year. Infrastructure issues have shifted from “Should we?” to “How quickly can we go live?” — and the answer depends entirely on how many layers you need to build from scratch.

The industry is converging on a six-layer model of stablecoin payment infrastructure. Each layer has its own regulatory scope, operational complexity, and integration burden. The hardest part isn’t any single layer, but the connections between them: transaction monitoring, travel rule compliance, sanctions screening, settlement reconciliation, and the orchestration logic that must operate across all six layers simultaneously.

Most platforms attempting to solve this problem end up cobbling together fragmented solutions from a dozen or more vendors, each with their own compliance models and settlement cycles. The result is a technically feasible but operationally fragile system, a nightmare to audit. Paxos has built all six layers on a single platform, operating under active regulatory supervision in the US, EU, and Singapore. One integration, one regulated counterparty. Payment companies like Modern Treasury, BVNK, and Confirmo are already running their stablecoin flows on Paxos infrastructure.

Below is what each layer actually requires, and how any flaw in one layer can ripple through the others.

Layer 1: Licensing and Regulatory Foundation

Every stablecoin payment project begins here, and most get stuck here.

Regulatory positioning of stablecoin infrastructure providers has become a defining competitive variable in the space. The passage of the GENIUS Act sparked a wave of issuers and infrastructure firms rushing to obtain OCC national trust charters — not just for legitimacy, but because license holders may ultimately connect directly to the Federal Reserve. Your position in the regulatory hierarchy today determines your position in the payment hierarchy tomorrow.

For fintech companies, the practical impact is severe. Operating across jurisdictions means obtaining trust licenses, money transfer licenses, or equivalent regulatory registrations in every market you serve. Building these independently requires years of legal work, millions of dollars in capital, and ongoing compliance cycles. Most fintechs lack the resources and time. The longer they wait, the higher the regulatory barriers become.

This layer is where the “build or partner” decision is made, because building independently here is the most costly and time-consuming.

Paxos Trust Company holds an OCC national trust charter. This is a bank-level federal regulator, providing a single framework for compliant stablecoin operations within the US. Paxos also holds active licenses from MAS (Singapore) and FIN-FSA (EU, MiCA approved). Partners operate under Paxos licenses, not building their own regulatory plans, which means compliance and legal teams have a regulated counterparty with a proven track record and active regulatory relationships to reference.

Layer 2: Customer Onboarding

A license without onboarding is just paper. Layer 2 is where regulatory obligations meet product experience, and where most stablecoin projects first encounter the tension between compliance and conversion.

Stablecoin projects need to perform KYC on individuals and KYB on businesses. The challenge isn’t just verifying identities but doing so without adding friction that kills partner conversion rates. Every extra screen, document upload, or “pending review” status is a dropout point. But cutting corners on verification can lead to more costly issues: transactions being blocked, accounts frozen, regulatory enforcement actions.

From a user experience perspective, the key question is whether onboarding can run as an invisible compliance layer. Ideally, it should operate in the background, with end customers only interacting with the partner’s product.

Paxos offers embedded KYB/AML infrastructure that can be directly integrated into partner platforms. Partners who have already collected identity data can leverage dependency frameworks to avoid repeated verification. Paxos also supports silent onboarding, where compliance runs in the background and customers never need to interact directly with Paxos. In all models, Paxos remains a regulated counterparty.

Layer 3: Custody and Wallets

Once customers are onboarded and funds start flowing, someone must safeguard those assets. The custody model chosen by the platform determines its risk exposure, insurance status, and custodial obligations. This layer is the first thing enterprise compliance teams scrutinize.

The difference between pure technology custody and qualified custody is more significant than most engineering teams realize. Technology providers can store digital assets. Qualified custodians hold them under specific regulatory frameworks, with check cycles, capital requirements, and fiduciary responsibilities, whereas pure tech providers do not. When enterprise partners assess counterparty risk, or when regulators do, this distinction is top of mind.

This layer also determines what happens if things go wrong. Qualified custody under federal licenses provides a clear legal framework for asset recovery, creditor priority, and regulatory recourse. Pure technology custody does not.

Paxos is one of the oldest qualified custodians in digital assets, operating under OCC supervision, with SOC 1 Type II and SOC 2 Type II certifications. Paxos offers qualified custody, including integrated accounts and segregated account structures, covering settlement accounts, stablecoin reserves, and multi-asset portfolios under unified regulatory oversight. For digital assets beyond fiat-backed stablecoins, Paxos provides embedded wallets and MPC infrastructure through Fordefi, acquired in November 2025.

Layer 4: Fiat Deposit and Stablecoin Receipt

The first three layers establish the regulatory and operational foundation. Layer 4 is where funds actually enter the system, and where two fundamentally different technical problems must be integrated into a single settlement experience.

For fiat, stablecoin projects need to accept real-time payments, wire transfers, and card payments. For crypto, they need to accept stablecoin deposits directly. Imagine consumers paying merchants, enterprises settling into stablecoin positions, treasury operations topping up wallets. Regardless of how funds arrive, they need to be quickly settled and clearly reconciled under a regulated infrastructure. A platform that handles fiat deposits but not stablecoin receipt (or vice versa) only has half the entry point — no usable product.

This layer is where the “bank connection” problem arises. Stablecoin infrastructure is built almost entirely outside the traditional banking system. Integrating with legacy core systems requires a dedicated translation layer. When building this layer, many projects find their custody providers cannot communicate with fiat rails, and vice versa.

Paxos provides fiat gateways and regulated settlement accounts that accept traditional rails and on-chain stablecoin deposits. Both paths settle funds into Paxos’s trusted infrastructure from the moment they arrive, in a compliant, auditable manner. For companies like Stripe, this means stablecoin payments from consumers can be fully accepted, exchanged, and settled to merchants via Paxos infrastructure. Stripe processes stablecoins at enterprise scale, proving stablecoin payments are no longer hypothetical — they are live.

Layer 5: Distribution and Payments

Moving funds into the stablecoin system is Layer 4. Moving funds out is where the infrastructure faces a stress test.

Platforms need to make stablecoin payments, settle back to fiat via local rails, or support both. The payment layer must handle transaction volume, support multiple channels, and reliably settle every time. This is also where “last mile” liquidity issues surface: stablecoins have made real progress in cross-border payments, but liquidity between stablecoins and local fiat in many channels remains thin. Thin liquidity means slippage, delays, and unreliable pricing. For a platform promising reliable settlement to partners, this is a survival issue.

This is also the most common failure point in DIY stablecoin stacks. A platform built with four different vendors for Layers 1–4, now finds no vendor handles the required payment channels, or settlement times are mismatched because compliance models and reconciliation cycles don’t align. The connection fails before funds reach the recipient.

Paxos offers stablecoin payments and fiat settlement for live projects. USD settlement and specific channels are handled directly by Paxos. For broader FX and local account delivery, Paxos extends coverage via partner integrations, without compromising regulatory standards.

Layer 6: Exchange (Fiat-Stablecoin Swaps)

Exchanges are not a one-time event but a repeated operation at multiple points in the payment flow. Deposits from fiat to stablecoin, treasury management from stablecoin to stablecoin, payments from stablecoin back to fiat. Each exchange requires liquidity, asset access, and settlement infrastructure.

The stablecoin market is more competitive than ever, with multiple issuers and tokens in active circulation. Platforms attempting to build exchange relationships in isolation end up managing different integrations with each issuer, each with its own settlement cycle and risk profile. This complexity multiplies with each new token and channel. And as stablecoin business grows (transactions between enterprises and consumers more than doubled last year), the exchange layer becomes a throughput bottleneck for the entire stack.

Paxos provides exchanges and orchestration among PYUSD, USDP, USDG, and USDC, using multi-location liquidity strategies and a unified orchestration API. USDT exchanges are enabled for institutional clients in specific jurisdictions, with broader availability coming in the next months. One integration replaces multiple issuer relationships and offers institutional pricing and execution to partners.

The Bigger Picture

The six-layer model is more than just an infrastructure framework. It’s a map of regulatory and operational scope, distinguishing platforms that merely talk about stablecoin payments from those that actually process them.

Stakeholders go beyond payments. Stablecoins are enabling a new bank-as-a-service paradigm: a model built on on-chain infrastructure rather than bank licenses and legacy core systems. The payment layer is where accounts are opened; credit, investment, and treasury products are where the business is built. Every platform solving the six-layer payment problem is also laying the groundwork for the next generation of financial products.

But the reverse is true as well. Every platform with gaps in its infrastructure — for example, custody that cannot connect to compliance engines, payment channels that cannot reconcile with deposit rails, or exchange layers adding days of settlement delay — is building a foundation that cannot support future growth.