View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010810 | Taler | General | public | 2025-12-19 02:04 | 2026-02-22 15:40 |
| Reporter | vecirex | Assigned To | Florian Dold | ||
| Priority | normal | Severity | tweak | Reproducibility | always |
| Status | assigned | Resolution | open | ||
| Target Version | 1.5 | ||||
| Summary | 0010810: Test case: use an IBAN twice (context: TOPS/CHF) | ||||
| Description | Using an IBAN twice (as in: adding the IBAN to another instance, although the given IBAN is already KYCed on *another instance) in the TOPS/CHF is known by @stefan and me to produce seemingly undefined behavior on the merchant side: it never works, so far; for one case, some people could also see it live in last week's QC meeting. Florian asked me to ship more analysis on this, so he can investigate; will do, then assign. * It doesn't matter if the instances using a given IBAN are all on one installation with self-provisioning or spread around on various machines: that is, the issue is global in the TOPF/CHF exchange scope. | ||||
| Additional Information | It's not clear what happens if an IBAN with kyc-required status is attempted to be KYCed on two instances; perhaps the first one added "wins"? This can be considered as subcase and given another IBAN not yet used, this can easily be tested. | ||||
| Tags | No tags attached. | ||||
| related to | 0010811 | assigned | Florian Dold | Test case: try to not use an IBAN anymore, deleting a bank account or the whole instance; can IBAN be reclaimed? [20min] |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-12-19 02:04 | vecirex | New Issue | |
| 2025-12-19 02:04 | vecirex | Status | new => assigned |
| 2025-12-19 02:04 | vecirex | Assigned To | => vecirex |
| 2025-12-19 02:13 | vecirex | Summary | Test case: use an IBAN twice => Test case: use an IBAN twice (context: TOPS/CHF) |
| 2025-12-19 02:13 | vecirex | Description Updated | |
| 2025-12-19 02:13 | vecirex | Additional Information Updated | |
| 2025-12-19 02:15 | vecirex | Description Updated | |
| 2025-12-19 02:15 | vecirex | Note Added: 0027118 | |
| 2025-12-19 02:18 | vecirex | Description Updated | |
| 2025-12-19 02:21 | vecirex | Note Edited: 0027118 | |
| 2025-12-19 02:22 | vecirex | Description Updated | |
| 2025-12-19 02:24 | vecirex | Description Updated | |
| 2025-12-19 02:25 | vecirex | Additional Information Updated | |
| 2025-12-20 11:39 | vecirex | Status | assigned => acknowledged |
| 2025-12-20 11:41 | vecirex | Assigned To | vecirex => |
| 2025-12-20 11:41 | vecirex | Status | acknowledged => confirmed |
| 2025-12-20 11:42 | vecirex | Note Added: 0027148 | |
| 2026-01-26 07:28 | Christian Grothoff | Severity | minor => tweak |
| 2026-01-26 07:28 | Christian Grothoff | Category | exchange => project management |
| 2026-01-26 07:28 | Christian Grothoff | Target Version | => post-1.0 |
| 2026-02-16 23:22 | Christian Grothoff | Target Version | post-1.0 => 1.5 |
| 2026-02-16 23:34 | Christian Grothoff | Relationship added | child of 0010811 |
| 2026-02-17 21:32 | Christian Grothoff | Assigned To | => Florian Dold |
| 2026-02-17 21:32 | Christian Grothoff | Status | confirmed => assigned |
| 2026-02-22 15:38 | Christian Grothoff | Relationship replaced | related to 0010811 |
| 2026-02-22 15:40 | Christian Grothoff | Project | Taler-Business => Taler |
| 2026-02-22 15:40 | Christian Grothoff | Category | project management => General |
