OpenPISPDeveloper Guide

Everything you need to build a Payment Initiation Service Provider on the OpenPISP network.

🔗

psp:// URI

The wire-level contract. A requester PISP generates a URI; any conforming payer PISP can resolve and act on it.

↔️

PISP ↔ PISP coordination — URI resolution, payment progression, and Stage 1/2 dispute handling.

🏛️

PISP ↔ SA coordination — governance, fee plans, settlement reporting, and Stage 3 escalation.

🔌

A plugin interface for bank connectivity. The reference implementation ships OBIE, TrueLayer, and internal adapters.

📋

Non-normative patterns for the requester and payer-app boundaries. Use them as a starting point, not a constraint.

🔐

mTLS on inter-PISP transport, JWS message signing, CRL revocation, and a documented threat model.