View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003527 | Taler | specification | public | 2014-08-14 18:58 | 2015-09-22 13:15 |
| Reporter | Florian Dold | Assigned To | Marcello Stanisci | 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 | high | Severity | feature | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | git (master) | ||||
| Target Version | 0.0 | Fixed in Version | 0.0 | ||
| Summary | 0003527: contract text should be a contract json structure instead | ||||
| Description | ... making it somewhat easier to create / parse the contract (which may contain information such as a download location for a file) | ||||
| Tags | No tags attached. | ||||
| child of | 0003840 | closed | Marcello Stanisci | Update API/Documentation about the interaction between merchant and wallet |
| Not sure, I think this is something we should work with a certain W3c committee on. They may prefer XML for the contracts, or something entirely different. This is a good point to try to standardize actually across payment systems, as long as we clearly separate the contract from our details (amount, signatures, etc.). But maybe we can have a generic "meta" container: json with amount, signatures, and contract format, and then the contract in whatever the contract format says. | |
| We should investigate what documents W3c has produced to describe / standardize payment contracts. | |
| See also: http://www.w3.org/Payments/ | |
| Marcello, I think you're working on this, please link to the documentation if/when/where you create it. | |
| Current implementation now sends JSON, documentation still forthcoming (0003840). | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2014-08-14 18:58 | Florian Dold | New Issue | |
| 2015-01-09 17:55 | Christian Grothoff | Note Added: 0008769 | |
| 2015-01-28 15:33 | Christian Grothoff | Note Added: 0008817 | |
| 2015-01-28 15:33 | Christian Grothoff | Assigned To | => Sree Harsha Totakura |
| 2015-01-28 15:33 | Christian Grothoff | Status | new => assigned |
| 2015-01-28 15:40 | Christian Grothoff | Note Added: 0008818 | |
| 2015-03-28 13:40 | Christian Grothoff | Product Version | => git (master) |
| 2015-03-28 13:40 | Christian Grothoff | Target Version | => 0.1 |
| 2015-04-12 21:50 | Christian Grothoff | Category | other => merchant API (HTTP-based) |
| 2015-09-17 12:10 | Christian Grothoff | Assigned To | Sree Harsha Totakura => Marcello Stanisci |
| 2015-09-17 12:10 | Christian Grothoff | Note Added: 0009635 | |
| 2015-09-17 12:10 | Christian Grothoff | Severity | minor => feature |
| 2015-09-17 12:10 | Christian Grothoff | Target Version | 0.1 => 0.0 |
| 2015-09-17 12:14 | Christian Grothoff | Relationship added | child of 0003840 |
| 2015-09-19 18:37 | Christian Grothoff | Priority | normal => high |
| 2015-09-21 14:33 | Christian Grothoff | Note Added: 0009656 | |
| 2015-09-21 14:33 | Christian Grothoff | Status | assigned => informing |
| 2015-09-21 14:33 | Christian Grothoff | Fixed in Version | => 0.0 |
| 2015-09-21 14:33 | Christian Grothoff | Resolution | open => fixed |
| 2015-09-22 13:15 | Christian Grothoff | Status | informing => closed |
| 2015-11-29 12:52 | Christian Grothoff | Category | merchant API (HTTP-based) => merchant backend API (HTTP specification) |
| 2024-01-12 13:02 | Christian Grothoff | Category | merchant backend API (HTTP specification) => specification |