Technical writing on PSD2, SCA, consent management, payment rails, and the practical realities of building on top of European bank APIs — from the BankLyra engineering team.
SCA is the most complex part of any open banking integration. This guide covers exemption hierarchies, redirect vs decoupled flows, and how to handle the edge cases that documentation leaves out.
Post-Brexit, the UK and EU operate distinct open banking regimes. We document the concrete differences in consent flows, data schemas, error codes, and SCA requirements that affect cross-border integrations.
An analysis of how PSD2 bank APIs fail — degraded performance, partial outages, silent errors — and how to design systems that stay resilient when upstream banks misbehave.
Consent authorisation abandonment is the hidden conversion problem in open banking. We analyse the UX and API design decisions that determine whether users complete the bank connection flow.
When does it make sense to route a payment over PSD2 PIS instead of cards? We compare economics, settlement latency, failure rates, and integration complexity across UK Faster Payments, SEPA Instant, and card networks.
Every PSD2 bank returns subtly different transaction schemas. We document 11 real inconsistencies — date formats, amount signs, merchant identifiers — and the normalisation strategies that make them manageable.
Do you need to register as an AISP or PISP to build open banking features? A practical guide to FCA TPP authorisation, eIDAS QWAC certificates, and the cases where you can use an aggregator's licence instead.
