The term "digital dollars" now appears in GENIUS Act statutory text, treasury committee briefings, and the procurement workflows of Fortune 500 payments teams. It is the institutional rebrand of the payment stablecoin: a tokenized US dollar liability, backed 1:1 by cash and short-duration Treasuries, redeemable on demand, and recorded onchain. As of Q2 2026, USD-pegged digital dollars represent a combined supply of $315.3 billion, with USDT at $187.2B and USDC at $75.6B leading the market.
​

For enterprise buyers, the relevant question is no longer "what is a digital dollar." It is "how do I evaluate, integrate, and operate digital dollar payments at the scale my treasury, AP, and marketplace operations require." That decision involves five distinct infrastructure layers, two markets (primary and secondary), and a regulatory framework that took effect in July 2025. This article walks through each piece in the language of corporate finance and payment operations, not crypto.
​

A digital dollar is a tokenized representation of one US dollar, issued by a regulated entity against reserves held in cash or short-duration Treasuries, transferable on public blockchain networks, and redeemable for one dollar on demand. In enterprise contexts the term refers exclusively to privately issued payment stablecoins, not a central bank digital currency.
​

The distinction from a CBDC is material. A US central bank digital currency would be a direct liability of the Federal Reserve, operating on a government-controlled ledger. As of 2026 the Federal Reserve has published research but has not authorized, piloted at scale, or launched a CBDC. The Federal Reserve's own FAQ confirms no such system is in production. When a treasurer or controller says "settle in digital dollars," the operative instruments are USDC, USDT, PYUSD, USDS, RLUSD, and the broader set of permitted issuer stablecoins.
​

Three properties define the category for an institutional buyer: 1:1 reserve backing with attested audits, settlement finality measured in seconds rather than days, and programmable money movement through smart contract instructions. Each of those properties maps to a line item a CFO or treasury operations lead already cares about: counterparty risk, working-capital velocity, and reconciliation cost.
​

Four enterprise workflows account for the majority of B2B digital dollar volume in 2026: treasury settlement between corporate entities, cross-border accounts payable, marketplace seller payouts, and international contractor or payroll disbursement. Each replaces a specific legacy rail (wires, ACH, correspondent banking, FX brokers) and each has a distinct cost delta and infrastructure footprint.
​

Multinational corporates use digital dollars to move working capital between subsidiaries, vendors, and clearing counterparties without routing through SWIFT messaging and correspondent nostro/vostro accounts. A $10 million intercompany transfer that previously cleared overnight through two correspondent banks now settles in under a minute on a single blockchain network. The infrastructure requirements are institutional custody on both sides, programmable approval thresholds, and a fiat off-ramp at the receiving entity if local fiat is required for downstream operations. Recent BIS analysis documents the magnitude of operational savings available to corporates that displace correspondent-banking flows.
​

A traditional $50,000 international supplier wire carries $15 to $40 in explicit fees, an FX spread of 100 to 300 basis points, and a one-to-three business day settlement window. The same payment denominated in USDC and routed to a supplier wallet on Base or Arbitrum carries network fees under one dollar and settles in seconds. AP teams running 200+ international payments per month see the cost delta compound into six-figure annual savings. Infrastructure requirements: a payments orchestrator that handles chain selection, supplier KYB, and reconciliation reporting back into the ERP.
​

Two-sided marketplaces and creator platforms use digital dollars to disburse to sellers instantly rather than batching weekly ACH or wire runs. Faster payouts directly improve seller retention and reduce platform float. The infrastructure pattern here is typically white-labeled: a custody and routing layer that the platform integrates once, exposing a single API for "pay seller X amount in their preferred stablecoin on their preferred chain."
​

Companies paying contractors in 30+ countries traditionally maintained relationships with multiple local payroll providers and absorbed FX, wire, and intermediary fees on each payment. A digital dollar payroll flow consolidates that into one issuance step and one disbursement step, with the contractor selecting whether to hold the stablecoin, swap to local fiat through an off-ramp, or spend directly through a stablecoin-linked card. Compliance requirements (sanctions screening, 1099 or W-8BEN reporting) are unchanged from fiat payroll.
​

The stablecoin payment system organizes into five distinct layers: issuers (who mint the digital dollar), rails (the blockchains and bridges that move it), orchestrators (which select rails and route value), custodians (which hold balances on behalf of institutions), and applications (the products that surface stablecoins to end users). Every layer except the orchestration layer is consolidating around a small number of regulated incumbents.
​

For enterprise integration teams, this mental model matters because it determines what to buy versus build versus partner for. The five layers are functionally distinct, each operates under different regulation, and a single vendor rarely covers more than two layers without making compromises.
​

Layer 1: Issuers. Regulated entities that mint and redeem digital dollars against reserves. Circle (USDC), Tether (USDT), PayPal (PYUSD), Sky (USDS), Ripple (RLUSD), Paxos (USDG, USDP), and bank-affiliated issuers such as the depository-institution subsidiaries permitted under the GENIUS Act sit here. Issuers compete on reserve quality, audit cadence, and chain coverage.
​

