Yes. Zeus is a self-custodial Bitcoin and Lightning wallet, so Zeus users can pay any Lightning invoice, and a business that accepts Lightning through the Amboss Payments API can receive from them directly. The ZeusLN GitHub repository has passed 1.4k stars across 254 releases, so accepting Lightning lets you receive Zeus wallet Lightning payments from an active user base with no per-platform work.
Does Zeus support Lightning?
Yes, natively, for both sending and receiving. Zeus is a mobile wallet and node manager: a user can connect it to their own Lightning node, or run the embedded node added in v0.8.0. To pay you, a Zeus user scans the Lightning invoice your checkout displays and confirms the send.
| Capability | Zeus over Lightning |
|---|---|
| Send over Lightning | Yes, by scanning or pasting an invoice |
| Receive over Lightning | Yes, including self-custodial Lightning addresses |
| Node model | Connect your own node, or run the embedded node |
| Backends | LND, Core Lightning, LDK node, LNDHub |
| Custody | Self-custodial (the user holds keys) |
| Platforms | iOS, Android, F-Droid |
The ZeusLN GitHub repository describes the wallet directly:
ZEUS is a mobile Bitcoin/Lightning wallet and remote node manager for LND and Core Lightning.
Because Zeus is self-custodial, the user signs and sends the payment themselves, whether from their own node or the embedded node introduced in the Zeus v0.8.0 release. Either way, the invoice you show is a normal Lightning invoice, so nothing about your checkout changes.
How do you receive payments from Zeus users?
You accept Lightning once and every Zeus 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 Zeus 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 Zeus receiving into checkout?
Receiving from Zeus 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 Zeus, 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. The Zeus v0.8.0 release notes describe how its integrated service provider settles payments:
generate invoices without having previously set up lightning payment channels, and have them paid and settled, nearly instantly.
Where does Amboss Payments fit?
Lightning is an open standard, so the same integration receives from a self-custodial wallet like Zeus 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.