3 ms·
.. until it ends with "SWIFT is incompatible with GDPR". (Okay, privacy wise, some might have uneasiness with SWIFT but we're talking about how it can't handle
by zinekeller 5y ago
.. until it ends with "SWIFT is incompatible with GDPR".
(Okay, privacy wise, some might have uneasiness with SWIFT but we're talking about how it can't handle (in this case) characters outside US-ASCII, unless you have negotiated it with the bank you're sending on, which if it's a US bank, is not supported: https://twitter.com/ajlobster/status/735240869859753985 https://twitter.com/ajlobster/status/735240869859753985)
- PeterisP 5y agoI'm not sure about the speed and schedule of adoption, but I believe that SWIFT systems across the world (including USA!) are migrating towards ISO 20022 messages which has technical support for characters outside US-ASCII; and requirements such as these are a driving factor to migrate away from the earlier SWIFT MT standards.
- zinekeller 5y ago... hopefully, but I wouldn't be shocked if the systems can technically receive Unicode-encoded transfers but then "convert" it into ASCII/EBCDIC at their mainframes :/