Layer 2: Rails. The public blockchains that record stablecoin balances and the bridges or messaging protocols that move them between chains. Ethereum, Solana, Tron, Base, Arbitrum, Polygon, and BNB Chain together hold the majority of stablecoin supply. LiFi, LayerZero, and Circle's CCTP operate as the messaging infrastructure for cross-chain transfer.
​

Layer 3: Orchestrators. Neutral aggregators that abstract the issuer and rail layers behind a single integration. An orchestrator selects which stablecoin, which chain, and which routing path to use based on cost, settlement time, and counterparty preference. This is the layer Eco occupies. The institutional value proposition of an orchestrator is integration consolidation: one KYB process, one API, one reconciliation feed, across every issuer and rail an enterprise might need to reach.
​

Layer 4: Custodians and fund management. Regulated custodians holding stablecoin balances on behalf of institutional clients with insurance, access controls, and audit. Fireblocks, Anchorage Digital, BitGo, and Coinbase Custody are the dominant providers. Treasury operations and asset management workflows live here.
​

Layer 5: Applications. The products that surface digital dollars to end users: payment processors, neobank apps, payroll platforms, marketplace checkout, treasury dashboards. Stripe, Bridge, and Mercury are examples. Applications integrate the layers below them to deliver a finished product.
​

Eco positions as the neutral orchestration layer in this stack: enterprises integrate once and reach every issuer, every rail, and every supported custodian without rebuilding for each new endpoint. The layered model is the canonical framework for evaluating where any given vendor fits and what gaps remain in a buyer's payments architecture.
​

Primary stablecoin markets are where new digital dollars are minted directly with an issuer against a fiat deposit, and where existing tokens are redeemed back to fiat. Secondary markets are the onchain venues (decentralized exchanges, automated market makers) and offchain venues (OTC desks, RFQ networks) where stablecoins already in circulation trade between holders. The distinction shapes pricing, slippage, and counterparty risk.
​

Primary access. Mint and redemption sit behind issuer KYB. A treasury team that wires $25 million to Circle receives newly issued USDC at par, with no spread. The constraints are operational: minimum sizes, settlement windows tied to the issuer's banking partners, and the time required to complete onboarding. For institutional-scale flows, primary access is the lowest-cost path.
​

Secondary access. Onchain venues such as Uniswap, Curve, and 1inch quote stablecoin-to-stablecoin and stablecoin-to-other-token markets continuously. Offchain venues such as B2C2, Cumberland, and Wintermute quote larger blocks through RFQ. Secondary access is faster than primary but introduces spread, slippage, and inventory risk that vary by venue and size.
​

Sophisticated institutions blend both. A $100 million payment may route partial-mint through Circle and partial-secondary through OTC inventory, depending on which path clears at lower all-in cost. A neutral orchestrator with both primary mint access and onchain plus offchain liquidity is the only configuration that can run best-execution analytics across that decision. This is the gap most issuers and DEX-only aggregators cannot fill on their own.
​

Enterprises buying digital dollar infrastructure face three primary architectural options: integrate directly with an issuer such as Circle or Bridge, integrate through a neutral orchestration layer, or rely on a custody-only relationship with a regulated custodian. Each path covers different layers of the stack, exposes different counterparty configurations, and produces different operational footprints. The right choice depends on volume, chain footprint, and how many issuers the enterprise needs to touch.
​

The table below summarizes the trade-offs.

In practice most enterprises end up combining paths: a custodian for balance sheet, an orchestrator for movement and routing, and direct primary access at one or two large issuers for the lowest-cost mint at scale. The architectural mistake is assuming any single vendor covers all three.
​

The Guiding and Establishing National Innovation for US Stablecoins Act became law on July 18, 2025, and established the first federal regulatory regime for payment stablecoins in the United States. Enterprise buyers do not directly hold issuer-level obligations under the statute, but their counterparty diligence list expanded substantially. Treasury, legal, and procurement teams should confirm each of the following before contracting with a digital dollar provider.

Implementing regulations are due by July 2026 with full effect by January 2027. Enterprise procurement teams should treat the current window as the compliance ramp and document diligence for issuers and orchestrators before that deadline.
​

Evaluating a digital dollar is not a feature-comparison exercise across USDC, USDT, and PYUSD. It is a structured assessment along four dimensions that determine fit for a given enterprise workflow: reserve quality, redemption SLA, chain coverage, and primary mint access. Buyers who score candidates on these dimensions consistently arrive at better procurement decisions than those who default to the largest-supply token.
​

Reserve quality. Composition (cash vs Treasuries vs commercial paper), duration, custodian identity, and attestation frequency. Tier-one reserves are 100% cash and short-duration T-bills custodied at a regulated US bank with monthly attestation by a Big Four auditor.
​

Redemption SLA. The committed time and minimum size for converting digital dollars back to USD in a bank account. T+0 redemption at any size is the institutional gold standard; T+1 with size minimums is acceptable for most enterprise workflows; longer windows raise liquidity risk that should be priced in.
​

