Reference Profiles

These are non-normative reference patterns. They are not part of the OpenPISP protocol.

The OpenPISP protocol defines only three things: the psp:// URI format, the Inter-PISP Protocol, and the Scheme Authority Protocol. Everything below the PISP boundary — how a requester talks to its PISP, how a payer app talks to its PISP — is bilateral and out of protocol scope.

The reference implementation publishes two profiles for those boundaries. Use them as a starting point, adapt them, or replace them entirely. Nothing here is required for OpenPISP conformance.

Profile	Boundary	Document
Requester Platform Interface	Requester ↔ PISP	→
Payer App Interface	Payer app ↔ PISP	→

A PISP may implement additional profiles beyond these — for example, a web checkout profile, an invoice profile, or a kiosk profile. These would follow the same pattern: a defined API surface, a stated auth approach, and a set of workflows it depends on.