Merchant Settlement Policy

Overview

A merchant settlement policy defines how and when a provider calculates, holds, converts, deducts, and releases merchant funds. It covers eligible transactions, fees, reserves, risk holds, minimums, currencies, schedules, destinations, exceptions, and reporting.

For Merchant Settlement Policy, the implementation must identify obligations, participants, settlement accounts, settlement asset, gross or net method, cutoffs, liquidity, value date, posting sequence, and exact point of internal or legal finality. The implementation should identify the obligation, participants, settlement asset, accounts or addresses, value date, liquidity source, posting sequence, and evidence of finality.

Merchant Settlement Policy should remain distinct from Merchant Settlement and Merchant Settlement Cycle, because each can represent a different stage, record, control, or financial outcome.

Teams should design for wrong positions, failed netting, insufficient liquidity, participant default, incorrect assets, premature finality claims, delayed delivery, duplicate postings, FX exposure, and unmatched settlement evidence. Important failure modes include insufficient liquidity, duplicate instructions, wrong settlement assets, delayed delivery, participant default, unmatched evidence, and premature claims of finality.

Controls should validate instructions, funding, destination, currency or asset, cutoffs, and participant positions before treating a settlement step as complete. For Merchant Settlement Policy, the authoritative record and completion rule should be documented before any irreversible operational, customer, or accounting action is released. Teams using Merchant Settlement Policy should preserve the evidence behind each decision so retries, corrections, support reviews, and audits can reproduce the final outcome. Changes affecting Merchant Settlement Policy should be versioned, tested under normal and degraded conditions, and reconciled after incidents or manual intervention.