CH IBAN / QR-IBAN problem #2985
Comments
|
Thanks for describing the issue! Just to make sure I understand: are you saying that one of the IBAN codes that faker generates could also fall into the category of a QR-IBAN in case it matches a bank's QR-IID? Is there a way to tell them apart (IBAN vs QR-IBAN)? Is there a list of QR-IIDs somewhere? And for your application, why would it matter if the generated code is IBAN or QR-IBAN - are they used in different situations? Maybe this could be an addition to the documentation. It feels more like a feature request to me than a bug, but I need a bit more context. |
thdaraujo
added
🙏🏽 Issue: Needs More Information
and removed
💡 Issue: Feature Request
labels
|
I accidentally selected a bug issue instead of open issue, sorry for that.
Exactly
The QR-IBAN contains the QR-IID (bank identification) in positions 5-9, using a number range from 30000 through 31999.
Because a valid QR reference is required for a transfer to a QR-IBAN |
Describe the bug
It's not really a technical problem, but you can run into problems in your tests. In Switzerland there are 2 types of IBANs. Normal and QR-IBAN.
How does the QR-IBAN differ from the IBAN?
Instead of the regular IBAN, the client's bank assigns them a QR-IBAN for the credit account. This is required to identify the beneficiary account. The only difference between the QR-IBAN and the IBAN is a different institution identification (IID), the QR-IID. Each legally independent financial institution participating in the procedure is assigned at least one QR-IID. The QR-IID of UBS Switzerland AG is 30005.
https://www.ubs.com/ch/en/corporates/payment-solutions/payments/payment-slips/faq.html
There is therefore the possibility of unreliable tests if such a QR-IBAN is generated by chance.
To Reproduce
Faker::VERSION => "3.4.2"
Additional context
I don't have a quick solution for this either, as the structure of locales/en/bank.yml does not provide an option for this.
The text was updated successfully, but these errors were encountered: