-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Commerzbank's usage of differenz BICs #188
Comments
I think I'm not entirely sure what you're suggesting to implement. On which basis should the bank code |
@rtwruck you can add multiple combinaison of valid BIC for the same bank code. We did it in France for BNP which has a similar complexity. It will work for validation, however when trying to get the BIC from the IBAN it can either give you the list or the most plausible option. In anycase, both BIC would work if you try to wire money to it. |
Yes it goes both ways, multiple bank codes can share the same BIC and multiple BIC can be linked to the same bank code |
Hi,
I'm not so sure whether 2) is a good idea but OTOH the current list of domestic bank codes is already 285 entries long. |
Hi,
Commerzbank, like many german banks, uses regional BICs. For example:
BLZ 20040000 ->
COBADEHHXXX
Commerzbank HamburgBLZ 30040000 ->
COBADEDDXXX
Commerzbank DüsseldorfThis data is also present in schwifty and matches the Bundesbank database.
Unfortunately though, Commerzbank decided to use
COBADEFFXXX
for all SEPA transactions regardless of which BLZ is encoded in the IBAN. So if you receive a payment, the account statement will have IBANDExx 2004 0000 ....
with BICCOBADEFFXXX
and the same combination should be used when transfering money (see https://www.commerzbank.de/service/wo-finde-ich-meinen-bic-meine-blz-bankleitzahl/).Currently, this will not pass schwifty's validation, i.e. the example IBAN's BIC will obviously be
COBADEHHXXX
andBIC.candidates_from_bank_code('DE', '20040000')
will only return that one, too.Are there any plans to support this?
The text was updated successfully, but these errors were encountered: