It’s possible to receive zaps through nostr:nprofile1qqszm52qe2qdkc4u7dma0klx3532jka2g8geck6fwxncyp90wktq2xsprpmhxue69uhhwetvvdhk6efwdehhxarj9emkjmn9qyxhwumn8ghj7mn0wvhxcmmv260q39 to nostr clients like nostr:nprofile1qqsraldwhvwcjgltmxwfu7kw8dqef2692yhzheuurd7k3kfy8cxjdqgpp4mhxue69uhkummn9ekx7mqpzpmhxue69uhkummnw3ezuamfdejseqpcd3 nostr:nprofile1qqszpxr0hql8whvk6xyv5hya7yxwd4snur4hu4mg5rctz2ehekkzrvcpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3camnwvaz7tmwdaehgu3dxqezu7tpdd5ksmmwdejjucm0d5m0hguy nostr:nprofile1qqs24yz8xftq8kkdf7q5yzf4v7tn2ek78v0zp2y427mj3sa7f34ggjcpzpmhxue69uhkummnw3ezumt0d5hsz9mhwden5te0we5hgmmj9ehx7um5wgcjucm0d5hs5xuvdg without KYC like you did experience in Primal.
You can e.g, receive zaps to your self custody LN-node or to #cashu wallets like nostr:npub1s4m06xdlu6fuhfhs4m3nhpp8xdpsdprwccdktckkzusfu8qzzprqnfpz6a nostr:nprofile1qqstxwlea9ah3u6kjjszu6a7lrnhqkfh8eptp2z6v0e9558tlkkl2rgprfmhxue69uhhyetvv9ujumtfde5ky6t5wvhxxctndqhsz9thwden5te0wfjkccte9ejxzmt4wvhxjme0lnhtq3 with nostr:nprofile1qqszm52qe2qdkc4u7dma0klx3532jka2g8geck6fwxncyp90wktq2xsprpmhxue69uhhwetvvdhk6efwdehhxarj9emkjmn9qyxhwumn8ghj7mn0wvhxcmmv260q39
Login to reply
Replies (2)
Thank you. We got it sorted out by installing self-hosted nostr:nprofile1qytzqamnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcpr3mhxue69uhkummnw3ez6vfwde3x7tnpdenkzmnf9e3k7tcqypr90hlgjed73xq2jvrjhna4ukdx2yjyqmdslqvjzhh83wj8jd9numxx6g9 on one of our nodes, and then using Nostr Wallet Connect (NWC) to configure Primal. Sent you a test of 21 sats. Looks like it went through.
I think we worked it out.
- we didn't want to create accounts with a third party
- we wanted to interface directly with our own node
- Alby Hub let us send, but as you pointed out, we could not receive
- we already had BTC Pay setup for our online store
- BTC Pay supports Lightning Addresses
- we created receive@btcpay.servingbitcoin.com
- we added this value to your Primal profile
- we can now receive zaps
Thanks for the encouragement and patience as we figured this out.