A customer emails asking for their money back. No dispute, no bank involved, no drama — you just process the refund and move on. It feels like the clean, cheap way out compared to the alternative. It isn’t free, though, and the fee attached to it tells you something about how payment processors actually price risk.
Three Different Moments, Three Different Price Tags
A payment can fail to complete in three distinct ways, and each one has its own line item on a high-risk merchant account’s fee schedule:
A decline happens before money moves at all — the card gets rejected at the point of sale, for any number of reasons (insufficient funds, a risk flag, a typo in the card number). Nothing was ever charged, but processing the attempt still costs the processor something, so it carries a small fixed fee: €0,50 / $0,60 / 40₸ / ₴250 / ₹15 per declined attempt, currency depending on the account.
A refund happens after money has already moved successfully — the customer paid, the transaction settled, and now the merchant is voluntarily reversing it. This is the scenario in this article, and it costs €3,00 / $3,40 / 240₸ / ₴1400 / ₹90 per refund.
A chargeback happens when the customer skips the merchant entirely and disputes the charge with their card issuer instead. The bank pulls the money back, often before the merchant even knows there’s a problem, and the fee reflects the extra work involved: €100 / $120 / 7500₸ / ₴50000 / ₹3000 per case — and that’s before counting any extra penalty for merchants whose chargeback volume crosses a monthly threshold.
Line them up and the pattern is obvious: the fee scales with how much control the merchant kept over the outcome. A decline costs almost nothing because nothing happened. A chargeback costs the most because the bank made the call, not the business. A refund sits in between — the merchant made the decision, but money still had to move twice (in, then back out), and that has a real processing cost.
Why a Refund Costs More Than a Decline
It’s tempting to think a refund and a decline should cost about the same — in both cases, the customer ends up with no charge on their account. The difference is that a decline never completes a transaction cycle, while a refund does it twice: the original charge processes fully, then a second operation reverses it. Two completed operations cost more to process than one failed attempt, and the fee reflects that directly rather than trying to average it out.
There’s also a practical reason processors price refunds this way: a refund still touches settlement, currency conversion (if applicable), and reconciliation on both sides of the transaction. A decline touches none of that — it just gets rejected and logged.
Why a Refund Still Costs Less Than a Chargeback
The gap between €3,00 for a refund and €100 for a chargeback isn’t arbitrary — it reflects who did the work and who took the risk. When a merchant issues a refund, the merchant controls the timeline, the amount, and the paperwork. There’s no dispute to investigate, no evidence to submit, no chance of losing an argument with a bank’s compliance team.
A chargeback flips all of that. The merchant usually finds out after the fact, has to gather evidence to contest it if they choose to, and risks losing the dispute even when the original transaction was entirely legitimate. On top of the flat fee, a high enough chargeback ratio triggers escalating penalties and can put the entire merchant account at risk — something a refund, however frequent, doesn’t do on its own.
That’s the real lesson buried in the fee schedule: processors are pricing in effort and risk, not just “money moved.” A refund the merchant chose to issue is administratively simple. A chargeback is a dispute the merchant didn’t get to avoid.
Doing the Math: When “Just Refund Them” Is the Cheaper Call
For a merchant weighing whether to proactively refund an unhappy customer or wait and see if it turns into a chargeback, the fee schedule makes the answer close to arithmetic. A refund costs a flat €3,00. A chargeback costs at minimum €100 — more than 30 times as much — and that’s assuming the merchant’s chargeback ratio hasn’t already crossed a penalty threshold that adds hundreds more per case.
There’s a version of this math that gets missed in the moment: a support team stalling on a refund request, hoping the customer gives up, is sometimes accidentally choosing the more expensive outcome. If the customer doesn’t give up and files a dispute instead, the €3,00 problem just became a €100+ problem, plus a small dent in the merchant’s chargeback ratio that didn’t need to exist.
None of this means refunds should be handed out automatically for every complaint — that has its own cost in lost revenue and, at scale, its own operational overhead. But when a refund is clearly warranted, delaying it rarely saves money. It just shifts the risk toward the more expensive category.
What This Means for High-Risk Merchants
High-risk accounts already carry higher baseline rates than standard merchant accounts, and that makes every line item on the fee schedule worth understanding on its own terms rather than lumping “returned money” into one mental bucket. Declines, refunds, and chargebacks aren’t three flavors of the same problem — they’re three different processes with three different costs, and only one of them (the refund) is something the merchant fully controls from start to finish.
Knowing the actual numbers — not just “refunds cost something” but the specific gap between €3,00 and €100+ — changes how a support policy gets written. A fast, proactive refund on a clearly legitimate complaint isn’t generosity. On the numbers, it’s usually the cheaper decision.
Polydirection provides merchant accounts and payment processing for high-risk industries, including crypto, gambling, and forex. See the full fee schedule →