View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011183 | Taler | specification | public | 2026-03-04 13:57 | 2026-03-04 13:57 |
| Reporter | Christian Grothoff | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | confirmed | Resolution | open | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | git (master) | ||||
| Target Version | post-1.0 | ||||
| Summary | 0011183: swap ToS and KYC Auth steps in UX | ||||
| Description | The more common UX is that the ToS acceptance comes first, and the KYC AUTH step also takes too long to be a first step. It would be better if KYC AUTH came last in the UX. But we cannot change this in the protocol, so the idea is to allow the merchant to *ask* for the ToS acceptance first, and then to have the merchant backend 'fake' the ToS acceptance submission after it learns KYC AUTH is done. This will be a MAJOR hack and requires both API changes, specification changes, and work in exchange and merchant. | ||||
| Tags | ux | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-03-04 13:57 | Christian Grothoff | New Issue | |
| 2026-03-04 13:57 | Christian Grothoff | Status | new => confirmed |
| 2026-03-04 13:57 | Christian Grothoff | Tag Attached: ux |
