Payment Prompt

Overview

A payment prompt is a customer-facing message or interface request asking the payer to choose a method, provide information, authenticate, approve, or complete a payment action. It must clearly identify the merchant, obligation, amount, currency, timing, and safe next step.

For Payment Prompt, the interface or route should clearly present the merchant, obligation, amount, currency or asset, expiry, fees, destination, consent, security cues, status, and recovery options without acting as the authoritative settlement record. For Payment Prompt, material operational risks include phishing, altered amounts, credential leakage, inaccessible forms, confusing timers, unsupported devices, abandoned redirects, bot impersonation, customer error, and fulfillment based on browser state rather than server evidence. The operating record should preserve the original obligation, participants, amount, currency or asset, authoritative identifiers, timestamps, state history, exceptions, and final financial effect.

Payment Prompt should remain distinct from Payment URL and Payment Page, 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 Prompt, this point supports the definition’s focus on payment prompt is a customer-facing message or interface request asking the payer to choose a method, provide information.

Controls should validate inputs server-side, authenticate external events, make irreversible actions idempotent, and reconcile provider, network, settlement, and ledger evidence. For Payment Prompt, the authoritative record and completion rule should be documented before any irreversible operational, customer, or accounting action is released. Teams using Payment Prompt should preserve the evidence behind each decision so retries, corrections, support reviews, and audits can reproduce the final outcome. Changes affecting Payment Prompt should be versioned, tested under normal and degraded conditions, and reconciled after incidents or manual intervention.