Pull Payment

Overview

A pull payment is initiated by the payee or its provider against the payer’s account or authorized payment method under a mandate or consent. Direct debits and merchant-initiated card charges are common examples, with revocation, return, dispute, and timing rules defined by the rail.

A commercial payment flow connects an obligation, payer experience, authorization, processing route, settlement, and accounting. The same use case can use cards, bank transfers , wallets, payment links, embedded components, or crypto. For Pull Payment, risk analysis should cover unclear payer intent, invalid obligations, thresholds that block legitimate users, misleading fees, duplicate collection, premature service delivery, expired terms, milestone disputes, and inconsistent refund treatment. The operating record should preserve the original obligation, participants, amount, currency or asset, authoritative identifiers, timestamps, state history, exceptions, and final financial effect.

Pull Payment should remain distinct from 24/7 Payment and Bank Transfer, 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 Pull Payment, this point supports the definition’s focus on pull payment is initiated by the payee or its provider against the payer’s account or authorized payment method.

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