Strike primary-source snapshot
Fetched: 2026-05-01 UTC
1) Official API docs introduction
Source: https://docs.strike.me
Selected excerpts from the docs:
The Strike API lets you make programmatic bitcoin and cash transactions using the Bitcoin and Lightning Networks.
This includes sending, receiving, exchanging, directing, making cash payouts to bank accounts, and using OAuth for 3rd party integrations.
It’s a payments API that uses Bitcoin as global payments infrastructure
Additional signals from the source:
- This is the clearest first-party statement that Strike is packaging Bitcoin and Lightning as reusable payments infrastructure rather than only a consumer app
- The docs explicitly bridge bitcoin, cash, bank payouts, and OAuth in one product surface, which points to a broader control-plane role
2) Walkthrough overview
Source: https://docs.strike.me/walkthrough/walkthroughs-overview
Selected excerpts from the page:
The Strike API allows you to send and receive dollars over the Lightning Network, without the need to interact with Bitcoin directly.
This means your application is able to leverage the speed, security, and interoperability of the Bitcoin Lightning payments without exposure to Bitcoin’s price volatility, tax treatment, and custody concerns.
Additional signals from the source:
- This is an important categorization clue because it shows Strike is abstracting Bitcoin settlement complexity away from the integrator
- The docs frame Lightning as infrastructure for dollar-denominated applications, not only a feature for Bitcoin-native users
3) Account overview and business onboarding
Source: https://docs.strike.me/account/overview
Selected excerpts from the page:
if you intend to use the Strike API or any other Strike services in association with a business or organization, you must sign up for a business account.
Once the information for your business, owners, and operators have been verified, your Business account will be approved and you will be able to deposit cash, buy bitcoin, and make transactions.
The Strike Dashboard is where you can create and manage your API Keys.
Additional signals from the source:
- The onboarding flow makes clear that Strike is a real business-facing operational platform with compliance review, not just a hobby developer API
- The dashboard and API-key workflow reinforce that the product is meant to be embedded into external systems
4) Example apps
Source: https://docs.strike.me/walkthrough/example-apps
Selected excerpts from the page:
The below list shows a variety of applications that use of the Strike API to enable payments through Bitcoin and Lightning.
Pay me in BTC allows you to deploy Bitcoin Lightning invoices as unique website URLs.
PlebPay allows you to create paywalls for URLs.
Plebshop allows Strike users to quickly create their own in-person checkout solution and receive payments to their Strike account.
Strike Oauth is a simple proof of concept that demonstrates how to integrate Strike Oauth Connect.
Additional signals from the source:
- The example-app taxonomy is one of the best signals that Strike exposes reusable primitives such as invoicing, paywalls, bill splitting, QR checkout, and OAuth flows
- The linked GitHub repos suggest a developer ecosystem around Strike’s payment rails rather than only documentation for an internal mobile app
5) Public status page
Source: https://status.strike.me
Selected excerpts from the page:
Banking Services
Bitcoin Payments: Lightning
Bitcoin Payments: On-Chain
Bitcoin Withdrawals
Buy Bitcoin
Send Globally
Strike API
Strike OAuth Connect
Strike Dashboard (dashboard.strike.me)
Additional signals from the source:
- The status taxonomy is a useful operational clue because it shows Strike runs several interdependent service layers, not just one app surface
- Strike treats the API, OAuth, payments rails, onboarding-adjacent services, and dashboard as first-class systems
Notes
- Strike appears best cataloged as bitcoin-and-cash payments API / Lightning settlement infrastructure / bank-payout and OAuth control plane.
- No canonical standalone whitepaper or litepaper surfaced in this pass.
- The most useful primary sources were the docs introduction, walkthrough overview, account onboarding page, example apps page, and the public status page.