<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<style type="text/css">.style1 {font-family: "Times New Roman";}</style></head><body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">I was at a round table a number of months ago in London on PSD2. Our industry, banks and regulators were in attendance. VocaLink presented CAPS as a solution there. It was
not well received for the reasons Dave states.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Dave, we should have a contact there via FDATA.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Brian<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Openid-specs-fapi [mailto:openid-specs-fapi-bounces@lists.openid.net]
<b>On Behalf Of </b>Dave Tonge via Openid-specs-fapi<br>
<b>Sent:</b> Thursday, October 13, 2016 2:30 AM<br>
<b>To:</b> Nat Sakimura <nat@sakimura.org>; Financial API Working Group List <openid-specs-fapi@lists.openid.net>; Henrik Biering <hb@peercraft.com><br>
<b>Subject:</b> Re: [Openid-specs-fapi] (Draft) FAPI WG Meeting Notes (2016-10-12)<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">I am aware of CAPS - it was started by Vocalink - who run the UK payments systems.<o:p></o:p></p>
<div>
<p class="MsoNormal">The first drafts of the proposal were (in my opinion) very bad - they wanted to centralise all identity management, so that the entity running the CAPS system would be the bridge between all customers, TPPs (third party providers) and banks
- rather then a federated model. At one of their presentations, it seemed as if they wanted to perform the authentication of customers on behalf of the banks.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The CAPS framework does solves some of the issues around liability that the banks are very concerned about, and as a result I think it is gaining some traction.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">My main contact at Vocalink has left, but I will ask him who is the best contact there for CAPS. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Vocalink were bought by Mastercard earlier this year, and notably their logo or name doesn't seem to be on the new website. I imagine this means that either they've failed to attract any of the UK banks to the system, or Mastercard are
changing the strategic direction for Vocalink.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I'm not aware of the other 2 initiatives. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Dave<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Thu, 13 Oct 2016 at 00:10 Nat Sakimura via Openid-specs-fapi <<a href="mailto:openid-specs-fapi@lists.openid.net">openid-specs-fapi@lists.openid.net</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<p class="MsoNormal">Thanks. <br>
I have contacts at Innopay but I do not to the ones quoted. <br>
<br>
Let's discuss them in the next call. <br>
We can discuss them over the mailing list as well. <br>
<br>
Nat Sakimura <br>
Chairman, OpenID Foundation<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
-----Original Message-----<br>
From: Henrik Biering via Openid-specs-fapi <<a href="mailto:openid-specs-fapi@lists.openid.net" target="_blank">openid-specs-fapi@lists.openid.net</a>><br>
To: <a href="mailto:openid-specs-fapi@lists.openid.net" target="_blank">openid-specs-fapi@lists.openid.net</a><br>
Sent: <span style="font-family:"Calibri",sans-serif">木</span>, 13 10<span style="font-family:"Calibri",sans-serif">月</span> 2016 5:28<br>
Subject: Re: [Openid-specs-fapi] (Draft) FAPI WG Meeting Notes (2016-10-12)<o:p></o:p></p>
</div>
<p class="MsoNormal">Today I came across a blog post by Innopay, that mentions some other
<br>
PSD2 related standards initiatives: <br>
<a href="https://innopay.com/blog/eba-rts-three-key-business-implications-for-bank-decision-makers" target="_blank">https://innopay.com/blog/eba-rts-three-key-business-implications-for-bank-decision-makers</a>/
<br>
<br>
The Berlin Group: <br>
<a href="http://www.berlin-group.org/psd2-acces-to-bank-accounts" target="_blank">http://www.berlin-group.org/psd2-acces-to-bank-accounts</a>
<br>
<br>
Preta S.A.S.: <br>
<a href="https://www.preta.eu/XS2A.html" target="_blank">https://www.preta.eu/XS2A.html</a>
<br>
<br>
CAPS: <br>
<a href="https://www.nets.eu/Media-and-press/news/Pages/PSD2-CAPS-framework-gaining-attention-in-Europe.aspx" target="_blank">https://www.nets.eu/Media-and-press/news/Pages/PSD2-CAPS-framework-gaining-attention-in-Europe.aspx</a>
<br>
<a href="https://www.caps-services.com/news#news-two" target="_blank">https://www.caps-services.com/news#news-two</a>
<br>
<br>
Does anyone have more knowledge about or contact to these initiatives? <br>
Maybe something to cover at the next meeting? <br>
<br>
/Henrik <br>
<br>
<br>
Den <a href="tel:12102016" target="_blank">12-10-2016</a> kl. 17:10 skrev Nat Sakimura via Openid-specs-fapi:
<br>
> Dear FAPI WG members: <br>
> <br>
> We had another very good WG call today. <br>
> <br>
> Here is the link to the Meeting Notes: <br>
> <br>
> <a href="https://bitbucket.org/openid/fapi/wiki/FAPI_Meeting_Notes_2016-10-12" target="_blank">
https://bitbucket.org/openid/fapi/wiki/FAPI_Meeting_Notes_2016-10-12</a> <br>
> <br>
> Please make a pull requests if there is any errors. <br>
> <br>
> Best, <br>
> <br>
> Nat Sakimura <br>
> _______________________________________________ <br>
> Openid-specs-fapi mailing list <br>
> <a href="mailto:Openid-specs-fapi@lists.openid.net" target="_blank">Openid-specs-fapi@lists.openid.net</a>
<br>
> <a href="http://lists.openid.net/mailman/listinfo/openid-specs-fapi" target="_blank">
http://lists.openid.net/mailman/listinfo/openid-specs-fapi</a> <br>
> <br>
<br>
_______________________________________________ <br>
Openid-specs-fapi mailing list <br>
<a href="mailto:Openid-specs-fapi@lists.openid.net" target="_blank">Openid-specs-fapi@lists.openid.net</a>
<br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-fapi" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-fapi</a>
<br>
_______________________________________________<br>
Openid-specs-fapi mailing list<br>
<a href="mailto:Openid-specs-fapi@lists.openid.net" target="_blank">Openid-specs-fapi@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-fapi" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-fapi</a><o:p></o:p></p>
</blockquote>
</div>
</div>
<br /><br /></body></html>