<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif;color:#0b5394">here's another example using a different variation of the above, but still enabled by CIBA</div><div class="gmail_default" style="font-family:tahoma,sans-serif;color:#0b5394"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;color:#0b5394"><a href="https://www.youtube.com/watch?v=6Z3YJd2r0qE">https://www.youtube.com/watch?v=6Z3YJd2r0qE</a><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, 30 Oct 2019 at 16:35, Chris Michael via Openid-specs-fapi <<a href="mailto:openid-specs-fapi@lists.openid.net">openid-specs-fapi@lists.openid.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Anders<br>
<br>
The OBIE example below is where all non-essential steps are removed from a redirect authentication. This solves some use cases but, as you state, is notb as good as Apple Pay, especially in a Point of Sale scenario. It would however work for an app-app (e.g. online purchase via a mobile app) scenario.<br>
<br>
As I am sure you are away, the CIBA standard we developed with/by FAPI WG members does allow much better UX which gets closer to Apple Pay. This is also included in the OBIE standard. However, no ASPSPs are implementing this yet, as it has not been specifically required by any regulators at this time.<br>
<br>
Here is a working demo of one of the 4 x supported CIBA flows<br>
<a href="https://www.youtube.com/watch?v=SXiRhCAYRCE" rel="noreferrer" target="_blank">https://www.youtube.com/watch?v=SXiRhCAYRCE</a><br>
<br>
I like your concept below, however creating additional TPP roles may take some time for the industry to get to grips with<br>
<br>
<br>
<br>
Chris Michael<br>
Head of Technology<br>
<br>
+44 7767 372277<br>
<a href="http://www.openbanking.org.uk" rel="noreferrer" target="_blank">http://www.openbanking.org.uk</a><br>
2 Thomas More Square, London E1W 1YN<br>
Twitter | Facebook | LinkedIn<br>
<br>
________________________________________<br>
From: Openid-specs-fapi <<a href="mailto:openid-specs-fapi-bounces@lists.openid.net" target="_blank">openid-specs-fapi-bounces@lists.openid.net</a>> on behalf of Anders Rundgren via Openid-specs-fapi <<a href="mailto:openid-specs-fapi@lists.openid.net" target="_blank">openid-specs-fapi@lists.openid.net</a>><br>
Sent: 30 October 2019 15:49<br>
To: Financial API Working Group List<br>
Cc: Anders Rundgren<br>
Subject: External : [Openid-specs-fapi] Open Banking NG<br>
<br>
Hi FAPIers,<br>
<br>
This picture from OBIE shows a payment scenario that is very far from Apple Pay:<br>
<a href="https://standards.openbanking.org.uk/wp-content/uploads/2019/06/4.1.1-Wireframe.png" rel="noreferrer" target="_blank">https://standards.openbanking.org.uk/wp-content/uploads/2019/06/4.1.1-Wireframe.png</a><br>
Yeah, using various kinds of "workarounds and fixes" it can surely be improved, but will that really scale?<br>
<br>
I have updated the "Dual-mode" Open Banking API proposal which if implemented should make Open Banking payments entirely "on par" with Apple Pay but with the added advantage that it builds on A2A (Account-to-Account) transactions which also is compliant with P2P (Person-to-Person) payments:<br>
<a href="https://cyberphone.github.io/doc/payments/dual-mode-openbanking-api.pdf" rel="noreferrer" target="_blank">https://cyberphone.github.io/doc/payments/dual-mode-openbanking-api.pdf</a><br>
<br>
To make the proposal more acceptable I have introduced an (optional) TTP role which (unlike PIS) is already known by payment professionals; the Payment Gateway.<br>
<br>
WDYT?<br>
<br>
Thanx,<br>
Anders<br>
<br>
On 2019-10-22 07:16, Anders Rundgren wrote:<br>
> A months has passed and it begins looking quite promising:<br>
><br>
> <a href="https://www.linkedin.com/posts/andersrundgren_open-banking-api-saturn-my-subversive-activity-6591608038912729088-31sr" rel="noreferrer" target="_blank">https://www.linkedin.com/posts/andersrundgren_open-banking-api-saturn-my-subversive-activity-6591608038912729088-31sr</a><br>
> Updated: <a href="https://cyberphone.github.io/doc/saturn/openbanking-api-for-saturn.pdf" rel="noreferrer" target="_blank">https://cyberphone.github.io/doc/saturn/openbanking-api-for-saturn.pdf</a><br>
><br>
> Anders<br>
><br>
> On 2019-09-21 10:26, Anders Rundgren wrote:<br>
>> This is probably not a use case people subscribed to this mailing list is particularly interested in.<br>
>> However, there are a couple of reason why this is a relevant issue:<br>
>> - If the bank can use the API themselves it will likely be better maintained<br>
>> - If the consumer payment market rather prefers schemes like Swish, TWINT, MobilePay <a href="https://empsa.org/" rel="noreferrer" target="_blank">https://empsa.org/</a> , <<a href="https://empsa.org/" rel="noreferrer" target="_blank">https://empsa.org/</a>> FAPI and similar Open Banking APIs could fall in importance<br>
>><br>
>> FWIW, I have just started (yesterday...) to investigate how Open Banking APIs could work in a local scenario:<br>
>> <a href="https://github.com/cyberphone/swedbank-psd2-saturn" rel="noreferrer" target="_blank">https://github.com/cyberphone/swedbank-psd2-saturn</a><br>
>> Swedbank uses the Berlin Group API but I guess the differences (on a higher level) compared to FAPI are not that big.<br>
>><br>
>> Anyway, since I'm not versed in OAuth2, I wonder if anybody out there have any ideas how to "patch" OAuth2 in such a way that an Open Banking API implementation could work in both local and remote mode without moving [too] many parts? Local mode = trusted service not needing user consent.<br>
>><br>
>> Cheers,<br>
>> Anders<br>
>><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" rel="noreferrer" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-fapi</a><br>
<br>
Please consider the environment before printing this email.<br>
<br>
This email is from Open Banking Limited, Company Number 10440081. Our registered and postal address is 2 Thomas More Square, London, E1W 1YN. Any views or opinions are solely those of the author and do not necessarily represent those of Open Banking Limited. <br>
<br>
This email and any attachments are confidential and are intended for the above named only. They may also be legally privileged or covered by other legal rights and rules. Unauthorised dissemination or copying of this email and any attachments, and any use or disclosure of them, is strictly prohibited and may be illegal. If you have received them in error, please delete them and all copies from your system and notify the sender immediately by return email. You can also view our privacy policy (<a href="https://www.openbanking.org.uk/privacy-policy" rel="noreferrer" target="_blank">https://www.openbanking.org.uk/privacy-policy</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" rel="noreferrer" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-fapi</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div style="padding:0px;margin:0px"> <table style="border-collapse:collapse;padding:0px;margin:0px"> <tbody><tr> <td style="width:113px"> <a href="https://www.pingidentity.com" target="_blank"></a><a href="https://www.pingidentity.com" target="_blank"><img alt="Ping Identity" src="https://www.pingidentity.com/content/dam/pic/images/misc/signature/ping-logo.png"></a> </td> <td> <table> <tbody><tr> <td style="vertical-align:top"> <span style="color:rgb(230,29,60);display:inline-block;margin-bottom:3px;font-family:arial,helvetica,sans-serif;font-weight:bold;font-size:14px">Rob Otto</span> <br> <span style="color:rgb(0,0,0);display:inline-block;margin-bottom:2px;font-family:arial,helvetica,sans-serif;font-weight:normal;font-size:14px">EMEA Field CTO/Solutions Architect</span> <br> <span style="font-family:arial,helvetica,sans-serif;font-size:14px;display:inline-block;margin-bottom:3px"><a href="mailto:robertotto@pingidentity.com" target="_blank">robertotto@pingidentity.com</a></span> <br> <span style="color:rgb(0,0,0);display:inline-block;margin-bottom:2px;font-family:arial,helvetica,sans-serif;font-weight:normal;font-size:14px"> </span> <br> <span style="color:rgb(0,0,0);display:inline-block;margin-bottom:2px;font-family:arial,helvetica,sans-serif;font-weight:normal;font-size:14px"> c: +44 (0) 777 135 6092</span> </td> </tr> </tbody></table> </td> </tr> <tr> <td colspan="2"> <table style="border-collapse:collapse;border:none;margin:8px 0px 0px;width:100%"> <tbody><tr style="height:40px;border-top:1px solid rgb(211,211,211);border-bottom:1px solid rgb(211,211,211)"> <td style="font-family:arial,helvetica,sans-serif;font-size:14px;font-weight:bold;color:rgb(64,71,75)">Connect with us: </td> <td style="padding:4px 0px 0px 20px"> <a href="https://www.glassdoor.com/Overview/Working-at-Ping-Identity-EI_IE380907.11,24.htm" style="text-decoration:none;margin-right:16px" title="Ping on Glassdoor" target="_blank"><img src="https://www.pingidentity.com/content/dam/pic/images/misc/signature/social-glassdoor.png" style="border: none; margin: 0px;" alt="Glassdoor logo"></a> <a href="https://www.linkedin.com/company/21870" style="text-decoration:none;margin-right:16px" title="Ping on LinkedIn" target="_blank"><img src="https://www.pingidentity.com/content/dam/pic/images/misc/signature/social-linkedin.png" style="border: none; margin: 0px;" alt="LinkedIn logo"></a> <a href="https://twitter.com/pingidentity" style="text-decoration:none;margin-right:16px" title="Ping on Twitter" target="_blank"><img src="https://www.pingidentity.com/content/dam/pic/images/misc/signature/social-twitter.png" style="border: none; margin: 0px;" alt="twitter logo"></a> <a href="https://www.facebook.com/pingidentitypage" style="text-decoration:none;margin-right:16px" title="Ping on Facebook" target="_blank"><img src="https://www.pingidentity.com/content/dam/pic/images/misc/signature/social-facebook.png" style="border: none; margin: 0px;" alt="facebook logo"></a> <a href="https://www.youtube.com/user/PingIdentityTV" style="text-decoration:none;margin-right:16px" title="Ping on Youtube" target="_blank"><img src="https://www.pingidentity.com/content/dam/pic/images/misc/signature/social-youtube.png" style="border: none; margin: 0px 0px 3px;" alt="youtube logo"></a> <a href="https://plus.google.com/u/0/114266977739397708540" style="text-decoration:none;margin-right:16px" title="Ping on Google+" target="_blank"><img src="https://www.pingidentity.com/content/dam/pic/images/misc/signature/social-googleplus.png" style="border: none; margin: 0px;" alt="Google+ logo"></a> <a href="https://www.pingidentity.com/en/blog.html" style="text-decoration:none;margin-right:16px" title="Ping Blog" target="_blank"><img src="https://www.pingidentity.com/content/dam/pic/images/misc/signature/social-blog.png" style="border: none; margin: 0px;" alt="Blog logo"></a> </td> </tr> </tbody></table> </td> </tr> </tbody></table><a href="https://www.google.com/url?q=https://www.pingidentity.com/content/dam/ping-6-2-assets/Assets/faqs/en/consumer-attitudes-post-breach-era-3375.pdf?id%3Db6322a80-f285-11e3-ac10-0800200c9a66&source=gmail&ust=1541693608526000&usg=AFQjCNGBl5cPHCUAVKGZ_NnpuFj5PHGSUQ" target="_blank"></a><a href="https://www.pingidentity.com/en/events/d/identify-2019.html" target="_blank"><img src="https://www.pingidentity.com/content/dam/ping-6-2-assets/images/misc/emailSignature/identify-email-image.png"></a> </div></div>
<br>
<i style="margin:0px;padding:0px;border:0px;outline:0px;vertical-align:baseline;background:rgb(255,255,255);font-family:proxima-nova-zendesk,system-ui,-apple-system,system-ui,"Segoe UI",Roboto,Oxygen-Sans,Ubuntu,Cantarell,"Helvetica Neue",Arial,sans-serif;color:rgb(85,85,85)"><span style="margin:0px;padding:0px;border:0px;outline:0px;vertical-align:baseline;background:transparent;font-family:proxima-nova-zendesk,system-ui,-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,Oxygen-Sans,Ubuntu,Cantarell,"Helvetica Neue",Arial,sans-serif;font-weight:600"><font size="2">CONFIDENTIALITY NOTICE: This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you have received this communication in error, please notify the sender immediately by e-mail and delete the message and any file attachments from your computer. Thank you.</font></span></i>