View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007365 | Taler | specification | public | 2022-09-18 09:33 | 2024-08-12 07:49 |
| Reporter | Christian Grothoff | 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 | low | Severity | feature | Reproducibility | N/A |
| Status | acknowledged | Resolution | open | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | git (master) | ||||
| Target Version | post-2.0 | ||||
| Summary | 0007365: KYC fee is never charged / not speced or implemented | ||||
| Description | The taler-exchange-offline tool (already) has a means to specify a KYC fee, and in principle the "/kyc-check" endpoint could generate a 402 payment required for the KYC process. However, the detailed 402 response is unspecified and also not implemented. | ||||
| Tags | No tags attached. | ||||
| There's now a high-level hint of the exchange possibly returning a 402 in the /kyc-check spec. | |
| Discussion today: have different KYC fees per trigger. | |
| Charge KYC fees either to reserve (incl. wallet's long-term reserve for balance trigger) or to outgoing wire amount. | |
| As long as frees cannot be paid, transaction is simply on hold until KYC threshold is gone below or balance goes high enough to pay KYC fee. | |
| Given that AML may trigger KYC, I think the _only_ case where we legitimately can and should charge a KYC fee is if a client explicitly asks for it -- e.g. because they want to get attributes signed for invoicing. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-09-18 09:33 | Christian Grothoff | New Issue | |
| 2022-09-18 09:33 | Christian Grothoff | Status | new => assigned |
| 2022-09-18 09:33 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2022-09-22 13:36 | Christian Grothoff | Note Added: 0019170 | |
| 2022-10-18 17:17 | Christian Grothoff | Note Added: 0019224 | |
| 2022-10-18 17:27 | Christian Grothoff | Note Added: 0019225 | |
| 2022-10-18 17:27 | Christian Grothoff | Note Added: 0019226 | |
| 2022-10-18 17:28 | Christian Grothoff | Note Edited: 0019226 | |
| 2022-12-20 17:27 | Christian Grothoff | Target Version | 0.9.1 => 0.9.2 |
| 2022-12-29 23:37 | Christian Grothoff | Target Version | 0.9.2 => git (master) |
| 2022-12-29 23:37 | Christian Grothoff | Status | assigned => implementing |
| 2022-12-29 23:38 | Christian Grothoff | Priority | normal => low |
| 2022-12-29 23:38 | Christian Grothoff | Status | implementing => assigned |
| 2023-01-21 20:21 | Christian Grothoff | Note Added: 0019697 | |
| 2023-04-04 13:53 | Florian Dold | Target Version | git (master) => post-1.0 |
| 2023-04-08 08:02 | Christian Grothoff | Assigned To | Christian Grothoff => |
| 2023-04-08 08:02 | Christian Grothoff | Status | assigned => implementing |
| 2023-12-24 05:49 | Christian Grothoff | Status | implementing => acknowledged |
| 2024-01-12 13:03 | Christian Grothoff | Category | exchange API (HTTP specification) => specification |
| 2024-08-12 07:49 | Christian Grothoff | Target Version | post-1.0 => post-2.0 |