<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">I don’t actually think there is any EBA / official mention of PSD3 - only some commitment to review PSD2. <div><br></div><div>I’m not sure there will be a PSD3 not that one is needed at all. What is clearly needed is a complete rewrite of RTS - so an RTS2 would be the right outcome. Imo this should be based on<div><div><br></div><div>1. Setting out clear use cases (eg ECommerce payments, POS payments) which are either mandated or optional/premium APIs</div><div><br></div><div>2. Removing all the ridiculous constraints around 90 day reauth, and indeed the whole construct that this is a proxy for screen scraping the limited access via web platforms. </div><div><br></div><div>3. Mandating SLAs which are needed to meet the above use cases. </div><div><br></div><div>4. Mandating a common standard (inc FAPI, web authn, etc</div><div><br></div><div>5. Manding conformance and certification to the standard(s)</div><div><br></div><div><div><br><div dir="ltr"><p style="margin: 0px; font-stretch: normal; line-height: normal;"><br></p><p style="margin: 0px; font-stretch: normal; line-height: normal;"><img src="blob:applewebdata://d6bb43fc-2279-407d-bd53-630ab359ad5e/d36557ae-b859-4b3d-b4dc-a2d752f142ef" data-unique-identifier=""></p><div dir="auto"><b style="background-color: rgba(255, 255, 255, 0);"><br class="gmail-m_8354166072974665155Apple-interchange-newline">Chris Michael</b></div><div dir="auto"><span style="background-color: rgba(255, 255, 255, 0);">Co-Founder and CEO<br>Ozone Financial Technology Ltd<br><a href="https://www.ozoneapi.com/" target="_blank">www.ozoneapi.com</a> <br><a href="tel:+44%207767%20372277" dir="ltr" x-apple-data-detectors="true" x-apple-data-detectors-type="telephone" x-apple-data-detectors-result="5/2" style="text-decoration-color: rgba(0, 0, 0, 0.258824);">+44 (0)7767 372277</a></span></div></div><div dir="ltr"><br><blockquote type="cite">On 8 Jul 2022, at 09:24, Anders Rundgren via Openid-specs-fapi <openid-specs-fapi@lists.openid.net> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><span>On 2022-07-08 10:07, Dave Tonge via Openid-specs-fapi wrote:</span><br><blockquote type="cite"><span>https://www.pymnts.com/bank-regulation/2022/eba-recommends-a-standard-api-for-open-banking-in-new-psd3/ <https://www.pymnts.com/bank-regulation/2022/eba-recommends-a-standard-api-for-open-banking-in-new-psd3/></span><br></blockquote><span></span><br><span>"would contribute to the development of the single EU retail payment market"</span><br><span></span><br><blockquote type="cite"><span>I imagine this would end up being based on the Berlin Group standards, but I suggest that we start the job of promoting the importance of rigorous technical conformance tests as the only way to ensure interoperability of a "common API" .</span><br></blockquote><span></span><br><span>I think it would be more useful making an effort combining Open Banking with the wallet concept since this what the Berlin Group tried, but probably failed with.</span><br><span></span><br><span>The wallet concept also powers P2P payments which is something Open Banking doesn't address at all. It doesn't have to but the importance of P2P (and thus the wallet) shouldn't be ignored.</span><br><span></span><br><span>I would also be interested to get some feedback on how you see SPC.</span><br><span></span><br><span>Cheers,</span><br><span>Anders</span><br><span></span><br><span></span><br><span>_______________________________________________</span><br><span>Openid-specs-fapi mailing list</span><br><span>Openid-specs-fapi@lists.openid.net</span><br><span>https://lists.openid.net/mailman/listinfo/openid-specs-fapi</span><br></div></blockquote></div></div></div></div></body></html>
<br>
<div><font face="Arial, Helvetica, sans-serif" size="2"><br></font></div><div><font face="Arial, Helvetica, sans-serif" size="2">The information in this email is confidential and solely for the use of the intended recipient(s). If you receive this email in error, please notify the sender and delete the email from your system immediately. In such circumstances, you must not make any use of the email or its contents.</font></div><div><font face="Arial, Helvetica, sans-serif" size="2"> </font></div><div><font face="Arial, Helvetica, sans-serif" size="2">Views expressed by an individual in this email do not necessarily reflect the views of Ozone.</font></div><div><font face="Arial, Helvetica, sans-serif" size="2"> </font></div><div><font face="Arial, Helvetica, sans-serif" size="2">Computer viruses may be transmitted by email. Ozone accepts no liability for any damage caused by any virus transmitted by this email. E-mail transmission cannot be guaranteed to be secure or error-free. It is possible that information may be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.</font></div><div><font face="Arial, Helvetica, sans-serif" size="2"> </font></div><div><font size="2"><font face="Arial, Helvetica, sans-serif">Ozone Financial Technology Limited t/a Ozone. Registered office: </font>86-90 Paul Street, London, EC2A 4NE<font face="Arial, Helvetica, sans-serif">. Registered in England and Wales. Registered number: 10969115.</font></font></div>