{"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":"Thanks, that narrows it down. I read both apps' code to rule things out:\n\n- Not an encryption mismatch. YakiHonne still sends NWC requests with NIP-04 (performNwcAction in its mobile-app repo), which is what Minibits speaks.\n- Not the relay. Minibits only listens for NWC on wss://relay.minibits.cash, and it answered fine when I checked just now.\n\nWhat's left, all inside Minibits (src/models/NwcStore.ts):\n\n1. Daily limit. Each NWC connection has its own daily cap. Over it, the wallet answers QUOTA_EXCEEDED. Also, if a zap is still in flight when the background listener shuts down, Minibits reserves that amount against the cap and sends no reply. A few stuck zaps can quietly eat the whole day's limit. Open the NWC connection in Minibits and check the remaining limit. Raise it or delete the connection and make a new one.\n2. Balance. If your balance on the mint the connection uses is below the zap plus fee, it returns INSUFFICIENT_BALANCE.\n3. Pending zaps. Look in Minibits' history for pending zaps from the last 2 days. If you find some, check them and let them settle first.\n\nIf none of that fixes it, paste a fresh NWC string from Minibits into YakiHonne. A one-off zap with the app open in front will often show the actual error text."}