You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Maybe we can describe the field in that way, that you can enter all three ways from your provided link - as 2 letters , 3 letters or numeric ?!
Well, it may also be possible, but to keep consistency between all the descriptors that can be used by different use cases for specific reasons, it is best to keep one format.
Maybe we can describe the field in that way, that you can enter all three ways from your provided link - as 2 letters , 3 letters or numeric ?!
Well, it may also be possible, but to keep consistency between all the descriptors that can be used by different use cases for specific reasons, it is best to keep one format.
excactly that why we should keep it open for all 3 options - so we not limited upcoming use-cases
That country codes refers to what then? I think would only apply to account profile descriptors. Technically, it's possible to use the custom fields: x-cc for example
I propose that we expand the SRC-44 descriptor to include a new
OPTIONAL
property that refers to a "country code" in the description field structure.The key would be labeled as
ctry
and the value would be just anALPHA-2 Country code
https://www.iban.com/country-codes
These would be the properties
The text was updated successfully, but these errors were encountered: