W3C home > Mailing lists > Public > public-payments-wg@w3.org > August 2019

Re: ISO 20022 Re: SEPA Credit Transfer + W3C PaymentRequest

From: Anders Rundgren <anders.rundgren.net@gmail.com>
Date: Tue, 20 Aug 2019 08:24:22 +0200
To: Colinde <ulrike.linde@colinde.de>
Cc: KETELS Kris <Kris.KETELS@swift.com>, William Vanobberghen <william-vanobberghen@cartes-bancaires.com>, Web Payments Working Group <public-payments-wg@w3.org>
Message-ID: <582ddd9c-bd32-e4d4-3bdd-90aa41b7e0ce@gmail.com>
On 2019-08-20 07:20, Colinde wrote:
> Hi,

Hi Ulrike,

> did you analyze the Berlin Group API for online initiation of Credit Transfers?

Not yet.  I guess this is one of the related documents?
To me this looks quite messy from an interoperability point of view.

Since wire-transactions using on-line banking applications as well as mobile P2P systems like Swish, typically only require you to specify 1-3 items regarding the beneficiary, I do the assumption that this also is sufficient for wire-transactions (including SEPA inst) when initiated through Saturn.

However, a cool thing in Saturn which doesn't have counterparts in Open Banking APIs, is the use of "Authority Objects" [1] which permit the optional fetch of partner specific data without clobbering protocols.

Note that Saturn has no relationship whatsoever to Banking APIs; it is dedicated to traditional "Consumer Payments" which is a much more limited scope.

Kind regards, Mit freundlichen Grüßen,
Anders Rundgren

1] https://cyberphone.github.io/doc/defensive-publications/authority-objects.pdf

> Ulrike Linde
> Strategien für die digitale Gesellschaft
> Altenberger Weg 11
> 13156 Berlin
> M +49 179 21 22 548
>> Am 19.08.2019 um 21:21 schrieb Anders Rundgren <anders.rundgren.net@gmail.com>:
>> Dear Kris and William,
>> There is nowadays quite a bunch mobile payment systems which like Saturn have almost nothing in common with 7816-based card-schemes.
>> These systems typically also eliminate the card terminal; the phone/mobile device presents the payment request and it is (client-wise) fully authorized there as well.  This impacts on the rest of the infrastructure.
>> https://cyberphone.github.io/doc/saturn/personal-payment-terminal.pdf
>> Most of these systems are proprietary and require NDAs for closer studies.
>> This 167(!)-page document
>> https://www.europeanpaymentscouncil.eu/sites/default/files/kb/file/2019-06/MSG%20MSCT%20026-18v09%20MSCT%20IIGs.pdf
>> from the European Payment Council suggests that all those national players like Swish, iDEAL, PayLib, etc. should create an interoperability network.
>> That will most likely never happen because 1) the vendors lack incentive 2) it would be technically, commercially and politically close to infeasible which is one of the motivations behind Saturn.
>> So the situation (standards-wise) for mobile payments beyond EMV/NFC emulation like Apple and Google Pay is AFAICT currently pretty much zero.
>> Kind regards,
>> Anders
Received on Tuesday, 20 August 2019 06:24:49 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:33 UTC