Payment Lookup
Pronunciation: PAY-munt LOO-kuhp
Definition
Payment lookup is the controlled retrieval of a payment record using an accepted identifier or search key. It can return current status, amount, parties, route, events, provider references, and related records while enforcing authorization, privacy, rate limits, and consistent source-of-truth rules. Payment Lookup requires named ownership and auditable controls for payment authorization, execution, fulfillment, and financial posting. Payment Lookup records must retain authoritative identifiers, timestamps, state changes, exceptions, owners, and the final operational and accounting outcome.
Overview
Payment lookup is the controlled retrieval of a payment record using an accepted identifier or search key. It can return current status, amount, parties, route, events, provider references, and related records while enforcing authorization, privacy, rate limits, and consistent source-of-truth rules.
For Payment Lookup, the identifier’s issuer, namespace, object, uniqueness, lifetime, and mappings to provider, network, order, and ledger records must be explicit. Operational review should test exposed credentials, schema drift, broken callbacks, incorrect status mapping, provider lock-in, duplicate requests, timeouts after success, untested exports, stale applications, and interfaces that bypass core controls. The operating record should preserve the original obligation, participants, amount, currency or asset, authoritative identifiers, timestamps, state history, exceptions, and final financial effect.
Payment Lookup should remain distinct from Payout Transaction Hash and Payment ID, because each can represent a different stage, record, control, or financial outcome.
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. For Payment Lookup, this point supports the definition’s focus on controlled retrieval of a payment record using an accepted identifier or search key.
Controls should validate inputs server-side, authenticate external events, make irreversible actions idempotent, and reconcile provider, network, settlement, and ledger evidence. For Payment Lookup, the authoritative record and completion rule should be documented before any irreversible operational, customer, or accounting action is released. Teams using Payment Lookup should preserve the evidence behind each decision so retries, corrections, support reviews, and audits can reproduce the final outcome. Changes affecting Payment Lookup should be versioned, tested under normal and degraded conditions, and reconciled after incidents or manual intervention.
Key Takeaway
Payment lookup is the controlled retrieval of a payment record using an accepted identifier or search key. Its authoritative records, controls, exceptions, and final financial effect must be explicit.
Sources
- ISO 20022 Message Definitions — ISO 20022 (2026-08-01)
- OpenAPI Specification 3.2.0 — OpenAPI Initiative (2026-08-01)