Citi and Coinbase Expand Stablecoin Payments for Business
Citi and Coinbase have announced a significant expansion of their partnership, launching two complementary products that bring two-way stablecoin payment rails directly to US corporate clients. For accounting firms, CFOs, and auditors advising businesses that touch payments infrastructure, the deal is not merely a fintech headline: it creates concrete stablecoin accounting obligations that need to be addressed before the first transaction settles.
What the Expanded Partnership Actually Does
The two firms first announced a collaboration in October 2025, focused broadly on fiat-to-crypto payment infrastructure. The September 2026 expansion goes further, introducing two distinct product tracks that operate in opposite directions across the fiat-stablecoin boundary.
Track One: Coinbase Virtual Accounts Powered by Citi
Coinbase will use Citi's Virtual Account Wallet infrastructure to underpin its own Virtual Accounts product. In practice, a business customer receives what looks and behaves like a standard bank account. Incoming fiat funds are automatically converted into stablecoins on the back end. The customer can accept, hold, and pay in fiat-denominated terms while the underlying asset is digital. The conversion happens without the merchant needing to actively manage a crypto wallet or directly hold stablecoins at any visible layer of the product.
Track Two: Spring by Citi Accepting Stablecoin Payments
Running in the opposite direction, Citi's institutional clients using its Spring by Citi platform will be able to accept stablecoin payments from counterparties. Coinbase handles the stablecoin payment rails, and once received, automatically converts the digital assets into fiat for final settlement. Again, the institutional client sees a fiat outcome without needing to operate a stablecoin custody arrangement directly.
Both products are launching initially in the United States and are explicitly designed to give businesses bank-account-like functionality, using stablecoins as the settlement layer rather than the customer-facing instrument.
Why the "No Direct Holding" Design Does Not Simplify Accounting
The marketing framing emphasises that merchants and corporate clients do not need to "directly hold or manage digital assets." That is operationally true, but it is not a clean pass on accounting or tax treatment. US GAAP and the IRS both look at economic substance, not product branding.
When Does the Conversion Event Occur?
Under FASB's ASC 350-60, which introduced fair-value accounting for certain crypto assets, the critical question is whether the entity ever recognises the stablecoin on its balance sheet, even momentarily. If fiat enters the system and is converted to a stablecoin before being transferred or used, there is a discrete moment at which the entity holds a crypto asset. That moment creates a recognition event. Similarly, on the Spring by Citi track, the stablecoin received from a counterparty is a digital asset at the point of receipt, even if it converts to fiat within seconds. The fair value at the instant of receipt is the tax and accounting basis.
Stablecoin Classification Under ASC 350-60
Stablecoins pegged to the US dollar generally trade very close to a one-to-one ratio, so the unrealised gain or loss under fair-value accounting is often immaterial. However, "often immaterial" is not the same as "zero." Firms need a documented policy addressing how they classify each specific stablecoin used, whether it qualifies as in-scope under ASC 350-60, and at what frequency they mark it to market. A high-volume payments operation that cycles through stablecoins thousands of times a month will accumulate small mark-to-market entries that can become material in aggregate if not tracked systematically within the firm's digital asset accounting software.
Tax Basis at Conversion
The IRS treats stablecoins as property, consistent with its long-standing position on crypto assets. Each conversion from fiat to stablecoin, and from stablecoin to fiat, is a taxable exchange. Where the conversion happens instantaneously and the stablecoin maintains its peg, the gain or loss may be negligible. But the obligation to record the basis, calculate the gain or loss, and report it does not disappear because the product has been designed to abstract away the stablecoin layer. Firms using either Coinbase Virtual Accounts or the Spring by Citi acceptance feature need data feeds from those platforms that capture the timestamp, the amount, and the exchange rate at each conversion event. Without that data, the crypto bookkeeping software cannot produce a defensible tax position.
Treasury and Operational Considerations for Corporate Clients
Counterparty and Settlement Risk
Both products sit between two large, regulated institutions. Citi is a globally systemically important bank, and Coinbase is a publicly listed, regulated crypto exchange. For corporate treasury teams assessing counterparty risk, this is a materially different profile from using a pure-play crypto payments provider. That said, the stablecoin settlement layer introduces its own risk profile. Firms should understand which specific stablecoin underpins each product and verify that the reserves backing it are subject to regular attestation. For context on what can happen when stablecoin issuers intervene in transactions, the coverage of stablecoin accounting and the AML implications of issuer freezes is relevant reading for treasury counsel.
Reconciliation Complexity at Scale
A business processing hundreds or thousands of payments daily through either product will generate a ledger in which every settlement period contains a series of fiat-in, stablecoin-held, fiat-out transactions. The nominal values may be near-identical given peg stability, but reconciliation still requires matching each conversion to a bank statement line, a stablecoin receipt, and a final fiat settlement. Firms relying on traditional accounts-payable and accounts-receivable workflows will find that standard bank feeds do not capture the intermediate stablecoin step. Dedicated digital asset accounting software or a well-structured API integration with the Coinbase and Citi data is not optional at volume, it is a basic audit-readiness requirement.
AML and Transaction Monitoring
Corporate clients are not exempt from AML obligations simply because the stablecoin conversion is handled by a licensed intermediary. Banks and crypto exchanges performing the conversion act as money transmitters or financial institutions with their own AML programmes. However, the corporate client still has responsibilities under its own compliance framework, particularly if it is a regulated entity itself. The underlying transaction data that flows through these rails needs to be retained in a form that supports a transaction monitoring review. Firms should confirm with their compliance teams what data Citi and Coinbase provide, and whether it is sufficient for the client's own AML records.
Implications for Accounting Firms and Auditors
Client Readiness Assessment
For accounting firms advising corporate clients, the Citi-Coinbase expansion is a signal that mainstream stablecoin payment rails are arriving in the enterprise segment, not just in crypto-native businesses. Any client operating a US payments function should be assessed now for whether they are, or are likely to soon be, touching stablecoin-denominated settlements. That assessment should cover four areas: accounting policy for crypto assets under US GAAP, tax reporting obligations for each conversion event, reconciliation capability in the current tech stack, and AML record-keeping for stablecoin transactions.
Audit Trail Requirements
Auditors reviewing financial statements for clients using these products will need to obtain sufficiently detailed transaction data to verify that each conversion event has been recorded at the correct fair value, that gains and losses have been calculated accurately, and that the balance sheet does not carry stablecoin balances that have not been properly classified. The "automatic conversion" feature marketed by both products does not mean the conversion is invisible to the auditor. It means the auditor needs to look one layer deeper into the platform data to find it.
Policy and Disclosure
Clients adopting either product for the first time will need to update their accounting policy notes for crypto assets, even if the practical impact is immaterial in the first period. Disclosure requirements under ASC 350-60 are specific, and a clean audit requires that management has made an affirmative determination about classification and measurement rather than assuming that "auto-converted" stablecoins fall outside the scope of crypto asset accounting. With the broader US stablecoin regulatory framework still evolving, firms should also stay current on legislative developments. The analysis of how the CLARITY Act stall affects stablecoin accounting frameworks sets useful context for where federal oversight may land and what that means for product-level compliance.
What Comes Next
Both products are launching in the US first, with broader geographic expansion implied but not yet specified. For firms advising US clients, September 2026 is the relevant start date for assessing exposure. The partnership builds on a foundation that Citi and Coinbase established in October 2025, and the speed of the follow-on expansion suggests both institutions see this as a platform rather than a pilot. Citi's head of payments, Debopama Sen, described the goal as building "the next generation of payments infrastructure, one that is seamless, interoperable, and operates across both traditional and digital payments instruments and networks." That framing points toward further product development rather than a static offering.
For accounting and finance professionals, the practical implication is that stablecoin accounting is no longer a niche consideration for crypto-native clients. It is becoming a default feature of enterprise payments infrastructure offered by the largest US banks. Firms that do not have a documented approach to crypto asset classification, tax basis tracking, and audit trail management for stablecoin transactions need to build one now, before their clients start transacting at scale.
Frequently Asked Questions
Does a business using Coinbase Virtual Accounts need to recognise stablecoins on its balance sheet?
Potentially yes. If incoming fiat is converted to stablecoins before the funds are used or transferred, the entity may hold a crypto asset at that interim point, which creates a recognition obligation under ASC 350-60. The answer depends on the precise moment of conversion and whether the entity has control of the stablecoin, even briefly. Legal and accounting advice specific to the product's mechanics is needed.
Is the fiat-to-stablecoin conversion a taxable event?
Under current IRS guidance, converting fiat to a stablecoin, and converting back, are both taxable exchanges. Where the stablecoin maintains its peg, the gain or loss will typically be negligible, but the obligation to record and report each event remains. High-volume operations need automated data capture to meet this requirement.
Which stablecoin underpins these Citi-Coinbase products?
The source reporting does not specify a single stablecoin. Coinbase's primary stablecoin is USDC, issued by Circle, but firms should confirm with Citi and Coinbase directly which asset or assets are used within each product before making accounting policy decisions.
What data should firms request from Citi and Coinbase for audit purposes?
At a minimum, firms need timestamp-level transaction data showing each conversion event, the amount converted, the exchange rate applied, and the final settled amount. This data needs to integrate with or be importable into the firm's crypto accounting software so that each event can be matched to ledger entries and supporting documentation.
How does this affect a client's existing AML programme?
Using a licensed intermediary to handle stablecoin conversions transfers some AML obligations to that intermediary, but it does not eliminate the corporate client's own record-keeping and monitoring responsibilities. Clients that are regulated entities should review whether the transaction data provided by Citi and Coinbase is sufficient for their own AML compliance documentation, and update their transaction monitoring policies accordingly.
Source: The Block