One question…
I noticed that nostr:npub1cm3rpgj7457yjuqnvdalxaauakqu0ndkpkyp5cldkyutpz4xszpsmk96wt addresses don’t support LNURL-verify, which means I can’t use it with some of the open source point-of-sale apps I’m currently testing.
Is this a feature you can enable in a future release?
Also, I’m guessing that https://pay.blitz-wallet.com/ is not set up to work with the Spark wallet yet, because I just lost $1 into the void by trying it out.
Yep. That is not converted yet
So…can I get my dollar back somehow? 😆
If you load the seed for your wallet into blockstreams app and choose a liquid card you should be able to see it.
We will look into this!
Any chance you can test it now?
Yes, it’s working now!
Tested using: https://lnpos.online
nostr:nprofile1qqsvdc3s5f0260zfwqfkx7lnw77wmqw8ekmqmzq6v0kmzw9s32ngpqcfwuxkg I do have one question. I see that payments can be received offline this way. Is there a time limit for receiving payments when you don’t have the app open, or do they automatically settle in the background?
Nope. One of the great benefits of Spark is the ability to receive truly offline.
That’s what I’m talking about! So they can just stay in “pending” state forever? 
Yep. Until you log on and create the new signature.
Love it. Let’s encourage all Spark wallets to incorporate LNURL-verify too, so any merchant can use a simple free point of sale with the wallet of their choice.
nostr:npub1hcwcj72tlyk7thtyc8nq763vwrq5p2avnyeyrrlwxrzuvdl7j3usj4h9rq, you guys are next!
The site you are using is spamming our backend, we might have to remove support for it.
We have removed support until we figure out how to prevent the spam.
Ah, interesting. I think the frequency may have to be tuned. Good thing we are just discovering this now.
nostr:npub1em3g0wcfjz5we0gaaelw07fcyqys3fwg42qykw774mvgala424rsl26ytm 👀
There were over 2,700 requests just from you for the single payment it looked like.
That seems…high. Talking to the developer about it! Thanks for bearing with us as we try to solve it.
I have a theory about what happened. After the payment completed, I didn’t close the POS page, and when I went back to the tab later, I saw it continually refreshing even though it was already in a success state.
I don’t know if it’s an issue with the app or the browser, but I’m messaging the app’s creator to see if there’s some way to automatically return to the payment entry screen to prevent an infinite loop.
