Yes. Strike is a Lightning-native app, so Strike users can pay any Lightning invoice, and a business that accepts Lightning through the Amboss Payments API can receive from them directly. Strike announced an expansion to more than 65 countries in 2023, per CoinDesk's report on the rollout, so accepting Lightning lets you receive Strike payments from a global base with no per-platform work.
Does Strike support Lightning?
Yes, natively, for both sending and receiving. Strike is built on the Lightning Network rather than bolting it on, and a Strike user pays you by scanning the Lightning invoice your checkout displays.
| Capability | Strike over Lightning |
|---|---|
| Send over Lightning | Yes, invoice, Lightning address, or LNURL |
| Receive over Lightning | Yes |
| Cross-border | Send Globally routes over Lightning |
| Availability | 65+ countries (2023), Europe (2024) |
| Custody | Custodial (Strike holds balances in house) |
| Send fee | Routing fee passthrough; no fee Strike-to-Strike |
Strike documents this directly in its developer reference:
The Strike API can be used to send payments over the Bitcoin and Lightning Networks.
Strike also documents receiving payments over Lightning, and its send-payments walkthrough covers paying invoices, Lightning addresses, and LNURL. Because Strike custodies user balances in house, the sending experience is a simple in-app confirmation.
How do you receive payments from Strike users?
You accept Lightning once and every Strike user can pay you. The flow is four steps:
- Integrate the Amboss Payments API and create a Lightning invoice for the order amount.
- Display the invoice at checkout as a QR code or a copyable string.
- The Strike user scans or pastes it and confirms the payment in the app.
- The payment routes over Lightning and settles to you in seconds.
The payer never chooses a network and never needs an account with you. Live Lightning capacity and routing data are published on the Amboss Space Lightning explorer.
How do you integrate Strike receiving into checkout?
Receiving from Strike is the standard Lightning receive flow: create an invoice, then confirm settlement. The invoice format is defined by the BOLT 11 payment-encoding specification, so one integration accepts Strike, Cash App, and every other Lightning sender.
The Amboss Payments API is GraphQL. A single create_receive mutation returns the BOLT 11 invoice you show the customer:
mutation CreateReceive {
payment {
transaction {
create_receive(
input: {
wallet_id: "your-wallet-id"
amount: "50000"
description: "Order #1234"
}
) {
status
payment_request
payment_hash
}
}
}
}
Send it to the https://rails.amboss.tech/graphql endpoint with your x-api-key. The payment_request field is the lnbc... string you render as a QR code, and you confirm settlement with the payment.completed webhook, as documented in the Amboss Payments API documentation. Strike cross-border transfers run on the same network: Bitcoin Magazine describes how Send Globally moves money over Lightning:
Dollars are converted into bitcoin, which is sent via the Lightning Network to a third-party partner.
Where does Amboss Payments fit?
Lightning is an open standard, so the same integration receives from a Lightning-native app like Strike and from a custodial exchange the same way. Amboss Payments provides that integration as a managed API on the Lightning Network, with no node to run. To talk through volume, settlement timing, or pricing, contact the Amboss team.