View Issue Details

IDProjectCategoryView StatusLast Update
0010810TalerGeneralpublic2026-03-20 23:55
Reportervecirex Assigned ToFlorian Dold Resolution deadline
ImplementerReviewer 
Release signed byDeployed by 
VerifierCommunicator 
Data protection authority notification requiredNo  
CSIRT notification requiredNo  
Estimated effort (hours)Actual effort (hours)0 
Fast-trackNo
Work packagenone
PrioritynormalSeveritytweakReproducibilityalways
Status closedResolutionfixed 
Target Version1.5Fixed in Version1.5 
Summary0010810: Test case: use an IBAN twice (context: TOPS/CHF)
DescriptionUsing 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 InformationIt'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.
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Relationships

related to 0010811 closedChristian Grothoff Test case: try to not use an IBAN anymore, deleting a bank account or the whole instance; can IBAN be reclaimed? [20min] 

Activities

vecirex

2025-12-19 01:15

administrator   ~0027118

Last edited: 2025-12-19 01:21

some lang fixes++

vecirex

2025-12-20 10:42

administrator   ~0027148

As suggested by CG: using MantisBT properly also means to stop assigning everything to oneself or even others, IF work on it is currently not being done!

Florian Dold

2026-03-12 12:08

manager   ~0028116

This is already covered by the merchant-kyc-auth-multi test.

Issue History

Date ModifiedUsernameFieldChange
2025-12-19 01:04vecirexNew Issue
2025-12-19 01:04vecirexStatusnew => assigned
2025-12-19 01:04vecirexAssigned To => vecirex
2025-12-19 01:13vecirexSummaryTest case: use an IBAN twice => Test case: use an IBAN twice (context: TOPS/CHF)
2025-12-19 01:13vecirexDescription Updated
2025-12-19 01:13vecirexAdditional Information Updated
2025-12-19 01:15vecirexDescription Updated
2025-12-19 01:15vecirexNote Added: 0027118
2025-12-19 01:18vecirexDescription Updated
2025-12-19 01:21vecirexNote Edited: 0027118
2025-12-19 01:22vecirexDescription Updated
2025-12-19 01:24vecirexDescription Updated
2025-12-19 01:25vecirexAdditional Information Updated
2025-12-20 10:39vecirexStatusassigned => acknowledged
2025-12-20 10:41vecirexAssigned Tovecirex =>
2025-12-20 10:41vecirexStatusacknowledged => implementing
2025-12-20 10:42vecirexNote Added: 0027148
2026-01-26 06:28Christian GrothoffSeverityminor => tweak
2026-01-26 06:28Christian GrothoffCategoryexchange => project management
2026-01-26 06:28Christian GrothoffTarget Version => post-1.0
2026-02-16 22:22Christian GrothoffTarget Versionpost-1.0 => 1.5
2026-02-16 22:34Christian GrothoffRelationship addedchild of 0010811
2026-02-17 20:32Christian GrothoffAssigned To => Florian Dold
2026-02-17 20:32Christian GrothoffStatusimplementing => assigned
2026-02-22 14:38Christian GrothoffRelationship replacedrelated to 0010811
2026-02-22 14:40Christian GrothoffProjectTaler-Business => Taler
2026-02-22 14:40Christian GrothoffCategoryproject management => General
2026-03-12 12:08Florian DoldNote Added: 0028116
2026-03-12 12:09Florian DoldStatusassigned => informing
2026-03-12 12:09Florian DoldResolutionopen => fixed
2026-03-19 17:38Christian GrothoffFixed in Version => 1.5
2026-03-20 23:55Christian GrothoffStatusinforming => closed