Fixed Fee

Overview

A processor might charge $0.30 per transaction, while a blockchain service can charge a fixed token amount in addition to variable network gas. Some fees are deducted from settlement and others are added to the payer total.

Fixed fees simplify forecasting but do not always reflect actual cost. Providers can revise them by asset, network, region, or account tier.

For crypto, a fixed provider fee should not be confused with the variable network fee selected by a wallet or validator market. Conversion also changes the base-currency value of a token-denominated fee.

Risks include double charging, hidden minimums, unexpected currency conversion, low-value transactions becoming uneconomic, and reconciliation that records only net settlement.

Systems should store fee type, amount, currency or asset, payer, basis, tax, gross payment, net settlement, effective date, and pricing plan.

Configuration for Fixed Fee should be evaluated at the time the payment request is created rather than reconstructed from current merchant settings. For Fixed Fee, asset support, network, amount precision, fee allocation, quote source, tolerance, callback behavior, settlement preference, and expiry can change later, so the effective values must remain attached to the historical payment.

Exception handling for Fixed Fee should define outcomes for unsupported assets, wrong networks, stale quotes, partial or excess amounts, provider timeouts, duplicate retries, and transactions observed after expiry. For Fixed Fee, staff actions should require appropriate permissions and produce a reason, timestamp, and linked accounting result instead of directly editing the final status.

For Fixed Fee, automated decisions should expose the inputs and rule version that produced the result. For Fixed Fee, dashboards and callbacks should present enough detail for reconciliation without leaking secrets or sensitive customer data, and a provider outage should leave the payment in a recoverable pending state rather than converting uncertainty into success or failure.

A fixed fee contributes differently to Cost of Payments at low and high transaction values and should be recorded in a Fee Ledger Entry .