The wallets we have tested.

• App open. The first payment, at the moment of signing.
• In the background, with the phone locked. A whole night, on charge: 8 payments out of 8, one an hour. Network fees: zero.
• App fully closed. Four attempts in forty minutes, no answer: the iPhone does not wake up an app you closed yourself, and the keys are only on the phone. On our public plan, which has no grace period, the subscription stopped. The same goes for a phone that is switched off.
• Connects by pasting. You create the connection in Zeus — Tools, Nostr Wallet Connect — with the limit and the end date shown on the signing page, and paste it there. After pressing the button, stay on the page: Zeus pays the first payment even from the background. Zeus offers to grant almost every permission, but lets you choose: two are enough, paying invoices and checking them.
• Revoking stops the payments. On 27 September we removed the connection in Zeus: from then on not a single sat went out, and the subscription stopped on its own.
• But PullCap cannot tell it was a revocation. When you remove the permission, Coinos answers “no”; Zeus, even with the app in the background, stays silent. To PullCap, a removed connection and a closed app look the same: the subscription stops the way it does when the wallet does not answer, after the retries and the grace period the seller chose.
• For sellers, not on the phone. To receive on a Lightning address, Zeus goes through ZEUS Pay: with ecash, the payments stay with a “mint”, the service that issues the tokens; with Zaplocker, they stay on hold until you open the app, and after 24 hours they go back. Neither way do you get paid on your own, in self-custody.

If you use it to pay a subscription: do not swipe it away from your open apps. Fully closed, it does not answer, the payments stop and, if it stays closed too long, the subscription is suspended.

• App fully closed: it paid twice. On the evening of 27 September, swiped away from the open apps: two hourly payments went out on their own, with the correct Lightning proof.
• Then it stopped. At the midnight payment, an hour and forty minutes after closing, it no longer answered. Zeus’s two permanent notifications had already disappeared about ten minutes after closing: on our phone the service does not survive closing the app. Once the app was reopened, Zeus answered again.
• In the background, the same. Later that night, leaving the app without closing it: it paid once, half an hour later; an hour after that it no longer answered, and the permanent notifications had disappeared again.
• It paid when it woke up, and PullCap found it. On the night of 29 September it did not answer the attempts between one and two. At 7:48 it woke up and paid what had been left pending: a single sat, not one per attempt, because the invoice was always the same. On our public plan, which has no grace period, the subscription had already been suspended: that same evening PullCap found the payment, recorded it and showed it to both the seller and the payer.
• Without Express Graph Sync, the first payment stops. Zeus holds it and asks whether to turn it on: with the app closed, nobody answers. Turn it on before you sign.
• Revoking stops the payments. On the evening of 29 September we removed a connection right after signing: from then on not a single sat went out.
• But, as on the iPhone, PullCap cannot tell it was a revocation. At the next payment, four attempts without an answer, and the subscription stopped the way it does when the wallet does not answer. Yet Zeus was awake: in the same minutes, from the same phone, it was paying the subscription of the phone acting as a node, below. To the removed connection it answered neither yes nor no.
• Does the spending limit hold with the app closed? On the 27th, after the payments made with the app closed, the connection in Zeus still showed 0 of 27 sats spent; on the 29th, after two payments, one with the app open and one when it woke up, it showed 1. We will keep testing it, with a very low limit.

Good to know: on battery, on our phone, Zeus did not stay awake all night, neither closed nor in the background, even with all three settings on. Every manufacturer handles the battery its own way, and on another Android phone it may go differently: that is why we are also testing it always on charge, below.

• Almost two days: 45 payments out of 45. From 23:37 on 29 September to 19:40 on 1 October, one an hour, day and night, on our 1-sat-an-hour public plan. On the first night, network fees: zero.
• All with the Lightning proof but one. At 7:40 on 30 September Zeus’s answer came without the proof: PullCap asked the wallet about that invoice, and the wallet confirmed the payment. For that one, the receipt is the wallet’s word.
• Then it stopped. On 1 October, at the 20:37 payment, no answer: four attempts in forty minutes, and at 21:30 PullCap suspended the subscription, as it does with a wallet that does not answer. In Zeus the service showed as active; the phone was on charge, with the screen on.
• On charge, but with the screen off? We did not try it: the screen stayed on the whole time.

