PSD2 / Open Banking
Regulated integration with monitoring outside its failure domain
A security-first PSD2 bridge plus geographically distributed public monitoring.
This was not an isolated API build. It meant translating requirements between Salt Edge, internal banking systems and operational reality, then joining shared debugging calls when two systems disagreed about what “correct” meant.
The status page follows the same systems thinking: it runs on Cloudflare Workers because monitoring should not disappear with the infrastructure it monitors.
What I walked intoThe setup
Connect a third-party PSD2 provider to internal transaction systems while meeting security, revocation, audit and resilience requirements.
How I untangled itThe turning point
Scoped signed JWTs use Redis for rapid revocation; events persist to MongoDB for audit. Azure Service Bus connects processing. The public status page runs on Cloudflare Workers outside the monitored Azure failure domain.
What changedWhere it landed
Transactional, auditable Open Banking integration with multi-location visibility into service health.
View public artifact ↗