Circle Payments Network (CPN) launched in April 2025 as Circle's answer to SWIFT for stablecoin settlement. It coordinates banks, payment service providers, and fintechs around a single rail: USDC, with optional EURC. Orchestration networks like Bridge.xyz, BVNK, Conduit, Sphere, and Eco take a different approach. They route across many stablecoins (USDC, USDT, PYUSD, USDe, RLUSD) and many chains, optimizing for cost, settlement speed, and liquidity depth rather than membership in one issuer's ecosystem.
​

This article explains what CPN is, how it works, who participates, and where it sits relative to the broader category of stablecoin orchestration. The honest answer in 2026: CPN and orchestration networks are not direct substitutes. They solve adjacent problems for different buyers.
​

CPN is Circle's permissioned coordination layer for regulated financial institutions to settle cross-border payments in USDC. Banks and PSPs join as members, exchange compliance metadata, and route fiat-in to fiat-out flows through USDC as the bridge asset. Circle announced CPN in April 2025 and moved it to general availability later that year.
​

The network was designed around three primitives. First, a directory of vetted institutions with verified KYB and Travel Rule readiness. Second, a messaging standard for compliance data attached to each payment. Third, settlement in USDC on supported chains, with each participant handling its own fiat off-ramp on the receiving side.
​

A sender's bank converts local currency to USDC, sends USDC to the recipient bank or PSP via CPN's compliance-wrapped messaging, and the recipient converts USDC back to local currency for the beneficiary. Circle does not custody funds in transit. CPN provides the rules, the directory, and the messaging layer.
​

Members commit to a service level: confirm receipt within defined windows, attach required Travel Rule data, and report exception handling. The chain choice (Ethereum, Solana, Base, Arbitrum, Avalanche, Polygon, and others on Circle's supported list) is negotiated between counterparties or routed by CPN logic. The actual onchain transfer is a standard USDC transfer or a CCTP V2 burn-mint when crossing chains.
​

Circle's launch partners and early members include Standard Chartered, Deutsche Bank, Société Générale-FORGE, Santander, BNY Mellon (as a custodian participant), and a tier of EMIs and PSPs across LatAm, MENA, and Southeast Asia such as dLocal, Yellow Card, and CoinsPH. The directory has grown to roughly 90 announced participants by Q1 2026, though only a subset are live for production volume.
​

Onboarding is not self-serve. Circle reviews each applicant's licensing, AML program, and operational readiness. That gating is the point: CPN's value to a bank is the assurance that every other counterparty has passed the same bar.
​

Circle has not published a public fee schedule for CPN itself. Members pay standard onchain gas, CCTP V2 fees where applicable, and any FX or off-ramp spread charged by their counterparties. Industry reporting in late 2025 suggested Circle takes a small per-transaction network fee from members on top of these costs, but the exact figures are negotiated and confidential.
​

For comparison, traditional correspondent banking on a corridor like USD to Philippine peso typically costs the originator 3 to 6.5 percent all-in, per World Bank Remittance Prices data. CPN's pitch is single-digit basis points plus FX, not single-digit percent.
​

The simplest framing: CPN is single-issuer and member-gated. Orchestration networks are multi-issuer and API-accessible. CPN optimizes for compliance-grade interbank settlement in USDC. Orchestration networks optimize for routing any stablecoin payment across any chain at the best available cost and speed, often without the sender knowing which asset moved on the wire.
​

Bridge.xyz (acquired by Stripe in 2024 for $1.1 billion) exposes an orchestration API that abstracts USDC, USDT, and PYUSD behind a unified balance and developer-facing endpoints. BVNK runs a similar model for European businesses, with merchant-of-record services layered on top. Conduit focuses on emerging market payouts. Sphere targets B2B invoicing. Eco's Routes product provides cross-chain stablecoin routing where the destination asset and chain are decoupled from the source.
​

The split is real. If you are a bank settling a $50 million corridor flow with another bank, CPN is built for you. If you are a SaaS company collecting USDC invoices from 40 countries on whichever chain the customer's wallet supports, an orchestration network removes friction CPN does not address.
​

Overlap is narrow but real on the payout corridor side. A PSP in Brazil could in theory settle inbound flows via CPN with a US partner bank, or via Bridge.xyz routing USDC over Solana to the same PSP's wallet. The CPN path comes with stronger compliance assurances about the counterparty. The orchestration path comes with chain and asset flexibility, faster integration, and typically lower per-transaction cost for smaller tickets.
​

Several orchestration networks have publicly stated they intend to integrate CPN as one route among many. Bridge.xyz and BVNK both messaged this in 2025. The likely 2026 to 2027 endgame: orchestration networks treat CPN as a high-trust premium rail for large interbank tickets and continue to handle the long tail across multiple stablecoins.
​

Upside: regulated counterparties, standardized Travel Rule data, alignment with Circle's policy posture under MiCA and the GENIUS Act framework discussions. Downside: USDC-only at the asset level (EURC for euro flows is the only other native option), member-gated access that excludes most fintechs and developers, and dependency on Circle as a single coordinating party.
​

For builders allergic to single-issuer lock-in, multi-issuer orchestration is a hedge. See why multi-issuer stablecoin fungibility matters for B2B and Circle Gateway vs multi-issuer routing tradeoffs for the asset-side counterpart of this debate.
​

Many will. A global PSP with bank partners on one side and a developer-facing wallet product on the other has different jobs to do. CPN handles the interbank leg with compliance assurances regulators expect. An orchestration network handles the wallet-facing leg where users hold USDT on Tron, USDC on Base, or PYUSD on Solana and expect their payment to just work.
​

The 2026 stack is rarely either-or. Treasury teams pick CPN for high-value, regulated, USDC-denominated flows. Product teams pick an orchestration network for breadth, speed, and developer ergonomics. The interesting middle ground is policy enforcement at execution time, which is where a stablecoin policy engine sits across both rails.
​

Three questions decide most cases. First: do your counterparties already sit inside CPN, or are they ordinary wallets and businesses? If the latter, CPN does nothing for you. Second: is USDC-only acceptable, or do you need to support USDT, USDe, PYUSD, RLUSD on the corridors you care about? Third: is your integration timeline measured in quarters (CPN membership) or weeks (orchestration API)?
​

For developer teams, start with the broader landscape of Circle alternatives for orchestration before committing. For treasury teams at regulated institutions, CPN's membership conversation is worth starting in parallel with any orchestration evaluation.
​

This article draws on Circle's CPN announcement (April 2025) and developer documentation, public statements from launch partners (Standard Chartered, Deutsche Bank, Société Générale-FORGE, Santander, dLocal, Yellow Card), Bridge.xyz acquisition disclosures from Stripe (October 2024), BVNK product documentation, Conduit and Sphere public materials, Eco product documentation, and World Bank Remittance Prices Worldwide Q4 2025. CCTP V2 details verified against Circle Developer Docs. Reporting on member fees is based on industry coverage where Circle has not published an official schedule; treat fee references as directional.
​