Lightning Wallets That Work With Zapable

The Short Answer

If you want the simplest setup for selling on Zapable, use Alby or Speed Wallet. Both can pass Zapable's compatibility check, which means Zapable can confirm when a buyer has paid your Lightning invoice.

If you use a self-hosted or advanced setup like BTCPay Server or LNbits, it may work too, but you should only trust it after Zapable accepts your Lightning Address and you complete a test purchase.

Zapable's wallet checker is the source of truth. If Zapable accepts your Lightning Address, your wallet supports the confirmation flow Zapable needs. If Zapable rejects it, that wallet may still be a good Lightning wallet, but it cannot be used for reliable seller payments on Zapable.

Why Zapable Requires a LUD-21 Wallet

Zapable is non-custodial for Lightning payments. That means buyers pay your wallet directly. The Bitcoin does not pass through a Zapable wallet, Zapable balance, escrow account, or payout system.

This is different from a custodial marketplace. In a custodial flow, the platform creates the invoice, receives the payment, sees the payment settle in its own wallet, then pays the seller later. Zapable intentionally avoids that model. We do not custody creator funds, we do not sit between the buyer and seller, and we do not delay Lightning payouts.

That non-custodial design is better for creators, but it creates one technical question: if the buyer pays your wallet directly, how does Zapable know the payment happened?

The answer is LNURL-verify, also called LUD-21. When a compatible wallet creates a Lightning invoice for Zapable checkout, it includes a verification URL. After the buyer pays, Zapable asks your wallet provider whether that exact invoice settled. If your wallet says yes, Zapable unlocks the buyer's purchase, marks the order paid, and records the sale.

A normal Lightning Address is not enough. Some wallets can receive Lightning payments, but they do not expose the verification endpoint Zapable needs. Those wallets may work perfectly for tips, direct payments, or personal use, but they cannot give Zapable reliable proof that a product checkout invoice was paid.

Compatible Wallets for Zapable Sellers

These are the wallets and setups we would point creators toward first.

Wallets That Usually Do Not Work for Zapable Sellers

The wallets below can be useful for buying, sending, saving, or receiving regular Lightning payments. The issue is narrower: they usually do not provide the LUD-21 verification Zapable needs for automated product delivery.

Compatibility vs Liquidity

Wallet compatibility and wallet liquidity are different. Creators need both.

• Compatibility means Zapable can confirm payments automatically using LNURL-verify / LUD-21.
• Liquidity means your wallet can actually receive the buyer's payment amount.

Think of inbound liquidity as your wallet's receiving capacity. If you sell a $50 product, your wallet needs enough capacity to receive roughly that amount over Lightning. Hosted wallets often manage this for you. Self-hosted nodes, LNbits, and BTCPay setups may require you to manage inbound liquidity yourself.

How to Make Sure Your Wallet Is Ready

1. Choose a Zapable-compatible wallet such as Alby or Speed Wallet.
2. Add your Lightning Address in your Zapable wallet settings.
3. Let Zapable run its compatibility check.
4. Receive a small test payment before sharing a product link publicly.
5. If you run your own node, confirm you have enough inbound liquidity for your product prices.

If a Buyer Says Payment Failed

First check whether Zapable accepted your Lightning Address. If it did, the next likely issue is receiving capacity or wallet availability. Try a small test payment, make sure your wallet service is online, and check your node liquidity if you use a self-hosted setup.

If you are not sure what is wrong, switch to Alby or Speed Wallet first. That removes most setup variables and lets you get back to selling.