Danaus

💯 this is an example of an ISO20022 compliant XML payload. See, we very API has its own specific format and schema. So when you are dosing up a system to say use the API, you need to make sure you send in the right schema. But the issue is, there used to be 100s of different schemas, making integration far more complex with mediation and connector layers. ISO20022, written and ratified by a STANDARDS BODY, has collated dozens of recommendations from the industry and has documented an agreed by all standard that is flexibly enough to meet all (well most) needs. So when a bank wants to connect their mainframe to another service, the days payload compliance part is already done, and just need minor workflow changes. The same happened in medical systems, where FHIR Compliant APIs were written. It's actually quite an amazing achievement iso20022, getting the old crusty banks to agree, well at least a bunch of them. Fednow and SWIFT moving to ISO20022, means all banking systems using current messaging payloads, will need to migrate by a cutoff date, aster which these guys will switch off the old APIs (well, I doubt they will). No one knows this, but when Bluetooth was invented there were dozens of competing PAN wireless networks. So what made BT win? It was SONY drive and persistence, licensing their tech, championing hardware modules, that eventually made brandz just use Bluetooth and nothing else. This is what ISO20022 is all about. And it's been driven hard by SWIFT mainly. Ripple (not XRPL) took the lead and built ISO20022 adaptors for all of its APIs, this means the big boys can almost as easily switch from SWIFT to Ripple, the payloads are identical (well for sake of argument they are). This is the big game being played out. It has ABSOLUTELY NOTHING TO DO WITH CRYPTO, except there are some fields in the messaging standard that will enhance digital assets being involved. That's it. And once again, no blockchain currently uses (and doesn't need) to use the messaging standard. E.g. XRPL, you create a JSON of your transaction, this is not ISO20022 payload, much simpler. Then you sign the transaction (cryptographically) with your private wallet keys, and either send it to an API, or post to rippled. It is then "consensuses" and added to the chain. XLM, ETH, XDC and BTC and most others use a similar method, except method of adding to blockchain is different. I hope this once and for all clarifies this, happy to answer ws, but pls ffs don't post screenshots and docs claiming tokens are ISO20022 compliant, if you do I will expect blockchain documentation showing ISO20022 payloads. Good speed