View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0008528 | Taler | specification | public | 2024-02-28 00:54 | 2024-04-15 21:32 |
Reporter | Florian Dold | Assigned To | Christian Grothoff | ||
Priority | normal | Severity | text | Reproducibility | have not tried |
Status | closed | Resolution | fixed | ||
Target Version | 0.10 | Fixed in Version | 0.10 | ||
Summary | 0008528: DD53: decide on consistent terminology for p2p payments | ||||
Description | We currently use inconsistent terminology in the various apps,. | ||||
Tags | No tags attached. | ||||
|
Examples please? |
|
webext wallet uses: * Digital cash transfer * send money "to another wallet" * Transfer (label for the transaction) * Digital cash invoice Android: * "push payment" (no p2p) * "receive funds" then "invoice another wallet" * "send funds" then "to another wallet" (next dialog "send money") * "request payment" / "create invoice" iOS: * payment request * P2P * request money |
|
- IMO push and pull payments are internal terms, not useful for public consumption ;-). - P2P payments is an "industry" term, also not ideal for users. - Invoice is a legal term, not all pull payments are invoices, thus sub-optimal - Digital cash transfer is unclear as to the direction; and "Digital" is redundant-ish. - "send funds" + "to another wallet" and "send money" + "to another wallet" are both good, "money" is better ("funds" is more complex language) - "receive money" + "from another wallet" would be a natural dual to "send money" + "to another wallet" (symmetry is good) In summary, I would propose we use a mixture of all of the above: - "send money" + "to another wallet" and - "receive money" + "from another wallet". These are unambiguous, short formulations using easy language and also perfectly symmetrical. The 2nd stage should then be combined with the choices "to a bank account" and "from your bank account" to address withdraw + deposit use-cases (as done by AFAIK WebEx and Android). |
|
Your proposed terminology LGTM. |
|
dae8e91d..13345912 updates the spec in light of this bug. There is likely more, but we need to make general progress on *implementing* DD53 before we can spec more. |
Date Modified | Username | Field | Change |
---|---|---|---|
2024-02-28 00:54 | Florian Dold | New Issue | |
2024-02-28 00:54 | Florian Dold | Status | new => assigned |
2024-02-28 00:54 | Florian Dold | Assigned To | => Christian Grothoff |
2024-02-28 23:12 | Christian Grothoff | Severity | minor => text |
2024-02-28 23:12 | Christian Grothoff | Note Added: 0021569 | |
2024-02-28 23:12 | Christian Grothoff | Assigned To | Christian Grothoff => Florian Dold |
2024-02-28 23:12 | Christian Grothoff | Status | assigned => feedback |
2024-03-01 00:27 | Florian Dold | Note Added: 0021591 | |
2024-03-01 00:27 | Florian Dold | Assigned To | Florian Dold => Christian Grothoff |
2024-03-02 19:11 | Christian Grothoff | Note Added: 0021611 | |
2024-03-02 19:11 | Christian Grothoff | Assigned To | Christian Grothoff => Florian Dold |
2024-03-05 23:13 | Christian Grothoff | Relationship added | child of 0008534 |
2024-03-07 17:41 | Florian Dold | Note Added: 0021760 | |
2024-03-07 17:41 | Florian Dold | Assigned To | Florian Dold => Christian Grothoff |
2024-03-07 17:41 | Florian Dold | Status | feedback => assigned |
2024-04-06 01:24 | Christian Grothoff | Relationship deleted | child of 0008534 |
2024-04-07 22:19 | Christian Grothoff | Note Added: 0022140 | |
2024-04-07 22:19 | Christian Grothoff | Status | assigned => resolved |
2024-04-07 22:19 | Christian Grothoff | Resolution | open => fixed |
2024-04-07 22:19 | Christian Grothoff | Fixed in Version | => 0.10 |
2024-04-15 21:32 | Christian Grothoff | Status | resolved => closed |