Strike

• Name: Strike
• URL: https://docs.strike.me/
• Category: bitcoin-and-cash payments product surface / Lightning settlement integration layer / dashboard-and-OAuth money-movement API
• Tags: bitcoin-ecosystem
• Summary: Strike at the project layer is the merchant- and developer-facing payment surface inside a broader Strike company shell. The useful product cut is the integration layer itself: dashboard-created API keys, scoped API actions, Lightning and onchain routing, bank-payout primitives, OAuth Connect, and reusable app patterns built around Strike account balances. The broader operator boundary now lives in strike, which is the cleaner place to reason about business approval, owner/operator verification, credential issuance, service availability, and the live company-run money-movement shell.
• What it does:
  • Lets individuals and businesses create Strike accounts, access a web dashboard, and manage API keys for programmatic payment workflows
  • Supports sending, receiving, exchanging, and directing bitcoin and cash transactions across the Bitcoin network and Lightning Network
  • Supports cash payouts to bank accounts and OAuth-based third-party integrations in addition to direct payment APIs
  • Gives applications a way to send and receive dollars over Lightning without forcing the integrator to hold or custody bitcoin directly
  • Publishes example apps for Lightning invoices, paywalled links, split bills, in-person checkout, and OAuth flows, which shows a wider developer ecosystem than a simple API landing page
  • Exposes a status surface that treats Strike API, Strike OAuth Connect, Lightning payments, onchain payments, withdrawals, onboarding, and banking services as distinct operating systems
• Key claims:
  • The walkthrough overview says the Strike API enables applications to send and receive dollars over the Lightning Network without direct exposure to bitcoin price volatility, tax treatment, or custody concerns
  • The account overview says business users sign up through the Strike Dashboard, complete entity and operator verification, and then can deposit cash, buy bitcoin, make transactions, and create API keys in the dashboard
  • The API-keys overview says integrators create keys in the Strike Dashboard, assign scopes to permit actions such as invoice creation or quote generation, and treat those keys as long-lived credentials able to perform financial transactions
  • The example-apps page shows first-party documentation for invoice links, split-bill flows, URL paywalls, in-person checkout, and OAuth examples, which is a strong clue that Strike is packaging reusable payment primitives rather than only documenting a closed app
  • The status page exposes separate operational surfaces for Banking Services, Bitcoin Payments: Lightning, Bitcoin Payments: On-Chain, Bitcoin Withdrawals, Buy Bitcoin, Send Globally, Strike API, Strike OAuth Connect, and the dashboard, which reinforces that Strike operates multiple interconnected payment layers
• Whitepaper: No canonical standalone Strike whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official API docs, onboarding guides, API-key guide, example-app documentation, and public status page; see ../whitepapers/strike-primary-sources-2026-05-01.md.
• Sources:
  • https://docs.strike.me/account/overview
  • https://docs.strike.me/walkthrough/walkthroughs-overview
  • https://docs.strike.me/api-keys/overview
  • https://docs.strike.me/walkthrough/example-apps
  • https://status.strike.me

Internal linkages

• Company boundary for the broader operator shell: strike.
• Closest Bitcoin operator contrast: river.
• Merchant-stack contrast: btcpay-server.
• Protocol-level contrast when the question is interoperable payment initiation rather than one operator stack: open-payments.

Protocol / company boundary

• Keep this note on the reusable payment surface: dashboard-managed accounts, scoped API keys, invoice and quote creation, Lightning and onchain routing, payout initiation, OAuth Connect, and the example-app patterns built around Strike balances and callbacks.
• Use strike for the named-operator layer around business approval, owner/operator verification, service availability, banking and payout exposure, credential issuance, and the broader company-run money-movement shell.
• That split matters because what can a Strike integration do? and which company decides who gets access, what services stay live, and how the legal/commercial shell behaves? are related but not identical questions.

Control surface

• At the product layer, practical authority accumulates around Strike account setup, dashboard-created API keys, scope selection, invoice and quote creation, payout initiation, OAuth permissions, and how tightly an application binds itself to Strike-managed account state and callbacks.

• The broader operator dependency sits one layer up in strike: business approval, owner/operator verification, credential issuance and revocation, banking and payout-service exposure, service-status truth, and the wider company-run money-movement shell.

• Read Strike here as a reusable payment-integration surface, not as a neutral Lightning baseline.

• Last reviewed: 2026-08-07 UTC