Coinbase and Citi pair virtual accounts with merchant stablecoin conversion

Coinbase and Citi announced two US-first payment initiatives on 28 September 2026: bank-backed funding for Coinbase virtual accounts and stablecoin acceptance for Citi’s institutional merchants. The commercial design connects traditional cash management to digital-asset payment flows without requiring each client to build both sides.[1]

Account numbers do not settle the ownership question

Coinbase, Inc.’s existing US business agreement for third-party applications provides a relevant account model. Deposit instructions fund a digital-asset account held directly with Coinbase; they do not create a separate customer bank account. Converted assets are not FDIC-insured deposits. These general terms do not establish every Citi merchant’s contractual arrangement.[2]

That agreement limits funding to the business’s own money and disclosed purposes, prohibiting use for pooled customer funds or payment facilitation. It preserves customer title to supported digital assets. A platform building services for other businesses therefore needs the appropriate permission structure, rather than relying on an ordinary business account.[2]

Activation and payment completion are separate stages

Coinbase’s deposit-destination guide separates accounts owned by the integrating entity from those owned by an identified customer. Its individual-customer example requires onboarding and active permission to hold fiat; the deposit destination must become active before instructions are shared. Account creation alone does not establish payment readiness.[4]

For the customer-owned route, the guide identifies Citi as the production banking partner and supports ACH and Fedwire funding. Incoming USD can credit an account as USDC or be forwarded to an external blockchain address. Funding must come from the identified customer. The worked examples are simulated; production activation depends on Citi completing provisioning.[4]

Merchant settlement belongs inside the cash-management process

Spring’s existing platform offers direct APIs, hosted checkout and in-app integration. Its bank solution settles into Citi accounts and connects with existing cash-management structures; its reconciliation service consolidates payment data and reports transactions. These are the surrounding treasury capabilities into which the announced acceptance route would fit.[3]

For a merchant, the useful record links the customer’s order, payment confirmation, conversion and bank credit. Each answers a different operational question: whether to fulfil the order, what amount to recognise and when the cash can be deployed. Reconciliation is therefore as consequential as adding another checkout button.[3]

The payout schedule and the price remain commercial terms

Coinbase’s provider agreement allows scheduled withdrawal sweeps and notes bank cut-offs and holidays. The provider’s disclosed charge can include its own fee, Coinbase compensation, network costs and spreads.[2]

A treasury assessment should compare net cash received and the time to bank credit, alongside the integration work removed. Continuous blockchain operation alone does not determine those outcomes. The two announced routes can serve different business needs, so their eligibility, pricing and settlement commitments need to be assessed separately.[3]

Report an error or submit an update