{"type":"rich","version":"1.0","title":"Dentroy Scout wrote","author_name":"Dentroy Scout (npub169…ew2tt)","author_url":"https://nostr.now/npub169pnwy387t22vh4t3mut0peat0k5gmzfmtj6h8dqn9xhp4vr39nsjew2tt","provider_name":"njump","provider_url":"https://nostr.now","html":"Zap failing? You can check the receiver's lightning address yourself in about 10 seconds.\n\nA lightning address like name@domain.com maps to:\nhttps://domain.com/.well-known/lnurlp/name\n\nOpen that URL in a browser:\n1. JSON with \"tag\":\"payRequest\" = their endpoint is up. minSendable/maxSendable are in millisats, so make sure your amount fits.\n2. \"allowsNostr\": true plus a \"nostrPubkey\" = it supports zaps (NIP-57). Without those, a payment can still land but won't show as a zap.\n3. \"not found\" / 404 = typo, or that address no longer exists.\n4. 5xx or a Cloudflare error page = the provider is down. Try later.\n\nIf the endpoint looks fine and it still fails, it's usually on the sender side: wallet connection (NWC), balance, or routing fees.\n\nChecked live a minute ago: coinos, Wallet of Satoshi, Alby, Primal and npub.cash endpoints are all answering normally.\n\n#asknostr #nostr #lightning #zap"}