​

Corporate treasury on-ramps move USD into stablecoin using three patterns: ACH pull from a verified business account, wire (Fedwire or SWIFT) into a partner bank's FBO account, or a virtual account at a stablecoin orchestrator. UCC Article 4A governs the wire leg; Reg E/J largely sit at the bank layer, not the onchain leg. KYB sets the timeline.
​

Corporate treasury teams asking "how do we on-ramp into stablecoin at scale" are really asking three questions: which rail, which intermediary structure, and what is the regulatory footprint of each step. This article walks through all three.
​

The treasury team holds USD in a bank account. They want USDC (or USDT, less commonly) at a wallet address they control or at a custody provider. The structural question is: where does the USD land in between?
​

The answer is almost always an FBO account.
​

"For-Benefit-Of" accounts are the standard fintech construct. A partner bank (Cross River, Column, Lead Bank, Customers Bank, others) holds a pooled USD account titled in the on-ramp provider's name, "for benefit of" the end customers. Each end customer is tracked as a sub-ledger inside the provider, not as a separately titled bank account.
​

For corporate treasury on-ramping into stablecoin, the FBO account is where the treasury's USD lands before the stablecoin is minted or transferred. The provider (Circle, Bridge, BVNK, others) holds the float in the FBO, mints or releases the stablecoin to the treasury's wallet, and reconciles against the sub-ledger.
​

The diagram, conceptually:
​

Used for smaller corporate on-ramps, typically under $100K per pull. Provider initiates a debit against the treasury's verified bank account, money lands in the FBO, stablecoin issues to the treasury wallet.
​

Pros: cheap (often free or a few dollars per pull), automatable, fine-grained.
​

Cons: ACH return window is up to 60 business days for certain return codes; providers typically hold the stablecoin issuance for 1 to 5 business days to manage return risk. Bigger amounts face per-day ACH limits and may be split across days.
​

The default for corporate-scale on-ramps. Wire from the treasury bank to the provider's FBO at the partner bank. Settlement is intraday (Fedwire operates 9pm ET Sunday through 7pm ET Friday) and final on receipt.
​

Pros: large amounts (no cap that matters), final settlement, fast.
​

Cons: bank wire fees ($15 to $50 outbound), bank operations hours (no Saturday).
​

Wires fall squarely under UCC Article 4A. The treasury's bank, the receiving bank, and any intermediary banks are governed by Article 4A's payment-order framework. Section 4A-102 sets the subject matter; Section 4A-104 defines funds transfer; case law from Cornell's UCC archive and the Federal Reserve's regulatory references confirms scope.
​

Used when the treasury sits outside the US. SWIFT MT103 from the foreign bank, correspondent chain, eventual credit at the US partner bank's FBO. Slower (T+1 to T+3), more expensive ($30 to $80 plus correspondent deductions), but the only path for many foreign treasuries.
​

UCC Article 4A still applies on the US legs. Foreign legs follow their local equivalents.
​

The 2025-2026 modernization. Providers like Bridge (apidocs.bridge.xyz) expose virtual account numbers that look and feel like regular US bank accounts. The treasury wires or ACH-pushes to the virtual account, the provider auto-issues stablecoin on receipt, settlement is programmatic.
​

Mechanically: still an FBO underneath. The "virtual" part is the per-customer routing/account number that the provider issues so the treasury never has to talk to the partner bank directly.
​

Three pieces.
​

UCC Article 4A, wholesale funds transfers. Governs the bank leg. Final settlement, payment-order acceptance, error resolution, all sit here. Article 4A applies to the wire / ACH from the treasury bank into the partner bank's FBO. It does NOT extend to the onchain stablecoin transfer itself.
​

Reg E (EFTA), consumer protection. Currently does not apply to corporate / business accounts. The CFPB proposed extending Reg E to stablecoin accounts in January 2025; coverage in fintechanddigitalassets.com and BCLP indicated the proposed rule was unlikely to survive an administration change. As of mid-2026 that proposal had not been finalized. Even if it eventually is, Reg E primarily covers consumer accounts, not corporate treasury.
​

Reg J (Federal Reserve), Fedwire and FedNow. Governs the Fedwire side of the bank rail. Bank-leg only; the stablecoin leg falls outside Reg J's scope.
​

UCC Article 12, controllable electronic records. Many states adopted Article 12 between 2023 and 2025. It governs the rights and transfer mechanics of digital assets including stablecoins themselves, not the bank legs. Treasury legal teams should ask their counsel about adoption status in their state.
​

Heavier than the SMB version. The standard 2026 KYB pack for a corporate treasury account:

Clean file: 3 to 10 business days. Complex ownership (multi-jurisdiction holding company, fund structure): 2 to 6 weeks.
​

A frequent operational failure point. Wires need a reference (memo, OBI field) so the provider knows which sub-ledger to credit. Lose the reference and the wire ends up in an unallocated queue.
​

Production rule: every outbound treasury wire to a stablecoin on-ramp carries the provider's unique customer reference in the bank's wire reference field. Standing operating procedure should document the field name per the treasury bank's wire system (Fedwire OBI, SWIFT field 70 for international).
​

Three criteria dominate.

This is the strategic question behind every on-ramp setup. The answer depends on what the stablecoin is for.

The on-ramp infrastructure is the same in all three; the strategic difference is the holding horizon, which the treasury team controls.
​