Payment Rails and Their Surcharges

Landed cost and dutyLast checked

Rail comparison dimensions

Payment rails are not interchangeable, though the differences that matter to a buyer are fewer than the list of options suggests. Five dimensions cover almost every real decision: the surcharge attached to the rail, the currencies the money passes through, how long funds remain tied up, what happens when an order fails, and any ceiling a rail places on a single transaction. Comparing rails before fixing the amount is comparing percentages of different numbers.

The surcharge is checked first and misleads most often. A percentage is read as though it were a fee, but it scales with the amount moved, which makes it a charge on order size rather than a price for using the rail. The rail with the lowest headline figure can still finish last once the conversion it carries is added, because a spread is charged inside the rate instead of appearing as a separate line that anybody would notice.

The remaining dimensions concern failure rather than cost. A rail with a formal reversal route behaves differently from one whose only remedy is a platform dispute. A rail that settles in a currency other than the account's adds a conversion step which may be charged twice, once on the way out and again if funds return. A rail with a per-transaction ceiling decides whether an order can be paid in one movement at all, which matters far more at the top of a budget ladder than at the bottom.

Surcharge table

Figures in this section are working parameters inside the landed-cost model, not quotations from any provider. Each carries a check date and a review tier, and each can be edited before an estimate is run. That framing is deliberate: published terms change, they differ by account and by region, and a rate copied without its date is worse than no rate at all. What the parameters are good for is holding one order still while two rails are compared against it.

Three rails sit in the model. Card payments are recorded as carrying no separate surcharge, with the cost appearing inside the conversion instead. Wallets show a markup of roughly two per cent, taken from 24 buyer reports read up to the check date, and transfers a wider one closer to three and a half, from 18 reports. A conversion step adds about two and a half more wherever money settles in one currency and is drawn from an account held in another.

Applied to a worked order, the ordering of the rails is stable while the size of the gap is not. On a hundred-and-fifty-dollar order the wallet markup works out at three, the transfer markup at a little over five, and a conversion step adds close to four whichever of the two is chosen. On a fifty-dollar order the spread dominates the surcharge and the whole difference shrinks to a dollar or two, which is the honest reason not to pick a rail on cost alone at the lower rungs of a budget.

Settlement delay column

Delay is the column most often left blank and the one that decides whether money can still be recovered. Authorisation and capture are separate events, and an order can still be cancelled inside that window without funds moving. Once captured, the amount sits with the platform until the order state changes, and the length of that period belongs to the order rather than to the rail. A rail returning funds in three days and one taking ten are describing the refund leg, not the hold.

The refund leg deserves to be timed in advance. Where a card reversal is available, money can come back without the platform's involvement; where a rail has no reversal route, the refund depends on the dispute process and on the seller agreeing to it. Comparing rails on surcharge alone optimises the cheapest line while ignoring the one that costs most when something goes wrong, and on a low-value order that is usually the entire amount.

A useful habit is to write the rail into the order note at the moment of payment, together with the amount and the date. When a refund runs late, that note answers the first question anybody asks, which is which route the money took. It also exposes a pattern across orders: a rail that is slow once is a coincidence, and a rail that is slow three times is a reason to change rails rather than to argue with a support queue.

Open the listing index

Chargeback leverage

Chargeback names a reversal initiated through the payment provider rather than through the platform, and its availability depends on the rail. Card payments generally carry a formal route with a stated window, a documented evidence list and a threshold below which the process is not worth opening. Wallet balances and bank transfers mostly carry no equivalent, so recovery runs through the platform's own dispute process, which is a different instrument with different timing and a different burden of proof.

Thresholds settle most of these cases before evidence does. Below a certain amount, the time spent assembling a reversal exceeds the sum at stake, and the sensible response in that range is to use the platform route or to write the loss off and record it. Above the threshold, the evidence list matters more than the argument: what was ordered, what arrived, what was asked of the seller and what the seller answered. None of that guarantees an outcome.

Filing a reversal also has consequences that outlast the order. Providers record disputes against the account, and a pattern of them can shape how later claims are treated regardless of their individual merits. Treat a reversal as a last resort with a written file behind it rather than as an opening move. Used that way it remains a genuine lever; used as a first response to a disappointing parcel, it spends a limited resource on a small dispute.

Two details shape how a reversal is read. The first is whether the file shows the seller was given a chance to put the problem right before the provider was drawn in, since a claim arriving with no prior message thread reads as a first contact rather than a last resort. The second is whether the amount claimed matches the amount paid, because a figure built from memory invites a query that costs another week. Neither detail changes the merits of the case; both change how much work it creates.

Rail recommendation rules

Four rules cover the decisions this desk sees most often. Match the rail to the amount, because a percentage surcharge is trivial on a small order and material on a large one while the reversal threshold moves in the opposite direction. Trace the refund route before paying rather than after. Remove any avoidable conversion by paying in whichever currency your account already holds, wherever the checkout allows that choice. Record the rail in the order note so a late refund can be traced without reconstruction.

Those rules produce different answers at different rungs of a budget. On a cheap accessory the cheapest rail with a traceable refund route wins, and the surcharge difference is smaller than a cup of coffee. On a large resale unit the reversal route and the transaction ceiling decide the choice, because a failed order at that size cannot be absorbed by a reserve sized for accessories. Scale changes which column matters, not which columns exist.

None of this replaces reading the terms attached to your own account, which may differ from the recorded bands in ways this desk cannot observe. The parameters are a comparison frame with a check date, not a promise about a checkout screen. Readers who want the arithmetic applied to one specific order can carry the same bands through the waterfall, and the two questions that follow from this section are handled in more detail on the payment release and reversal pages.

Payment rail surcharge bands carried in the cost model

Bands are editable parameters inside the landed-cost waterfall rather than quoted rates: editor analysis for the card and spread lines (sample size 0), buyer reports for the wallet band (sample size 24) and the transfer band (sample size 18), all read to 2026-09-21. Bands move, so re-read them in the tool and check the date shown there before relying on a comparison. No provider term is asserted here.

Payment rail surcharge bands carried in the cost model
ItemReading
RailRecorded band and where the cost appears
CardNo separate surcharge in this model; the cost sits in the conversion spread
WalletBand around two per cent of the amount moved, from 24 recorded reports
Bank transferBand around three and a half per cent, from 18 recorded reports
Any rail, other settlement currencySpread near two and a half per cent added on top of the rail band
Any rail, refund legTiming set by the reversal route or by the platform dispute process
Any rail, before captureAmount still cancellable; the hold begins once the payment is captured

Sources and checks

  • Editor analysis — Rail comparison dimensions and the card and spread parameters inside the landed-cost modelno sample
  • Public community thread — Recorded wallet surcharge reports used to set the wallet bandn=24
  • Public community thread — Recorded bank transfer surcharge reports used to set the transfer bandn=18

Last checked · next review due · status current.