Pending Payment
Pronunciation: PEHN-ding PAY-munt
Definition
A pending payment is a payment that has been created or observed but has not reached a terminal business outcome. It may be waiting for customer action, authorization, confirmation, provider response, review, settlement, or reconciliation and should expose the specific dependency. Pending Payment requires named ownership and auditable controls for payment authorization, execution, fulfillment, and financial posting. Pending Payment records must retain authoritative identifiers, timestamps, state changes, exceptions, owners, and the final operational and accounting outcome.
Overview
A pending payment is a payment that has been created or observed but has not reached a terminal business outcome. It may be waiting for customer action, authorization, confirmation, provider response, review, settlement, or reconciliation and should expose the specific dependency.
The source-of-truth record should preserve current state, event source, event time, allowed transition, terminal flag, and financial effect for Pending Payment, including the handoff to Payout Pending . 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.
Pending Payment should remain distinct from reconciliation and Payout Pending, because each can represent a different stage, record, control, or financial outcome.
For Pending Payment, the state must have an authoritative source, timestamp, allowed transitions, financial effect, terminality, and rules for late or duplicate events. For Pending Payment, the most consequential risks are ambiguous states, stale events, wrong payment matching, premature fulfillment, confirmation assumptions, late success after expiry, unsupported manual transitions, contradictory evidence, and customer messages that overstate finality.
Controls should validate inputs server-side, authenticate external events, make irreversible actions idempotent, and reconcile provider, network, settlement, and ledger evidence. For Pending Payment, the authoritative record and completion rule should be documented before any irreversible operational, customer, or accounting action is released. Teams using Pending Payment should preserve the evidence behind each decision so retries, corrections, support reviews, and audits can reproduce the final outcome.
Key Takeaway
A pending payment is a payment that has been created or observed but has not reached a terminal business outcome. Its authoritative records, controls, exceptions, and final financial effect must be explicit.
Sources
- A Glossary of Terms Used in Payments and Settlement Systems — Bank for International Settlements (2026-08-01)
- CloudEvents Specification — Cloud Native Computing Foundation (2026-08-01)