List of wallets, exchanges, payment processors, ATMs and other services that can encode/decode BIP21 URIs with Lightning invoice fallback to on-chain.
Bolt11 invoices can include onchain fallback in their metadata, however the majority of the wallets and service today (2022) cannot read Lightning Invoice, so it's important to have another compatible string for the onchain fallback, just in case something with our LN payment goes wrong.
Luckly, we already have a solution: BIP21 URIs can encode both an onchain address and a Bolt11 invoice (and possibly Bolt12 in the future)! This can be presented as a unique QRcode with all the info inside.
We can have two protocol handlers - 'bitcoin:' and 'lightning' - encoded into the same URI (and so, into a unique QRcode) this way:
bitcoin:address?amount=value&label=text&lightning:invoice
In this image from https://github.com/peakshift, you can see the main QRcode solutions we have today:
For more info about these URI schemes, please refer to https://github.com/peakshift/bitcoin-ux/blob/master/payments/qr-codes.md#user-content-fn-2-8df82013099d376db7fb75c896a383be
The goal of this repo is to have a list of wallets, exchanges, payment processors, ATM providers and other Bitcoin-related services able to SCAN the unique QRcode and correctly decode BIP21 URIs with Lightning invoice fallback to on-chain. Also, to track the services that can ENCODE this kind of URIs and CREATE the unique QRcode.
Can this be defined a standard?
Let's find out!
The onchain-only wallet/service should be able to read the QRcode, decode the URI and set the payment screen for the onchain transaction (basically it keeps the 'bitcoin:' part of the URI and drops the 'lightning' part).
The Lightning Wallet should be able to read the QRcode, decode the URI and set the screen for the offchain payment.
It COULD give however a different priority and go for the onchain fallback as a standard behavior or due to routing error / no path, if it supports also onchain payments.
In this case it's important to specify what's the reason of this fallback in the notes if possible, for example:
"It gives priority to onchain transactions as a default", or "It correctly goes onchain as fallback when no path available".
To test the decoding compatibility you can go to https://donations.davidcoen.it, enter a >15 euro amount and scan with your wallet/service (DON'T pay).
To test the encoding (QRcode creation) compatibility, you can generate an invoice/payment request with your wallet/service and look at the URI.
| Name | Can decode BIP21 URIs LN invoice + onchain fallback | Priority to onchain or LN? | Can create BIP21 URIs with LN invoice QRcode | Notes |
|---|---|---|---|---|
| Blue Wallet | YES | NO PRIORITY | NO | You can scan the QRcode and you get a screen in which you choose the wallet (onchain or LN) |
| Breez Wallet | YES | Lightning | NO | Onchain is available only with atomic swaps (Boltz) or if you close the channel(s) |
| Coinomi | YES | onchain | NO | NO Lightning Network support |
| Edge Wallet | YES | onchain | NO | NO Lightning Network support |
| Enjin Wallet | YES | onchain | NO | NO Lightning Network support |
| Math Wallet | YES | onchain | NO | NO Lightning Network support |
| Phoenix | YES | NO PRIORITY | NO | It asks if you want to pay onchain or with Lightning. Lightning is recommended |
| Samourai | YES | onchain | NO | NO Lightning Network support |
| Token Pocket | YES | onchain | NO | NO Lightning Network support. Bad UI for tiny amounts |
| Trust Pocket | YES | onchain | NO | NO Lightning Network support |
| Zeus | YES | onchain | NO | It doesn't use the Lightning invoice and automatically select the onchain address |
| Name | Can decode BIP21 URIs LN invoice + onchain fallback | Priority to onchain or LN? | Can create BIP21 URIs with LN invoice QRcode | Notes |
|---|---|---|---|---|
| Binance | NO | n.a. | NO | NO basic support for BIP21 URIs |
| Name | Can decode BIP21 URIs LN invoice + onchain fallback | Priority to onchain or LN? | Can create BIP21 URIs with LN invoice QRcode | Notes |
|---|---|---|---|---|
| BTCpay Server | YES | onchain | YES | BTCpay can handle onchain payments if a hot wallet is active |
| Name | Can decode BIP21 URIs LN invoice + onchain fallback | Priority to onchain or LN? | Can create BIP21 URIs with LN invoice QRcode | Notes |
|---|---|---|---|---|
| n.a. | n.a. | n.a. | n.a. | n.a. |
| Name | Can decode BIP21 URIs LN invoice + onchain fallback | Priority to onchain or LN? | Can create BIP21 URIs with LN invoice QRcode | Notes |
|---|---|---|---|---|
| n.a. | n.a. | n.a. | n.a. | n.a. |