View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011904 | Taler | wallet (all platforms) | public | 2026-10-30 21:33 | 2026-11-02 19:58 |
| Reporter | MarcS | Assigned To | Resolution deadline | ||
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | normal | Severity | feature | Reproducibility | have not tried |
| Status | implementing | Resolution | open | ||
| Target Version | 1.10 | ||||
| Summary | 0011904: TalDir: Implement push notifications | ||||
| Description | When someone sends a P2P transaction via TalDir, the recipient currently does not get notified. They must manually open their Taler Wallet regularly so it can check (poll) the MailBox whether a P2P message arrived. This is annoying, makes unnecessary network calls, and the user might forget to do it thus delaying the message arrival. Both Apple and Google operate a Push Notification Service, where the app can register itself to get a Token, which can then be integrated into the mailbox configuration. If a message arrives at the user's mailbox, the mailbox server can send the Token to the PN server, which will deliver it to the user's device, which then knows which app that PN belongs to. The recipient sees on their phone lockscreen that either money or a payment request arrived in their mailbox. They can either ignore/delete the notification, or tap on it to launch the Taler Wallet now - which then polls the mailbox to download and present the message. | ||||
| Additional Information | Currently the message content contains just the talerURI, and is E2E encrypted so only the recipient can decrypt and read it. I suggest that we should transfer two additional data fields: 1) Whether the message contains incoming money or a payment request (Boolean) 2) The message subject the sender typed in for the recipient (String, max 100 alphanumeric characters). Or even less... The subject 2) would get encrypted like the talerURI, so the mailbox service cannot know it. After downloading the messages from the mailbox service, Taler Wallet has the decrypted subjects and can directly show the list of messages with subjects, like a mail program does. Without this subject, the user only sees the talerURI (either "Send" or "Request"), so the wallet can only present the list with an incoming or outgoing icon and color. To be able to show more info about each transaction, it needs to query the exchange with the talerURI - thus network traffic, which might take some time. Consider a rockstar receiving dozens or hundreds of messages a day from fans sending some money... The boolean 1) however should be transferred unencrypted, so the mailbox service can read it, and transfer it with the Token to the PN server. Then the recipient will already see in the PN whether the message in the mailbox has incoming money or a payment request, without the need to open the wallet app. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-10-30 21:33 | MarcS | New Issue | |
| 2026-10-31 14:42 | Christian Grothoff | Status | new => implementing |
| 2026-10-31 14:42 | Christian Grothoff | Target Version | => 1.10 |