2587577 - Why is Routing Number a global field instead of being a country-specific field?

Routing Number field in Payment Information is a global field, though it is not used in all the countries. Why is this field not a country-specific field?

Employee Central: Payment Information

Routing Number field is used in a lot of coutries. Currently, Routing Number field is in use in the following countries: ARE, AUT, BRA, CAN, CHE, CHL, COL, DEU, ECU, EGY, ESP, FIN, FRA, GBR, IND, IRL, ITA, JPN, KEN, MEX, MYS, NGA, OMN, PHL, QAT, SAU, SGP, SWE, THA, TWN, VEN, ZAF, USA.

Routing Number is delivered as a global field since a lot of countries are using this field. Generally, if a field is in use for more than 10-15 countries, it is delivered as a global field.

This field can be left blank if the user belongs to a country where Routing Number is not in use. If it is not customized to be a compulsory field, there should not be any problem when the field is left blank or when it's visibility is none.

The field Routing Number (routingNumber) is known by different names in different countries. It is not possible to make the label country-specific, however, it can be maintained accordingly to logged in user's language through translations (in object definition of paymentInformationDetailsV3 as well as in the Manage Configuration UI -> Payment Information UI).

RTN, CSF , KBA , LOD-SF-EC-PAY , Payment Information (Bank Information) , Problem