Settlement Service (PSP-hosted) — Backend Specification

OpenAPI 3.0.3. This is the API a pilot-psp must implement/host itself — the counterpart to spec-settlementdesp (DESP calls into these endpoints on the PSP’s backend). This is the single most directly “buildable” spec in the set for a distributing PSP’s core settlement integration.

Endpoints

MethodPathoperationIdPurpose
POST/v1/fundingsfundingsRequestFunding from a commercial money account (managed by the receiving PSP) to a digital euro account (managed by the requesting PSP, via DESP)
POST/v1/defundingsdefundingsRequestDefunding to a commercial money account
POST/v1/payment-instructionspaymentReceive a payment instruction hosted by the Payee PSP
POST/v1/paymentspaymentsReceive a payment request hosted by the PSP
POST/v1/refundsrefundsReceive a refund request hosted by the Payer PSP
GET/callback/v1/fundings/{funding-id}/statusfundingsStatusStatus message for a funding request
GET/callback/v1/defundings/{defunding-id}/statusdefundingsStatusStatus message for a defunding request
GET/callback/v1/payment-instructions/{payment-instruction-id}/statuspaymentinstructionStatusStatus message for a payment instruction
GET/callback/v1/payments/{payment-id}/statuspaymentsStatusUpdateStatus message for a payment
GET/v1/payments/{payment-id}/status-inquiriespaymentsStatusInquiryQuery payment status
GET/callback/v1/refunds/{refund-id}/statuspaymentRefundStatusStatus message for a refund

Implementation note

Since this is PSP-hosted, building it means exposing these routes on the PSP’s own backend infrastructure (see offline-payments and eurosystem for the PSP-built-vs-Eurosystem-provided split) and wiring them to internal ledger/account logic per the sLM-* step tables in src-end-to-end-process-flows.

spec-settlementdesp · pilot-psp · funding-and-defunding · online-and-offline-payments