View Issue Details

IDProjectCategoryView StatusLast Update
0006741Talerlibeufin-nexuspublic2023-09-25 13:31
ReporterMS Assigned ToMS  
PrioritynormalSeverityminorReproducibilityhave not tried
Status resolvedResolutionno change required 
Target Versionpost-1.0 
Summary0006741: bank account operation affects the whole connection
DescriptionThe "fetch-transactions" API offered by Nexus operates under one bank account imported name. However,
the actual Camt record is asked in the name of the *connection*. If one connection can host two bank accounts,
then asking for account A will involve *also* account B, leading to confusion.
TagsNo tags attached.

Activities

MS

2023-09-25 11:56

manager   ~0020541

Nexus 'connection' has been discarded, so this won't apply anymore, just strictly speaking. However, the case where Nexus has more than one bank account has to be handled by the camt parser.

I'd anyway suggest to close this and reopen one that doesn't mention any obsolete data model element like 'connection', but addresses the multiple bank accounts reported in one camt document.

Christian Grothoff

2023-09-25 12:13

manager   ~0020544

Makes sense. I understand that this is the case where we then filter by the IBAN (or account number) in the configuration, right? Please open a reformulated bug report and then close this one referring to the new one in a note.

MS

2023-09-25 13:31

manager   ~0020545

Yes, filtering is one way to cut on complexity. Here's the new bug: 0007942, and I'm closing this.

Issue History

Date Modified Username Field Change
2021-02-05 14:13 MS New Issue
2023-01-08 11:38 Christian Grothoff Target Version => 0.9.2
2023-02-15 11:39 MS Target Version 0.9.2 =>
2023-04-13 20:38 Florian Dold Category nexus => libeufin-nexus
2023-04-13 20:50 Florian Dold Project libeufin => Taler
2023-04-17 11:54 Florian Dold Target Version => 0.9.5
2023-09-23 16:21 Christian Grothoff Target Version 0.9.5 => post-1.0
2023-09-25 11:56 MS Note Added: 0020541
2023-09-25 12:13 Christian Grothoff Note Added: 0020544
2023-09-25 13:31 MS Note Added: 0020545
2023-09-25 13:31 MS Assigned To => MS
2023-09-25 13:31 MS Status new => resolved
2023-09-25 13:31 MS Resolution open => no change required