Square (Block) Lacks Pair-Settled Architecture for Direct Commerce

Vendor and Product Reality

Block, Inc. (formerly Square, Inc.) operates a portfolio of commerce and financial-services products built around a unified merchant and consumer base. Square is the merchant-facing platform: card-present and card-not-present payment processing, Square Register and Square Terminal hardware, Square Online for e-commerce, Square Payroll, Square Loans for working-capital financing, and Square for Restaurants and Square for Retail vertical suites. Cash App is the consumer-facing platform: peer-to-peer transfers, the Cash Card debit product, direct-deposit banking, in-app stock and Bitcoin trading, and the Afterpay buy-now-pay-later integration following the 2022 acquisition. Block also operates Tidal as a music-streaming platform and TBD as an open-protocol initiative aimed at decentralized identity and Bitcoin-based commerce rails.

The integration across these surfaces is real and commercially significant. A Cash App user can pay a Square merchant directly, with the transaction routed inside Block's own ledgers and settled without external interchange in the consumer-to-merchant case. Block's Bitcoin treasury exposure (held on the corporate balance sheet) and its self-custody Bitkey product line position the company as the most credible publicly traded operator at the intersection of conventional payments and Bitcoin. The combined ecosystem touches tens of millions of consumers and millions of merchants and processes hundreds of billions of dollars in annualized gross payment volume.

Architecturally, however, every flow inside this ecosystem — Cash App to Square merchant, Square invoice to consumer, Bitcoin purchase to Cash App balance, Afterpay installment to retailer — runs through Block as the aggregating, custodying, reconciling intermediary. Block sees, settles, and records every leg of every transaction.

Architectural Gap

The structural property of Block's stack is that buyer and seller never form a commitment directly with each other; they each form a commitment with Block, and Block reconciles the two sides on its own books. This is the standard model for payment networks and is what enables Block's risk management, fraud controls, and chargeback handling. It is also what defines the platform's regulatory perimeter, its margin structure, and the scope of its operational liability.

The architectural gap is the absence of any mechanism by which a Cash App buyer and a Square merchant — both already authenticated to Block, both already known to one another within the platform — can form a bilateral, pair-settled commitment whose lineage is bound to both parties without Block being a counterparty to that commitment. Every direct interaction between two Block-resident entities still requires Block to stand in the middle. There is no architectural primitive within Block's stack for buyer-seller pairs to commit to each other directly under a lineage that survives outside Block's own ledger.

This matters for two emerging classes of commerce. The first is high-value, low-frequency commercial agreements — wholesale, contracted services, recurring B2B procurement — where the parties want bilateral evidence rather than aggregator records, but want it without the cost and friction of building bespoke contracting infrastructure. The second is Bitcoin- and stablecoin-denominated commerce, where the underlying asset already settles peer-to-peer on its own rails but the commercial commitment layer remains aggregator-mediated. Block's TBD initiative gestures at this second case but does not resolve the architectural gap; it produces protocols, not a pair-settlement primitive.

What the AQ Matched-Pair Primitive Provides

The matched-pair primitive supplies three architectural elements directly relevant to Block's ecosystem. First, bilateral pair-settled commitments: buyer and seller form a commitment that binds them to each other, signed by both, with no third party as a counterparty to the commitment itself. Second, no aggregator: the primitive does not require, and does not produce, an intermediating custodian; settlement of the underlying value (fiat, Bitcoin, stablecoin) runs on whatever rail the parties choose, and the primitive governs the commitment layer rather than the value layer. Third, lineage-bound matched commitments: each commitment carries a verifiable chain of provenance — what was offered, what was accepted, by whom, under what conditions — that survives independently of any platform's ledger.

The primitive is not a payment network and is not a competitor to Cash App or Square in their core function of moving value. It is the substrate beneath direct commercial commitments, composable with whatever value rail and whatever identity layer the parties bring.

Composition Pathway

Composition with Block runs along the boundary between commitment and settlement. Cash App and Square continue to act as identity surfaces, custodial rails, and value-movement infrastructure exactly as today. The matched-pair primitive sits beside them, exposing a commitment layer through which a Cash App user and a Square merchant — or a Square merchant and another Square merchant, or a Cash App user and an external counterparty — can form a bilateral, lineage-bound agreement. Settlement of the agreed value runs through the existing Block rails; the agreement itself binds the parties to each other rather than to Block.

For Bitcoin and stablecoin flows, the composition is even more direct. Block's self-custody products (Bitkey, on-chain wallets) move value peer-to-peer on Bitcoin rails. The matched-pair primitive supplies the bilateral commitment that anchors the commercial meaning of the transfer — what was bought, what terms applied, what recourse the parties retain — as a lineage-bound record signed by both parties without an aggregator. The combined stack delivers both peer-to-peer value movement and peer-to-peer commercial commitment, neither of which Block today produces architecturally on its own.

Commercial Implication

Block's growth has historically come from extending aggregator-mediated commerce into adjacent surfaces — restaurants, retail, payroll, lending, music. Each extension reinforces the aggregator role and the regulatory and operational obligations that come with it. Composition with the matched-pair primitive opens an addressable market that the aggregator architecture cannot reach: commercial commitments where the parties want bilateral evidence and pair settlement without an intermediary as a counterparty. For Block, this is a class of customer — wholesale, B2B, contracted services, high-trust recurring commerce — that today routes around Block to bespoke contracting tools or to nothing at all.

For the broader payments market, the composition reframes the long-running tension between aggregator efficiency and direct-commerce evidence. PayPal, Stripe, Adyen, and the card networks all share Block's structural position as commitment intermediaries. A primitive composed beneath any of these stacks repositions the aggregator from "necessary counterparty to every transaction" to "selectable rail for value movement," with the commitment layer disaggregated. Block's existing strength in consumer identity (Cash App), merchant tooling (Square), and Bitcoin infrastructure makes it the most natural early adopter of a primitive that decouples commitment from custody.

Licensing Implication

The matched-pair primitive is licensable as a commitment substrate beneath any payments, commerce, or settlement platform. For Block specifically, a license preserves the Square merchant base, the Cash App consumer relationship, the Bitcoin and Afterpay product lines, and the ecosystem economics intact; the primitive supplies the bilateral, no-aggregator, lineage-bound commitment layer that Block does not architecturally produce. Licensing simultaneously to Block and to adjacent platforms — Stripe, PayPal, Adyen, on-chain commerce protocols — is the natural deployment pattern, because the primitive's value increases with the number of platforms beneath which it composes. The intellectual property covers bilateral pair-settled commitments, no-aggregator settlement, and lineage-bound matched commitments as a composable set, and the licensing model is structured so that no single payments platform can subsume the substrate by adopting it alone.