DM more payment details.

More details?

Sorry for the issue, my monitoring failed to report it, both fixed 2 days ago.

Was a user request, glad to see others like it.

Please note that feature depends on nostr client publishing zapped event info in the nwc command's metadata - all won't likely.

Thanks. The zaps fix targets android. True that iOS is still a challenge as it does not allow much control over the background processing. In my tests zaps work on iOS reasonably well, however I am aware of many corner cases. Will work on that further.

Not sure about ecash vs lightning balance - there is only one ecash balance in Minibits. NWC connection has daily limits that might limit how much can be zapped from nwc-connected nostr app.

Few more details for the deep seekers:

>> Zap with confidence when app stays in the background
On android, zaps failed in unpredictable ways if app was running in the background (not fully killed). This was caused by low level react native bug that is now fixed.

>> Zaps now link to the post you zapped
Based on user request. This feature depends on nostr client that need to add necessary metadata into the NWC command that eventually reaches the wallet.

>> NFC fixed between two Minibits on iPhone & Android
NFC host card emulation on Android had a specific bug manifesting only when read by another Minibits wallet running in iOS, that has been patched.

>> Further contacts improvements
New contact can be added by scanning a QR code encoding address or npub. Wallet now shows its own address encoded as nprofile.

>> Send cashu requests straight to contacts and pay from the thread
Cashu payment requests can now be sent to contacts, then tapped in the messages thread and paid by the payer. Wallet now honors if the cashu pr is set as single use only.

Confirming that it is doable for sent zaps if nostr client publishes the zapped event in the nwc command metadata.

Will lend in next OTA release, make sure to run latest v0.4.5.

Check Minibits Ippon.

https://minibits.cash/#ippon

You mean the one you've sent? Will investigate if possible.

Received zap tx holds the njump link that provides all details in browser when tapped.

More clear now.

Push notifications enabled are a must have for NWC to work properly.

If not enabled, there is a fallback websocket connection that behaves exactly as you describe (reconnects only on app foregrounded).

So enable push in Settings, then test. Thanks for looking at it that deep, any feedback is appreciated.