Chain coverage. The set of blockchains where the stablecoin is natively issued (not bridged). Native issuance avoids bridge counterparty risk and reduces routing complexity. A buyer that needs Ethereum, Base, Arbitrum, Polygon, and Solana should require native issuance on each.
​

Primary mint access. The KYB process, minimum mint size, and settlement window for direct primary access. Enterprises moving $10 million or more per month should prioritize issuers that grant primary access; for smaller flows, secondary-market liquidity through an orchestrator's RFQ network is typically sufficient.
​

A rubric-based evaluation produces a defensible answer to "which digital dollar should we use for which workflow" and surfaces gaps that a single-issuer integration cannot close.
​

Integration follows a four-step pattern: select the issuer or orchestrator counterparty, complete KYB and contracting, integrate the API or SDK into existing ERP/treasury/payment systems, and run a parallel production-shadow test before cutting over live volume. Most enterprises complete the technical work in four to twelve weeks; the diligence and contracting timeline depends on the buyer's internal compliance process.
​

The integration surface area depends on which architectural path the buyer selected. Issuer-direct integrations require building chain-aware logic in-house: which network to send on, how to handle gas, how to confirm finality, how to reconcile against existing payment records. Orchestrator integrations push that complexity into the orchestrator's API, leaving the enterprise to call a single endpoint such as "pay this counterparty this amount in this stablecoin on their preferred chain" and receive a structured confirmation back. EIP-7683 formalizes the cross-chain intent pattern that orchestration layers rely on.
​

Programmability is the operational unlock that legacy rails cannot match. Conditional release based on delivery confirmation, automated multi-party splits, escrow that times out and refunds, recurring payments that adjust to an external price feed: each of these is a smart-contract instruction attached to a digital dollar transfer. this article covers the design patterns in depth.
​

Three trends will define the digital dollar market over the next 18 months: GENIUS Act implementation regulations taking full effect by January 2027, deeper integration between regulated custodians and onchain settlement, and the consolidation of cross-issuer orchestration as a distinct infrastructure category. Enterprise buyers should expect the supply distribution to broaden as bank-affiliated issuers enter the market and the share concentration of the top two issuers softens.
​

Bank-affiliated issuance. Under the GENIUS Act, subsidiaries of insured depository institutions may issue payment stablecoins. Expect several large US banks to launch dollar tokens in 2026 and 2027, alongside non-US bank issuance under MiCA in the EU and the Stablecoin Bill in Hong Kong.
​

Cross-issuer refungibility. The market is moving toward institutional-grade ability to convert between any two regulated dollar tokens at near-zero spread at primary-market scale. Orchestration layers with both mint access and aggregated secondary liquidity are building toward this functionality; it is not yet a shipped product across the market.
​

Best-execution analytics. Institutions will increasingly demand reporting on whether their last $100 million of stablecoin flow cleared at competitive spread versus open-market benchmarks. This is the analog of TCA reporting in equities and FX, applied to digital dollar settlement.
​

Programmable corporate treasury. Treasury teams are beginning to encode payment policy directly into onchain instructions: dual-control approval, dynamic counterparty limits, automated sweep into yield-bearing tokenized Treasuries. This is where digital dollars structurally separate from wires and ACH; the divergence will accelerate through 2027.
​

Common questions from enterprise buyers evaluating digital dollar infrastructure cluster around regulatory status, CBDC comparison, settlement performance, and integration scope. The answers below reflect the post-GENIUS Act operating environment as of mid-2026.
​

Yes. The GENIUS Act, enacted July 18, 2025, established federal regulation for payment stablecoins. Permitted issuers must maintain 1:1 reserves, publish monthly attestations, submit to annual audits, and comply with Bank Secrecy Act obligations. Implementing regulations are due by July 2026 with full effect by January 2027.
​

Digital dollars are issued by regulated private entities and circulate on public blockchains. A US CBDC would be issued by the Federal Reserve on a government-controlled ledger. As of 2026 no CBDC has been authorized or piloted at scale in the US, and pending legislation in both chambers of Congress explicitly restricts the Federal Reserve from issuing one without statutory authorization.
​

Settlement finality depends on the underlying blockchain. On Solana, Base, Arbitrum, and Polygon, payments reach economic finality in seconds. On Ethereum mainnet, finality completes within 12 to 15 minutes. This compares to one to three business days for international wires and one to two business days for ACH.
​

At minimum: a custody relationship for holding balances, an orchestration or issuer-direct integration for movement, AML and sanctions screening, and reconciliation back into the ERP or treasury system. Multi-chain or multi-issuer flows require an orchestration layer to avoid building chain-aware logic in-house.
​

USDC, USDT, PYUSD, USDS, and RLUSD are all digital dollars. The term is an umbrella for the category of USD-backed payment stablecoins. Differences between specific tokens come down to issuer, reserve composition, chain coverage, and redemption terms, which is why an evaluation rubric matters more than picking the largest-supply token by default.
​

https://eco.com/support/en/articles/14747316-the-stablecoin-infrastructure-stack provides a companion deep-dive on the operational architecture supporting digital dollar payments at enterprise scale.
​