Cash App

• Name: Cash App
• URL: https://cash.app/
• Category: crypto-adjacent consumer money app / Bitcoin access layer / merchant checkout infrastructure
• Tags: bitcoin-ecosystem
• Summary: Cash App matters here because it combines mass-market Bitcoin distribution with a separate grant-based merchant-pay rail. Not a pure wallet note. Not an open payments standard either. The broader named-operator and distribution boundary around Cash App’s bitcoin, merchant, and adjacent Bitkey / Square surfaces now lives separately in block.
• What it does:
  • Lets users buy bitcoin on a schedule, turn spare change into bitcoin, get paid in bitcoin via direct deposit, and withdraw bitcoin to their own wallets
  • Offers consumer-facing bitcoin payments at merchants that use Square, with the bitcoin page explicitly saying users can pay in seconds with bitcoin or U.S. dollars
  • Exposes Cash App Pay as a developer product with a Customer Request API, Network API, Management API, and Pay Kit JavaScript SDK
  • Supports Cash App Pay across mobile ecommerce, web ecommerce, and point-of-sale flows, including QR-based approval and mobile-native approval experiences
  • Uses a grant-based payment flow in which merchants request permission from customers, receive grants after approval, and then create payments server-side through the Network API
  • Maintains a public engineering and open-source footprint through the cashapp GitHub organization and Block’s open-source program, which highlights bitcoin-related work such as LDK alongside broader developer infrastructure
• Key claims:
  • The bitcoin landing page says Cash App offers fee-free recurring bitcoin purchases via Auto Invest, lets users use Round Ups and direct deposit for bitcoin accumulation, and emphasizes transparent pricing with “no hidden costs, no inflated spreads”
  • The same page says Cash App is “designed for bitcoin,” claims bitcoin is held 1:1 and never lent out, and says users can withdraw to their own wallet anytime
  • The Cash App Pay docs introduction says the product includes comprehensive guides, API references, testing environments, and integration tools for implementing Cash App Pay
  • The API fundamentals guide says Cash App Pay is composed of three REST APIs plus a JavaScript SDK: Customer Request API, Network API, Management API, and Pay Kit
  • That guide also says the core workflow is to create a customer request, get it approved to generate a grant, then use the grant to create a payment, with settlement later that day
  • The product-overview page says Cash App Pay currently supports three main use cases: mobile ecommerce, web ecommerce, and POS
  • The public GitHub organization shows Cash App maintains a sizable open-source engineering footprint beyond the payment product itself, with many actively maintained repositories under the cashapp domain-verified org
  • Block’s open-source page says Block’s projects span payment systems, privacy initiatives, bitcoin hardware wallets, and bitcoin tooling such as LDK, which reinforces that Cash App sits inside a larger engineering ecosystem with real public infrastructure commitments
• Whitepaper: No canonical standalone Cash App whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the Cash App bitcoin landing page, the Cash App Pay partner docs, the API-fundamentals and product-overview docs, the public GitHub organization, and Block’s open-source overview; see ../whitepapers/cash-app-primary-sources-2026-05-02.md.
• Sources:
  • https://cash.app/
  • https://cash.app/bitcoin
  • https://developers.cash.app/cash-app-pay-partner-api/guides/welcome
  • https://developers.cash.app/cash-app-pay-partner-api/guides/welcome/llms.txt
  • https://developers.cash.app/cash-app-pay-partner-api/guides/technical-guides/api-fundamentals/introduction-to-cash-app-pay-ap-is
  • https://developers.cash.app/cash-app-pay-partner-api/guides/product-overview/how-cash-app-pay-works
  • https://github.com/cashapp
  • https://block.xyz/open-source

Internal linkages

• Company / operator boundary above the product surface: block.
• Closed-loop merchant-approval comparison point: walletconnect-pay.
• Stronger separation between identity, discovery, and scoped authorization: open-payments.

Protocol / company boundary

• Keep this note on the product surface: retail bitcoin access, 1:1 reserve and withdrawal claims, and the grant-based Cash App Pay workflow across mobile, web, and POS.
• Use block for the named-operator layer above that product: the organization that bundles Cash App with Bitkey, Square merchant rollout, broader bitcoin strategy, and the wider engineering / open-source posture.
• That split matters because how does Cash App bitcoin or Cash App Pay work? and who controls the broader company shell around those rails? are related but not identical questions.

Control surface

• The product-layer leverage sits in which bitcoin actions Cash App makes easy, how reserve and withdrawal assurances are framed, how Cash App Pay grants and settlement work, and which merchant / developer flows are first-class.

• Do not flatten this into only consumer app adoption. The important product question is still how Cash App turns bitcoin access and merchant approval into a usable default payment path.

• For the wider corporate distribution, merchant, and strategy shell above this product, read block.

• Last reviewed: 2026-08-07 UTC