W3C home > Mailing lists > Public > public-webpayments-ig@w3.org > February 2016

Re: On a PISP flow [Was: Feedback from Harry Halpin and Ian Jacobs to European Banking Authority Discussion Paper]

From: Frédéric Meignien <frederic.meignien@cantonconsulting.fr>
Date: Thu, 11 Feb 2016 00:32:17 +0100
To: "'Telford-Reed, Nick'" <Nick.Telford-Reed@worldpay.com>, Matt Saxon <saxonmatt@hotmail.com>
Cc: public-webpayments-ig@w3.org, "ij@w3.org" <ij@w3.org>, Jean-Yves Rossi <jean-yves.rossi@cantonconsulting.fr>, David Ezell <David_E3@VERIFONE.com>, "evert.fekkes@rabobank.nl" <Evert.Fekkes@rabobank.nl>, Paddy Ramanathan <paddy.ramanathan@gmail.com>, VIGNET cyril <Cyril.VIGNET@bpce.fr>
Message-ID: <56BBC881.1010707@cantonconsulting.fr>
Hello Nick, Hello Matt,
could we have a chat or a mail exchange about the questions raised by 
Ian in the message hereafter ?
Impacts of PSD2 on the flows are certainly to consider (since PSD2 
creates a play ground for new actors) and I would appreciate to know 
your approach on the best way to present flows (and which flows would be 
the most interesting).
And we have to integrate this in the discussions handled by the group 
dedicated to PSD2 (David, Paddy, Evert, Cyril).

     As a reminder, the new actors (definitions from PSD2):

/*    Payment Initiation Service Providers* :‘payment initiation 
service’ means a service to initiate a payment order at the request of 
the payment service user with         respect to a payment account held 
at another payment service provider;//
//*    Account Information Service Providers*: ‘account information 
service’ means an online service to provide consolidated information on 
one or more payment accounts held by the payment service user with 
either another payment service provider or with more than one payment 
service provider;//
//*    Account Servicing Payment Service Providers*: ‘account servicing 
payment service provider’ means a payment service provider providing and 
maintaining a             payment account for a payer;/

Le 02/02/2016 15:47, Ian Jacobs a écrit :
> Hi Frédéric,
> Here’s our “flow” home page:
>   https://github.com/w3c/webpayments/wiki/Flows
> The exercise should help us understand the impact of the Web Payment APIs on priority flows,
> and in looking at the “before the API” and “after the API” pictures, we are like to detect issues that
> we need to ensure we address in the API specification.
> Similarly, it seems through your question that there’s a way to use (different) flows to show the world “before
> PISPs” and “with PISPs”. I don’t know whether PISPs will have an impact on all the flows that are listed on the
> above wiki page. But in the cases where PISPs do play a role, I think it makes sense to do something like this:
>    * Take a “pre W3C API flow”  and modify it to include a PISP
>    * Add it to the list of flows (e.g., “3DS with PISP” though that may or may not be a real example).
>    * Create a “post W3C API flow” (e.g., 3DS with PISP and W3C API”).
> Then we can evaluate the result and see if we observe any critical issues that the W3C API needs to take into account.
> If you would like to contribute, I suggest contacting Nick Telford-Reed and Matt Saxon on the working group list: public-payments-wg@w3.org.
> Thanks!
> Ian
> --
> Ian Jacobs <ij@w3.org>      http://www.w3.org/People/Jacobs
> Tel:                       +1 718 260 9447
Received on Wednesday, 10 February 2016 23:33:11 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:08:49 UTC