Proximity Payment

Overview

A proximity payment is initiated through short-range interaction between a payer’s device or credential and merchant acceptance equipment. It commonly uses contactless cards, mobile wallets, near-field communication, or QR-based presence flows and still depends on authorization, security, and settlement rules.

The operating record should preserve the original obligation, participants, amount, currency or asset, authoritative identifiers, timestamps, state history, exceptions, and final financial effect. For Proximity Payment, this point supports the definition’s focus on proximity payment is initiated through short-range interaction between a payer’s device or credential and merchant acceptance equipment.

Proximity Payment should remain distinct from 24/7 Payment and Pull Payment, 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 Proximity Payment, this point supports the definition’s focus on proximity payment is initiated through short-range interaction between a payer’s device or credential and merchant acceptance equipment.

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

Configuration or rule changes affecting Proximity Payment should be versioned, reviewed, tested in normal and degraded conditions, and deployable with a documented rollback procedure. Operational reporting for Proximity Payment should separate completed, pending, failed, retried, manually adjusted, and unresolved records so aggregate totals do not hide uncertain outcomes. A production review of Proximity Payment should compare external provider or network evidence with internal state and accounting records before the organization releases irreversible follow-on action.