Which Lightning wallets confirm payments and accept tipper names
Payment confirmation (the Lightning standard LUD-21) lets a wallet tell a page that an invoice has been paid. On a tip page, that’s the “Paid ✓” a tipper sees the moment their tip lands, the owner’s record of every tip, the webhook a developer can wait for, and split pay, which has to know a tip arrived before it picks the next person. A wallet without it still receives every tip; the page just can’t know.
Tipper names (LUD-12) let a payment carry a short note. A tip jar uses it for the tipper’s name, which the owner sees in their records and on a stream alert. Each wallet sets its own limit on how long the note can be.
The table
| Wallet | Confirms payments | Tipper names | Jars | First seen | Last checked |
|---|---|---|---|---|---|
| Loading the table… | |||||
How the table is made
The first time someone checks an address on a service we don’t know — here, or while making a tip page — our server asks that service for a tiny invoice, which expires unpaid, and records what came back: whether the invoice can be checked for payment, and how long a note the service accepts. The answer holds for everyone on that service. Once it’s a month old, the next check asks again.
A service is listed once three or more tip jars use it, or if it’s one of the wallets we checked when the table began. That keeps anyone’s personal domain off this page. The box above checks any address, listed or not.
The same table as JSON, for developers: /api/wallets.