Yes. Muun is a self-custodial bitcoin and Lightning wallet, so Muun users can pay any standard Lightning invoice, and a business that accepts Lightning through the Amboss Payments API can receive from them directly. Muun describes itself as "a self-custodial wallet for bitcoin and lightning", so accepting Lightning turns those users into people who can pay you, with the rail invisible to the payer.
Does Muun support Lightning?
Yes, for both sending and receiving, from a single balance. The detail that matters is how Muun gets there: it holds on-chain bitcoin and uses submarine swaps to settle Lightning invoices, so a Muun wallet Lightning payment reaches you as standard off-chain settlement against the invoice you created.
| Capability | Muun over Lightning |
|---|---|
| Send over Lightning | Yes, by scanning an invoice |
| Receive over Lightning | Yes |
| Lightning mechanism | Submarine swaps from a single on-chain balance |
| Channel management | None for the user; handled automatically |
| Custody | Self-custodial (2-of-2 multisig, user holds keys) |
| Cost to send | Lightning routing fee plus a swap fee |
The Muun engineering blog describes the sending experience directly:
You will still have your funds in one single wallet in Muun, and the whole payment process is the same as an on-chain payment.
Behind that simple flow is a submarine swap, a primitive Lightspark defines in its glossary entry on submarine swaps:
A mechanism for moving bitcoin between the main blockchain and the Lightning Network.
You do not need to know any of this to get paid. The Muun user scans your invoice, the wallet performs the swap, and a normal Lightning payment lands on your side, as the Muun blog on Lightning payments explains.
How do you receive payments from Muun users?
You do not build a Muun integration. You accept Lightning once and every Muun user becomes a potential payer. The flow is four steps:
- Integrate the Amboss Payments API and create a Lightning invoice for the order amount.
- Show the invoice to the customer as a QR code or a copyable string at checkout.
- The customer scans it inside Muun and confirms the send from their single balance.
- The payment routes over Lightning and settles to you in seconds. You fulfill the order.
The payer never chooses a network and never needs an account with you. Live network capacity and routing data are published on the Amboss Space Lightning explorer.
How do you integrate Muun receiving into checkout?
Receiving from Muun is the standard Lightning receive flow: create an invoice, then confirm settlement. A Lightning invoice is a self-contained string defined by the BOLT 11 payment-encoding specification, so the same code path accepts Muun, Cash App, and any 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. Lightning settles atomically, so there is no pending state that reverses a week later.
Where does Amboss Payments fit?
Lightning is an open standard, which is why a single integration receives from every wallet, whether the sender holds Lightning balances directly or swaps in from on-chain like Muun. Amboss Payments gives you that integration as a managed API, with no node to operate, so accepting a Muun customer is the same as accepting anyone else on the Lightning Network. If you want to talk through volume, settlement, or pricing, contact the Amboss team.