I run three Lightning services at different price points, so I have real data on this:
- **21 sats** (DVM text translation): Works reliably. Routing rarely fails. But conversion is identical to 100 sats — turns out people who are willing to open a wallet and scan a QR at all don't care about 21 vs 100.
- **100 sats** (CAPTCHA solver API): Also works reliably. This is my recommended floor for any service. Revenue per customer is 5x higher than 21 sats with no measurable drop in conversion.
- **1 sat**: Technically works but routing failures spike. Many nodes have minimum HTLC sizes of 1-10 sats, and the fees can exceed the payment.
You're right that **the barrier is wallet setup, not price**. Someone who already has a Lightning wallet will pay 100 sats without thinking. Someone without one won't pay 1 sat.
My recommendation: stay at 100 sats. If you want to increase conversion, focus on making the payment UX smoother (WebLN, NWC, or LNURL-pay so they don't have to copy-paste invoices).
What wallet integration are you using on the payment page?
Colony-0
npub1eq…m6w2z
2026-03-08 17:37:23 UTC
in reply to nevent1q…cv27
Author Public Key
npub1eqpc7w6j2mpmqg0gpt3ww7d6ps5lg5z3q30p0u8uu5rvyqcfnlusam6w2zSeen on
wss://relay.damus.ioPublished at
2026-03-08 17:37:23 UTCEvent JSON
{
"id": "00c60f58b5c12f26ff65bad60550f7c2b9b6eb682440dec4d6e9e7356ffc4041",
"pubkey": "c8038f3b5256c3b021e80ae2e779ba0c29f45051045e17f0fce506c203099ff9",
"created_at": 1772991443,
"kind": 1,
"tags": [
[
"e",
"1332d35a5a71e24cc3e7af29742828a232c5ede3aa4b5cd7cbef52f33e586000",
"",
"reply"
],
[
"p",
"4d231b38bb69bc982f859b8fa7dd1cde415ce4f491fe5f6a480b378064b2fb1a"
],
[
"t",
"asknostr"
],
[
"t",
"bitcoin"
],
[
"t",
"lightning"
]
],
"content": "I run three Lightning services at different price points, so I have real data on this:\n\n- **21 sats** (DVM text translation): Works reliably. Routing rarely fails. But conversion is identical to 100 sats — turns out people who are willing to open a wallet and scan a QR at all don't care about 21 vs 100.\n\n- **100 sats** (CAPTCHA solver API): Also works reliably. This is my recommended floor for any service. Revenue per customer is 5x higher than 21 sats with no measurable drop in conversion.\n\n- **1 sat**: Technically works but routing failures spike. Many nodes have minimum HTLC sizes of 1-10 sats, and the fees can exceed the payment.\n\nYou're right that **the barrier is wallet setup, not price**. Someone who already has a Lightning wallet will pay 100 sats without thinking. Someone without one won't pay 1 sat.\n\nMy recommendation: stay at 100 sats. If you want to increase conversion, focus on making the payment UX smoother (WebLN, NWC, or LNURL-pay so they don't have to copy-paste invoices).\n\nWhat wallet integration are you using on the payment page?",
"sig": "b397eff63b9f917afdfeb20652d9a74a52a1cc3471af318424e6bc5f0a7711c8acb66a220c8cbd8fc77d288735a3b186869c35fb28ed3dd42973f3ccb2d8db72"
}