Payment-versus-Payment (PvP)

Overview

Payment-versus-Payment (PvP) is a settlement mechanism in which the final transfer of one currency occurs only if the corresponding final transfer of another currency also occurs. Its defining feature is conditional finality across currency legs, not simply processing two payments at similar times.

Payment-versus-Payment (PvP) is closely connected to Settlement System , Settlement Exposure , and Settlement Liquidity Requirement . Implementation should define the settlement asset, accounts or addresses, participant roles, instruction format, cutoff and value dates, funding method, liquidity controls, finality point, and reconciliation evidence. Governance should define approval thresholds, escalation duties, and the authoritative record for final settlement. The operating record should preserve the original obligation, participants, amount, currency or asset, authoritative identifiers, timestamps, state history, exceptions, and final financial effect. Important failure modes include duplicate or delayed events, wrong destinations or currencies, stale instructions, unavailable providers, unsupported retries, and customer-facing status that differs from authoritative records.

Payment-versus-Payment (PvP) should remain distinct from Settlement System, Settlement Exposure, and Settlement Liquidity Requirement, because each can represent a different stage, record, control, or financial outcome.

Instructions should be validated and deduplicated before release, while balances and positions should be monitored through completion. Material risks include insufficient funding, wrong destination, counterparty default, settlement delay, instruction duplication, currency mismatch, failed validation, and ambiguity about finality. For Payment-versus-Payment (PvP), this point supports the definition’s focus on settlement mechanism in which the final transfer of one currency occurs only if the corresponding final transfer of.

Controls should validate inputs server-side, authenticate external events, make irreversible actions idempotent, and reconcile provider, network, settlement, and ledger evidence. For Payment-versus-Payment (PvP), the authoritative record and completion rule should be documented before any irreversible operational, customer, or accounting action is released.