Payment Slippage

Overview

Payment slippage is the difference between the expected economic outcome of a payment or conversion and the actual result at execution. It can arise from price movement, limited liquidity, spreads, routing, timing, fees, or amount changes between quotation and completion. For Payment Slippage, payment pricing can combine provider charges, card or bank fees, blockchain network costs, conversion spreads, fixed charges, percentage rates, minimums, and taxes.

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. For Payment Slippage, this point supports the definition’s focus on difference between the expected economic outcome of a payment or conversion and the actual result at execution.

Payment Slippage should remain distinct from Payment Failure, because the two records can carry different authority, timing, and financial effects. For Payment Slippage, a displayed fee may be estimated before execution and finalized afterward.

For Payment Slippage, the charge must identify who pays it, who receives it, its calculation base, timing, currency or asset, tax treatment, network relationship, rounding, minimum or maximum, and treatment after failure or refund. For Payment Slippage, the principal failure modes are hidden charges, wrong fee payer, stale estimates, volatile network costs, double charging, incorrect rounding, unreconciled rebates, unexpected taxes, refund disputes, and presenting a provider fee as a pass-through cost.

For Payment Slippage, controls should use versioned fee schedules, validated calculation bases, explicit payer settings, deterministic rounding, clear disclosure, and reconciliation to provider and network charges. Estimates should be labeled. Controls should validate inputs server-side, authenticate external events, make irreversible actions idempotent, and reconcile provider, network, settlement, and ledger evidence.