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