01 Trigger Event

On November 11, according to people familiar with the matter, Goldman Sachs, Citi, Santander, Deutsche Bank, and 19 other financial institutions plan to invest approximately $270 million to support the first five years of operations of the joint stablecoin project Project Faro. The project is expected to establish an issuing entity in the United States and launch its product in the first half of 2027.

The $270 million is not merely a product development budget. It is startup capital sufficient to cover issuance, reserve operations, compliance, and initial distribution. What the participants intend to aggregate is not a new blockchain, but the liquidity, payment infrastructure, and customer relationships of traditional financial institutions.

I could not confirm the final allocation of funds or the complete participant list, so I cannot assume that the $270 million would be divided equally among the 21 institutions. But one thing is clear: this is no longer a fintech company's all-or-nothing experiment. It is a collective bet by financial institutions on a new layer of money distribution.

02 What This Really Means

The issue is not that “another stablecoin is coming,” but who is positioned to become the default distribution channel for dollar stablecoins.

Tether and Circle's moat has never been based on code alone. USDT's first-mover network effects, exchange depth, merchant coverage, and cross-border liquidity, together with the USDC distribution Circle built through Coinbase, created a reinforcing cycle between usage frequency and liquidity.

But banks control bank accounts, payroll payments, cross-border settlement, corporate treasury, and compliance access. These channels are far larger than crypto-native channels. The historical problem was not a lack of potential users, but a lack of unified issuance and clearing infrastructure.

Project Faro seeks to aggregate dispersed banking resources onto a single stablecoin network. This is a direct application of aggregation theory to payment infrastructure: an individual bank's stablecoin may not have a moat, but a dollar token backed by 21 banks could achieve higher switching costs.

That is what the $270 million should actually be understood to purchase. It buys the fuel to start a liquidity flywheel, not market share in itself.

That said, I have not tested the project's internal reserve, redemption, or settlement architecture and cannot confirm whether it will use full reserves, regulated issuance, permissioned validation, or a hybrid structure. The lack of transparency does not change the strategic assessment at the distribution layer, but it will affect the risk profile.

03 Historical Analogy / Structural Comparison

The more useful structural comparison to the structure before the 2008 financial crisis is not “banks issuing internet money,” but payment networks shifting from closed systems to open interfaces.

Visa and Mastercard did not replace banks; they became the common rail for transfers between them. PayPal did not replace bank accounts; it became the interface through which individuals paid merchants. AWS did not replace enterprise data centers either; it abstracted computing capacity, allowing startups to operate without first purchasing servers.

Project Faro occupies a similar position: banks may retain accounts and customer relationships while using tokens as a cross-institution settlement interface.

The distinction from Tether and Circle is also important. Existing stablecoins first built crypto-native liquidity and then expanded into traditional payments. Project Faro is attempting to reverse that sequence, starting with institutional balance sheets and payment customers before seeking crypto-native usage.

This could produce ecosystems centered in two directions:

  • One begins with on-chain traders, DeFi, and cross-border payments, with dollar liquidity at its center.
  • The other begins with bank customers, payroll, and corporate treasury, with compliance and fiat distribution at its center.

Whoever can bring users from the other side into their ecosystem may become the leading gateway in the next round of dollar stablecoin competition.

The 2014 AWS analogy offers another lesson: once an infrastructure platform emerges, developers may not remain loyal to the original cloud brand. They may choose the cheapest, most convenient, and most compatible operating environment. Stablecoins may develop similar provider-agnostic routing. Users choose a dollar token, not the logo of its parent company.

The analogy has limits, however. Payment networks operate under mature legal, reserve, and clearing rules. Stablecoins also layer crypto regulation, monetary policy, and bank competition on top of those requirements. Whether Project Faro can succeed depends not only on technology and capital, but on whether regulators allow these banks to share customer and payment resources.

04 What It Means for AI Builders

The first decision to revisit this week is to remove “stablecoin = crypto payment feature” from the infrastructure roadmap. For teams providing APIs, agent payment capabilities, or AI SaaS, a stablecoin is more likely to serve as a cross-border settlement layer than as another way to accept payments.

If Project Faro launches in 2027, banks' payroll, merchant acquiring, and corporate treasury channels could give AI products their first opportunity to enter real payment flows through existing financial relationships. The challenge is not whether an AI product can generate an invoice, but whether that invoice can automatically become a verifiable, traceable token that can be settled across institutions.

The second decision is to reassess the sequencing of fintech and AI integration. Over the past two years, many teams have treated stablecoins as an add-on capability for AI agents, such as using tokens to call external APIs. A more viable path may be to capture the transaction workflow first: AI identifies expenses, matches invoices, processes refunds, and reconciles accounts, while stablecoins handle only the final value transfer.

The third decision is not to hard-code a single stablecoin into a product's core abstraction. A joint bank issuance means the dollar token market may remain fragmented. AI billing, agent treasury, and cross-border SaaS should use a payment router to handle issuers, networks, fees, redemption, and liquidity, rather than exposing customers directly to USDT or USDC address models.

For model access and token gateway platforms such as opc.club, the important development to watch is not stablecoin issuance itself, but whether a combined “usage-based billing + cross-border settlement” model emerges. If AI inference costs can be settled automatically through stablecoins, model usage could shift from monthly enterprise invoicing to instant, API-usage-based payment. The real moat may not come from supporting one more payment protocol, but from integrating payment, metering, routing, and reconciliation into a closed loop.

05 Counterargument / Risks

I may be overestimating traditional banks' execution capabilities.

Financial institutions are generally better at reproducing existing processes than creating new interfaces. Project Faro involves data isolation, customer authorization, cross-bank liquidity, ownership of reserve assets, and profit sharing. Each bank wants to retain its customer relationships and may be reluctant to surrender control over distribution.

More seriously, a bank-backed stablecoin may be a defensive move rather than an offensive one. Large institutions are more likely to launch multiple regulated tokens to preserve compliance access than to share a genuinely unified network. Although there may be 21 participants, the actual operating model could still consist of 21 isolated closed loops.

This is where my judgment may be mistaken: the $270 million demonstrates that banks are willing to place a bet, not that they are willing to aggregate. If every bank must provide guarantees, capital, and customer channels, the supposed joint project may ultimately remain a consortium rather than become winner-take-all infrastructure.

Regulation could also become the decisive constraint. If the U.S. stablecoin framework requires 100% cash or short-term Treasury reserves, daily redemption, and strict segregation of custody, the issuing entity will resemble a bank liability more than a crypto-native dollar substitute. Project Faro's room for innovation may therefore be narrower than crypto-native teams expect.

Tether and Circle will not stand still, either. Mature stablecoins have deeper liquidity, broader on-chain integrations, and more developed redemption networks. Even with bank distribution, a new entrant must solve the hardest cold-start problem: few people want to hold a token that can be used only with a small group of banks.

My current conclusion is not that Project Faro will defeat Tether and Circle. It is that the project will test whether financial institutions can extract payment distribution from separate, closed-ended products. The outcome of that test is more valuable than the project's name.