Coinbase Is Becoming the Stablecoin Infrastructure for US Banks

When banks adopt stablecoins, who builds the plumbing? The obvious answer is the banks themselves. They have the regulatory frameworks, the client relationships, and the engineering teams. But building stablecoin infrastructure means managing blockchain wallets, monitoring on-chain settlement, and running conversion systems that bridge two different financial worlds. That's a different business from taking deposits and making loans. So the banks are outsourcing it to the company they spent years pretending didn't exist.

On November 9, PNC Bank announced that its corporate and institutional clients can now receive USDC payments, automatically converted to dollars and deposited into their PNC accounts. The infrastructure underneath is Coinbase's. Six weeks earlier, Citi announced almost the same thing: stablecoin acceptance through Spring by Citi, powered by Coinbase Payments, with Citi settling as the bank of record.

On the same day as the PNC announcement, the OCC granted Coinbase an unconditional national trust charter. Coinbase National Trust Company can now provide federally regulated custody, settlement, and stablecoin reserve management.

Those three events in six weeks tell one story. Coinbase is becoming the stablecoin infrastructure layer for US banks, the same way Stripe became the payments layer for internet companies, by handling the part that banks don't want to build themselves.

What the banks are actually buying

PNC's press release spells it out. Eligible corporate clients receive payments in USDC on the Ethereum blockchain. Coinbase Payment APIs handle the receipt and conversion. The stablecoins are automatically converted 1-to-1 into US dollars and deposited into a designated PNC deposit account.

From the corporate client's perspective, a stablecoin payment looks like any other incoming payment: it arrives as dollars in their bank account. From PNC's perspective, they never hold USDC on their balance sheet, never manage blockchain wallets, and never deal with on-chain settlement directly. Coinbase handles all of that.

Tom Lang, PNC's head of treasury management product and operations, described it as "testing and learning." That framing matters. PNC positioned this as a complement to its existing faster-payments capabilities, not a replacement. Stablecoin is one more way for corporate clients to receive money, alongside ACH, RTP, and wire.

Citi's version is structurally similar but slightly broader. Spring by Citi, their payment acceptance platform for merchants, integrates Coinbase Payments so institutional clients can accept stablecoins at checkout. The conversion happens automatically, and Citi settles as the bank of record. Brett Tejpaul, Coinbase's head of institutional, described the arrangement as giving "Citi's institutional clients easy, low-friction stablecoin acceptance" without either side building systems they don't need.

So two of the ten largest US banks, PNC at roughly $600 billion in assets and Citi at roughly $2.5 trillion, now use the same Coinbase Payment APIs for stablecoin acceptance. Both auto-convert to fiat. Both position it as a complement to existing payment rails. Neither holds stablecoins on their own balance sheet.

Why banks buy instead of build

Banks are also building their own stablecoins. A 21-institution consortium is creating a controlled token backed by member deposits, running on its own infrastructure, settling within its own regulatory framework. The Zelle pattern applied to stablecoins.

The PNC-Coinbase deal is the opposite side of the same question. Instead of building a stablecoin or issuing one, PNC is buying infrastructure to accept an existing one. They didn't create a new token. They plugged into USDC through Coinbase's API.

The reasons are straightforward. Building stablecoin infrastructure requires blockchain wallet management, on-chain monitoring, compliance tooling for digital asset transactions, and conversion infrastructure for fiat settlement. A bank could build all of that internally, but the regulatory complexity alone would take years. Coinbase already has it.

Think of it like a restaurant adding delivery. The restaurant knows how to cook and it knows its customers, but building a fleet of delivery drivers, a tracking system, and a logistics operation is a different business entirely. So the restaurant contracts with a delivery platform that already built all of that.

The food still comes from the restaurant's kitchen, and the customer still pays the restaurant. The delivery platform handles the part in the middle. That's Coinbase's role here.

What the trust charter changes

Coinbase's OCC trust charter, approved as unconditional on November 6, changes the compliance math for every bank evaluating a Coinbase partnership.

