Blink

• Name: Blink
• URL: https://www.blink.sv/
• Category: Bitcoin wallet / Bitcoin banking and payments control plane / hosted-and-self-hostable Lightning infrastructure
• Tags: bitcoin-ecosystem
• Summary: Blink is the product surface of a broader Bitcoin banking stack. The wallet matters less than the operator package behind it: hosted GraphQL access, merchant receiving tools, BTC-and-USD balance handling through Stablesats, and a self-host path tied to Blink Core, Bria, and admin tooling. Real stack, not just a wallet app.
• What it does:
  • Provides a mobile Bitcoin wallet for sending and receiving both onchain Bitcoin and Lightning payments
  • Lets users and merchants hold balances in BTC or a synthetic USD balance through the Stablesats hedging layer
  • Exposes a hosted GraphQL API authenticated with API keys for app and backend integrations
  • Supplies merchant tools such as a point-of-sale web app, reusable receiving QR codes, and BTCPay and WooCommerce integration paths
  • Offers a self-host stack for community banks or organizations, including Blink Core, Stablesats, Bria for batching and liquidity management, Blink CLI, and admin/dashboard tooling
  • Publishes an open-source mobile wallet intended to be customized by communities and organizations using the Blink-compatible backend
• Key claims:
  • The main developer-docs intro frames Blink as “a powerful, cost-effective, and reliable solution” for integrating Bitcoin and Lightning payments, explicitly supporting both bitcoin- and USD-denominated flows
  • The docs say Blink-to-Blink transfers are free, Lightning routing fees are roughly 0.02%, and Stablesats conversion carries a 0.2% spread, signaling that the product is optimized as a payments rail rather than just a wallet UI
  • The authentication docs show a server-side GraphQL API at https://api.blink.sv/graphql secured with API keys, which is a strong indicator that Blink has a real developer and operational surface beyond the consumer app
  • The merchant-tools and API-use-cases pages present Blink as merchant infrastructure, including a Lightning cash-register flow, reusable QR codes, BTCPay plugin support, and WooCommerce integration
  • The self-host overview explicitly says the Blink core banking platform contains what is needed to launch “a community bank on Bitcoin and Lightning,” and breaks the stack into Blink Core, Stablesats, Bria, Blink CLI, mobile wallet, dashboard, and admin panel
  • The open-source mobile app README says the app is designed to be compatible with Galoy’s backend and customizable for any community or organization, reinforcing that the wallet is one surface of a broader banking stack
  • The public API reference documents a wide GraphQL surface spanning wallet/account lookups, authorization scopes, currency conversion estimation, map markers, and other operational queries, which supports cataloging Blink as a broader payments-control-plane vendor
• Whitepaper: No canonical standalone Blink whitepaper or litepaper surfaced in this pass. The clearest current source of truth is the official site, developer docs, public API reference, and open-source app/backend materials; see ../whitepapers/blink-primary-sources-2026-04-30.md.
• Sources:
  • https://www.blink.sv/
  • https://www.blink.sv/en/merchant-tools
  • https://www.blink.sv/en/api-use-cases
  • https://dev.blink.sv/
  • https://dev.blink.sv/api/auth
  • https://dev.blink.sv/self-host
  • https://dev.blink.sv/public-api-reference.html
  • https://raw.githubusercontent.com/blinkbitcoin/blink-mobile/master/README.md

Internal linkages

• Parent company-and-banking stack that explains why Blink is bigger than a wallet app: galoy
• Self-hosted merchant-stack contrast for operators who want invoices and stores without Blink’s broader banking layer: btcpay-server

Protocol / company boundary

• Keep this note on the Blink product surface: hosted GraphQL access, BTC-and-USD balance handling through Stablesats, merchant receiving tools, self-host packaging, and the wallet-plus-admin surfaces an operator or integrator touches directly.
• Use galoy for the broader company boundary around Cala ledger design, Bria transaction-control policy, institutional integration workflow, compliance-aware packaging, and the named operator shell that decides how Blink sits inside a larger banking stack.
• That split matters because how does Blink the wallet / merchant / API product behave? and which company controls the surrounding banking, ledger, and integration shell? are related but not identical questions.

Control surface

• At the product layer, authority sits in hosted API admission, wallet and merchant-tool defaults, Stablesats exposure and spread policy, self-host versus hosted deployment, and the admin surfaces wrapped around the Blink stack.

• The thicker ledger, transaction-policy, and institutional operator boundary lives one layer up in galoy.

• Read Blink as the product layer of a broader Galoy-shaped banking system, not as a standalone wallet primitive.

• Last reviewed: 2026-08-13 UTC