(no title)
lapusta | 6 years ago
1) Regulation. What you heard as "PSD2" - is essentially a directive by European Commission and EBA demanding banks to open up access to accounts data and payment initiation. Neither it defines by what means this access should be provided, nor when it should be available - each European country Central Bank can decide on its own.
2) Technical Specification. Examples are OpenBanking UK specification or The Berlin Group - would be groups of banks or local regulators trying to define common standards. Think of interface definition that describes both APIs as well as journeys/workflows.
3) Compliance. In the EU some of the banks (mostly large ones) are now required to be PSD2 compliant, which means they would need to expose their APIs through the standards described above. In the US, where there is no such requirement - the only way to access the bank account is to emulate a browser.
4) Third-Party Providers or Aggregators (Plaid, Teller, Tink, SaltEdge, Bud...) - would essentially provide access to the accounts of multiple banks via APIs. If you look at Plaid in the US - their codebase is probably 50%+ screenscraping/user emulation scripts in order to retrieve your accounts from e.g. Bank of America. For the EU fin-techs its a bit better, but still depends per country (remember Berlin Group vs UK OpenBanking?).
Nursie|6 years ago
Why 'would be' just out of interest?
AFAICT Open Banking is an organisation that has been given a mandate by the UK government, through the competition and marketing authority, and is funded by the nine largest retail banks. In the UK it is the defacto standard, and compliance of the CMA 9 is mandatory.
While there is so far no consistent standard across the EU, at least within the UK this one is set and pretty much non-negotiable.
(Disclaimer - I have consulted with Open Banking and continue to do so, but of course I do not speak on their behalf)
-- edit --
I'm particularly interested in this -
> Third-Party Providers or Aggregators (Plaid, Teller, Tink, SaltEdge, Bud...) - would essentially provide access to the accounts of multiple banks via APIs.
As AFAICT this would be explicitly disallowed unless all the users of said APIs are themselves accredited. You can't just get accredited for PSD2/OB API use, then expose that information to non-accredited entities. If this is what Plaid are doing then I wouldn't expect their accreditation to last all that long.
lapusta|6 years ago
The scenario is typically the following. After the EU Commission approves the directive, each country has to transform it into the national law and define the authority/approach/timelines. In the case of the UK, it's indeed the way you've described.
> As AFAICT this would be explicitly disallowed unless all the users of said APIs are themselves accredited.
In UK Plaid would have to follow the OpenBanking regulation indeed and provide access according to the consent of the account owner. In the US they are just storing your password and using it according to their privacy policy.
mariushn|6 years ago
PSD2 deadline is set to September 2019: http://europa.eu/rapid/press-release_MEMO-17-4961_en.htm
wayzel|6 years ago
Not entirely correct. In the US, JPMorganChase, Intuit, and others have adopted the OFX standard (consortium-based, which provides #2) as a more secure, controlled API alternative to browser emulation.
lapusta|6 years ago