View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006521 | Taler | wallet-core | public | 2020-08-24 06:32 | 2022-11-04 19:52 |
| Reporter | Florian Dold | Assigned To | Christian Grothoff | 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 | closed | Resolution | fixed | ||
| Product Version | git (master) | ||||
| Target Version | 0.9 | Fixed in Version | 0.9 | ||
| Summary | 0006521: spec and implement "return coins to bank account" feature | ||||
| Description | We need to take care of two things: * the API that wallet-core provides for this * the user experience we want and that the UI should implement | ||||
| Tags | No tags attached. | ||||
| has duplicate | 0005118 | closed | Florian Dold | allow new customer wire information to be added |
| One scenario I would like to see here is simply scanning a payto:// QR code with the Taler wallet. If that QR code comes with a supported wire format, we could "play" merchant and simply offer to wire funds to the respective account (only asking the user 'how much' to send, while making it clear that there will be no 'contract' associated with this). This is actually needed in cases like at BFH where someone may give a cashier *cash* and then later wants the ecash back into their bank account (but NOT the cashier's bank account!). I hope the origin of cashier's coins already shows up as payto://void/ as we had discussed. :-) A second case I would imagine is that under 'settings', we could have a *list* of "origin bank accounts" where we list the origins (bank name, account number) of the banks from which we have done withdrawals (except maybe payto://void/?), and _there_ offer to (a) forget origin (datenschutz!), or (b) send money back to origin. | |
| High level design is done, only UI tweaks left, resolving. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-08-24 06:32 | Florian Dold | New Issue | |
| 2020-08-24 12:38 | Christian Grothoff | Note Added: 0016742 | |
| 2020-08-24 20:34 | Christian Grothoff | Status | new => feedback |
| 2020-08-24 20:34 | Christian Grothoff | Category | other => wallet (TS core) |
| 2020-08-24 20:34 | Christian Grothoff | Product Version | => git (master) |
| 2020-09-05 11:53 | Christian Grothoff | Severity | minor => feature |
| 2020-09-08 15:44 | Florian Dold | Relationship added | has duplicate 0005118 |
| 2022-08-25 18:54 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2022-08-25 18:54 | Christian Grothoff | Status | feedback => informing |
| 2022-08-25 18:54 | Christian Grothoff | Resolution | open => fixed |
| 2022-08-25 18:54 | Christian Grothoff | Fixed in Version | => 0.9 |
| 2022-08-25 18:54 | Christian Grothoff | Note Added: 0019042 | |
| 2022-08-25 18:55 | Christian Grothoff | Target Version | => 0.9 |
| 2022-11-04 19:52 | Christian Grothoff | Status | informing => closed |
| 2023-04-13 18:36 | Florian Dold | Category | wallet (TS core) => wallet-core |