Before the charter, Coinbase was a crypto exchange with state licenses. It held a New York BitLicense from NYDFS since 2017 and a New York limited-purpose trust charter since 2018. But from a bank compliance officer's perspective, routing payments through a state-licensed crypto company introduced regulatory friction. Different regulators in different states, no single federal framework.

The national trust charter puts Coinbase under OCC supervision alongside every other national bank and trust company in the country. Rick Schonberg, CEO of Coinbase National Trust Company and head of trading and custody, told Banking Dive that "the regulators actually make us better at what we do." He previously held roles at JPMorgan Chase, Goldman Sachs, and State Street before joining Coinbase, bringing a traditional finance perspective to a crypto-native company.

The charter allows Coinbase to provide digital asset custody, settlement, and stablecoin reserve management under a federal framework. It does not make Coinbase a full-service bank. Coinbase National Trust Company cannot take deposits or extend loans. But for the services banks actually need from Coinbase, specifically custody and stablecoin payment infrastructure, the charter provides the regulatory cover that makes partnership decisions easier.

Coinbase is the latest in a wave of crypto-native firms pursuing OCC trust charters after the GENIUS Act cleared a path for federal trusts to participate in stablecoin issuance and custody. Ripple received its full trust charter in October 2026. Circle and BitGo also hold charters. The OCC has embraced these applications under the current administration, though the Independent Community Bankers of America sued the OCC in October 2026, arguing that the agency overreached its authority in granting trust charters to crypto firms.

If ICBA prevails, the regulatory foundation under these bank-crypto partnerships gets less certain. But for now, the charter is the cleanest regulatory signal a crypto company can send to a bank's compliance team.

The pattern underneath

The PNC and Citi deals share a specific architecture: Coinbase provides the stablecoin infrastructure, the bank provides the client relationship and fiat settlement, and the client never touches crypto directly. The bank's balance sheet stays clean while the client's experience stays familiar.

This is how infrastructure layers get established. Stripe didn't compete with banks for merchant accounts; it built the API layer that made online payments work and let platforms plug in, the same way AWS built the compute layer instead of competing with enterprise IT departments.

Coinbase is doing the same thing with stablecoins. It built the conversion, custody, and settlement infrastructure, and it's letting banks plug their clients into it. The bank keeps the client relationship, and Coinbase keeps the infrastructure revenue.

PNC's partnership with Coinbase started in December 2025 with crypto trading for private bank clients. Six months later, they expanded to stablecoin payments for corporate clients. Citi's expanded from institutional custody to merchant stablecoin acceptance through Spring by Citi. Both relationships started narrow and widened.

If this pattern holds, the next step is outgoing stablecoin payments, not just incoming. PNC's pilot only covers receiving USDC. Corporate treasury teams that want to send stablecoin payments to suppliers or international counterparties would need the other direction. Coinbase's Payment API infrastructure could support that, but neither PNC nor Citi has announced it.

What this means for the stablecoin stack

Two things are happening at the same time in bank stablecoin strategy, and they point in different directions.

On one side, a consortium of 21 financial institutions including PNC, Citi, Wells Fargo, and Bank of America is creating its own stablecoin for interbank settlement, a closed-loop token expected in the first half of 2027. On the other, PNC and Citi are plugging into USDC through Coinbase for client-facing payment acceptance, an open token on public rails for general commerce.

PNC is doing both. It joined the consortium to build a bank-controlled stablecoin for interbank settlement, and it partnered with Coinbase to accept USDC from corporate clients today. That's not a contradiction. The consortium handles settlement between member banks. USDC acceptance through Coinbase handles inbound payments from anyone.

But the partnership side has momentum. Two major deals in six weeks, and Coinbase's trust charter removes the biggest regulatory objection. Mastercard acquired its way into the stablecoin stack. Stripe took the acquisition route through Bridge. Coinbase is taking the partnership route, the AWS model rather than the vertical integration model.

The question for 2027 is whether Coinbase's infrastructure play can scale beyond pilots. PNC's program is limited. Citi's is broader but still new. The underlying architecture, Coinbase Payment APIs converting USDC to fiat through bank settlement, works at small volumes. Whether it works at the scale of PNC's $600 billion in assets or Citi's $2.5 trillion is the engineering question nobody has answered yet.