What we take from it: a subscription needs a wallet that answers even when nobody is looking at it. For a phone, almost two days is more than enough of a test. The next step is a real node, to see how PullCap behaves in every respect.

• App open. The first payment, at signing, arrived within seconds, and so did the one an hour later.
• In the background: 39 payments out of 39. From signing, on 30 September at 10:53, until 1:00 a.m. on 2 October, one an hour, all with the Lightning proof, with a connection created after turning on the automatic start of the service (auto start wallet service). In everyday use: on Wi-Fi and on mobile data, on charge and on battery. 35 on the first attempt, 4 after one or more retries.
• By day, on battery. On 30 September the phone stayed off the charger all day, while we were at work. Two payments with the phone locked and the screen off, left alone for two hours.
• At night, on charge: 8 payments out of 8. Between 30 September and 1 October, from 23:00 to 6:00, with the phone locked and Sleep Focus on: all on the first attempt. On the first night, between the 28th and the 29th, with a connection created before turning on the automatic start, it had stopped after one o’clock.
• The second night: to be re-checked. Between 1 and 2 October, around 2:00 a.m., the NWC service stopped: the phone was on charge, in Sleep Focus, and the iPhone may have closed the app after a few hours. On our public plan, which has no grace period, one pause is enough to suspend the subscription; on a monthly subscription the retries last days, and the seller chooses the grace period. We are re-checking it.
• App fully closed: it does not answer. A couple of times the app was swiped away from the open apps, by mistake too, as happens: the NWC service stopped and the payments did not go out. Once reopened, it paid at the next attempt: no payment lost, only late. If it stays closed for longer than the attempts, the subscription is suspended, as with any wallet that does not answer.
• Connects by pasting. You create the connection in Primal and paste it on the signing page. The lowest limit Primal lets you choose is 1000 sats: it is only a cap, not a charge.
• Revocation: does it say “no”, or stay silent? Still to be tested, with the app open.

Good to know: on our 1-sat payments, Primal’s fee was 3 sats: each payment cost us 4 sats, as the balance shows. We have not seen it on larger amounts yet. It is a test on a single phone: we will update it as it goes.

• Pays every hour. So far 244 payments out of 244: the first at signing, on 2 October at 18:33, in 3 seconds; then one an hour, all with the Lightning proof, and all on the first attempt but one: on the evening of 11 October a request went unanswered, and the payment went through on the second attempt, less than a minute later. Fees, on 1-sat payments: zero for the first 27, then 1 sat each. The Lightning network sets them, not PullCap.
• For sellers too. On 3 October we signed up as sellers with our Alby Hub: the sat with the code arrived, and the code can be read in Transactions, under “Description” and “Comment”. Then one of our Coinos accounts signed a 1-sat-an-hour plan: so far 229 payments out of 229, the first in 4 seconds, all with the Lightning proof, and all on the first attempt but one: on the morning of 11 October a request went unanswered, and the payment went through nine minutes later, on the next round. So the same node pays and gets paid; but it only gets paid while the computer is on.
• With Alby Go fully closed, it pays all the same. On the phone there is also Alby Go, which holds no keys: it is a remote control for the node. It stayed fully closed for the whole test, and the payments went out all the same: the computer pays, not the phone.

Good to know: paying on Lightning needs a channel. On the first deposit Alby Hub opens one, and the opening is paid once: for us it cost 3,514 sats. And, like any node, it only pays and gets paid while it is on and connected to the network: on a home computer, as long as the computer is on. We will test the version in Alby’s cloud later.

• Pays, even with the tab closed. So far 122 payments out of 122, one an hour: the first at signing, on 7 October at 20:41, in 4 seconds; then day and night, even with the Rizful tab fully closed. All with the Lightning proof, and a fee of 1 sat each.
• Gets paid, even with the tab closed. Since 10 October Rizful is on the seller side too: a seller of ours signed up with a Rizful address, reading the code in the note of the sat, in quotes. One of our Coinos accounts pays it, one an hour: so far 70 payments out of 70, all with the Lightning proof, at night too with the tab closed. The first went through on the second attempt: the Coinos connection had its maximum fee set too low.

Good to know: the connection does not open with one click, like the Coinos one: you create it in Rizful and paste it on the signing page. Rizful itself recommends keeping there only the sats you expect to use soon.