- From: Anders Rundgren <anders.rundgren.net@gmail.com>
- Date: Sat, 21 Sep 2019 15:13:19 +0200
- To: KETELS Kris <Kris.KETELS@swift.com>, William Vanobberghen <william-vanobberghen@cartes-bancaires.com>
- Cc: Web Payments Working Group <public-payments-wg@w3.org>
We never received any information on ISO 20022 or SWIFT's efforts addressing the client side of things. It is the same as with EBA's R2P (Request To Pay) [1] which also is claimed to solve all issues. A problem is that nobody really knows what "all" issues means which is not that surprising given that it is a moving target. One solution is creating complex APIs with tons of (often redundant) information. Another solution is creating nimble, scenario-specific APIs like Saturn. Anyway, whatever solution you settle for an API will surely at some point in time "run out of gas". The monumental success of DNS shows that lookup is a way forward. To make Saturn more agile with respect to requirement changes, I have applied this concept to high level business messaging: https://cyberphone.github.io/doc/research/casting-apis-in-stone.pdf Maybe ISO and SWIFT has something similar? Anders 1] https://www.ebaclearing.eu/media/azure/production/2262/190916_eba-cl_r2p_whitepaper.pdf
Received on Saturday, 21 September 2019 13:13:45 UTC