View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008754 | Taler | libeufin-nexus | public | 2024-04-20 12:03 | 2024-04-20 12:03 |
| Reporter | Antoine A | Assigned To | Antoine A | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | assigned | Resolution | open | ||
| Target Version | 0.11 | ||||
| Summary | 0008754: Safer bouncing strategy | ||||
| Description | With ISO20022's fuzzy specifications and banks' variable implementation, it's possible to fail to identify reversal transactions, creating bounce loops. We need to be more restrictive about which transactions to bounce, we should only bounce transactions that we are absolutely sure are successful and not inversions. We also rely on the bank not executing two EBICS transactions with the same MsgId. All banks do this, but they don't store the old MsgId indefinitely. UBS, for example, keeps them for 90 days. Xe should add a cut-off date so that we don't bounce on transactions older than N days, just to be on the safe side. | ||||
| Tags | No tags attached. | ||||
