Gateway Fee

Overview

A gateway may charge the merchant, add the fee to the payer total, or deduct it from settlement. Contract terms should define whether failed, expired, refunded, or manually accepted payments incur the fee.

In crypto payments, the fee can be calculated from the invoice amount, received amount, or converted settlement value. The basis and rate timestamp matter when assets are volatile.

A low advertised gateway rate can exclude other mandatory costs or apply only at certain volume tiers. Merchants should compare effective total cost rather than one component.

Risks include hidden fees, double charging through processor partners, reconciliation from net amounts only, changing tiers, and payer totals inconsistent with checkout.

Systems should record provider, pricing plan, fee type, rate or fixed value, basis, currency, payer, gross amount, refund treatment, and net settlement.

Configuration for Gateway Fee should be evaluated at the time the payment request is created rather than reconstructed from current merchant settings. For Gateway 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 Gateway 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 Gateway Fee, staff actions should require appropriate permissions and produce a reason, timestamp, and linked accounting result instead of directly editing the final status.

For Gateway Fee, automated decisions should expose the inputs and rule version that produced the result. For Gateway 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.

Gateway fees contribute to Cost of Payments and should be captured as a detailed Fee Ledger Entry before accounting aggregation.