View Issue Details

IDProjectCategoryView StatusLast Update
0010968Talerspecificationpublic2026-03-08 07:39
ReporterChristian Grothoff Assigned ToChristian Grothoff 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
PrioritylowSeverityfeatureReproducibilityN/A
Status closedResolutionnot fixable 
Platformi7OSDebian GNU/LinuxOS Versionsqueeze
Product Versiongit (master) 
Target Version1.5Fixed in Version1.5 
Summary0010968: use KYC AUTH only instead of entering bank accounts into mechant SPA
DescriptionWe have an issue where users enter their IBAN but then do the KYC Auth transfer from a different account.
The receiver-name could also have a mismatch. Both problems could be solved if we *only* show the KYC AUTH
instructions (on exchanges that do KYC, that is) and have the merchant backend "learn" the IBAN by requesting it from the exchange who learns it from the incoming wire transfer.

(suggested by Oec).
Tagsux

Required notifications

Address or linkRemarkAdded byNotifiedActions

Activities

Christian Grothoff

2026-03-08 07:38

manager   ~0028033

There is a bit of an issue with this: without the customer's account number, we don't know which wire transfer instructions to provide. An exchange may have multiple accounts with different *credit restrictions*. Given the customer's account, we can tell which of these are relevant and whether the wire transfer is going to be technically possible and acceptable to the exchange. But if we just show the wire transfer instructions, they may be impossible or even the merchant might be able to do it but then the account might not work anyway. So I think it is actually always better to first ask for their account, allow the merchant backend/SPA to check that the account would work with the exchange (technically and legally) and only then show the (correct) wire transfer instructions.

Christian Grothoff

2026-03-08 07:39

manager   ~0028034

Closing as it turns out this is not really feasible.

Issue History

Date ModifiedUsernameFieldChange
2026-02-02 12:16Christian GrothoffNew Issue
2026-02-02 12:16Christian GrothoffStatusnew => assigned
2026-02-02 12:16Christian GrothoffAssigned To => Christian Grothoff
2026-02-02 12:17Christian GrothoffStatusassigned => implementing
2026-02-04 21:40Christian GrothoffSummaryuse KYC AUTH only instead of entering bank accounts into mechant SPA => use KYC AUTH only instead of entering bank accounts into mechant SPA [7d]
2026-03-07 15:51Christian GrothoffTag Attached: ux
2026-03-07 17:30Christian GrothoffPrioritynormal => low
2026-03-08 07:38Christian GrothoffNote Added: 0028033
2026-03-08 07:38Christian GrothoffStatusimplementing => informing
2026-03-08 07:38Christian GrothoffResolutionopen => not fixable
2026-03-08 07:38Christian GrothoffFixed in Version => 1.5
2026-03-08 07:39Christian GrothoffTarget Versionpost-1.0 => 1.5
2026-03-08 07:39Christian GrothoffSummaryuse KYC AUTH only instead of entering bank accounts into mechant SPA [7d] => use KYC AUTH only instead of entering bank accounts into mechant SPA
2026-03-08 07:39Christian GrothoffStatusinforming => closed
2026-03-08 07:39Christian GrothoffNote Added: 0028034