Crypto vs Card Fees: Complete Merchant Cost Model (2026)

A crypto vs card fees comparison must follow the money. The processor's headline rate is only one line. Settlement, conversion, disputes, held funds, network costs, compliance, and internal operations can change the result.

Hold four inputs constant across both rails. Use the same order value, customer location, settlement destination, and accounting period. If one option ends in a bank currency and the other in a stablecoin, include every step needed to reach the asset the business uses. The crypto payment explainer maps that rail before the cost worksheet begins.

Why does the headline percentage give the wrong answer?

Headline rates describe different boundaries. A card quote may cover authorization and acquiring while leaving currency conversion, disputes, or payout conditions elsewhere in the agreement. A crypto quote may show a processing percentage while treating the customer's network fee, merchant withdrawal, or conversion as separate steps.

The comparison fails when those boundaries do not match. A 1% acceptance rate that forces a later conversion can cost more than a higher rate that settles directly in the required asset. A rail with no card chargebacks can still create wallet, reconciliation, and compliance work. A card integration can simplify bank settlement while adding cardholder-data controls.

Define the start and finish first. The customer pays a specific amount; the merchant receives a specific final asset at a specific destination. Then place every deduction and operating cost between those points.

Which card-payment costs belong in the model?

Card acceptance has several possible cost layers. They include acquiring and processor charges, cross-border or currency conversion, payout terms, disputes, and card-data security work. The exact schedule depends on the provider, country, card type, transaction channel, settlement currency, and merchant risk profile. Do not substitute an industry average for the merchant's signed agreement.

Disputes deserve their own line. Card networks maintain formal chargeback processes with reason codes, evidence requirements, and response windows. The cost is not limited to a dispute fee; it can include the transaction amount, staff time, fulfillment loss, and any funds held under the acquiring relationship.

PCI DSS follows cardholder data exposure. It applies to entities that store, process, transmit, or can affect that data's security. Scope depends on the merchant's complete card environment, not on one payment provider in isolation.

Which crypto-payment costs belong in the model?

Crypto acceptance also has distinct cost layers. They can include gateway processing, the payer's network fee, merchant withdrawal network cost, provider-imposed conversion, custody operations, and internal reconciliation. These components belong to different steps, so label who pays each one.

On a Paymos invoice, the payer's wallet pays the inbound blockchain fee. Paymos covers its own cost of accepting and consolidating the payment. The merchant balance remains in the accepted asset, and Paymos does not force conversion to fiat, BTC, or ETH.

At withdrawal, Paymos takes no processing commission. The selected asset-and-network route can include a disclosed, subsidized network fee. Network cost varies, so calculate it from the current route rather than publishing one permanent gas amount. The gas fee guide explains why live conditions matter.

How does settlement asset change total cost?

The final asset decides which conversions belong in the worksheet. A business that keeps treasury in USDT should compare the cost of reaching USDT. A card payment that settles to a bank account may need a later purchase and transfer of USDT. A crypto processor that forces stablecoin-to-fiat conversion can create the opposite round trip.

Paymos settles in the same asset received from the payer. A USDC payment contributes to the merchant's USDC balance; it is not automatically converted to another token or bank currency. Paymos does not provide a bank-account cash-out service.

Bank settlement requires a separate conversion path. Add its provider, rate, transfer charge, and timing. If the merchant keeps or pays suppliers in stablecoins, same-asset settlement can remove those steps entirely.

How should network fees be counted?

Assign every network cost to the actor and transaction that creates it. The payer's wallet pays to send the invoice payment. The processor may incur costs to accept or consolidate deposits. The merchant can pay a network fee when withdrawing to its own wallet. A later transfer from that wallet creates another independent network cost.

Do not call all of those costs “gas” in one row. Separate inbound payment, processor operations, merchant withdrawal, and any later treasury movement. This prevents double counting and makes provider pricing comparable.

Paymos includes its acceptance and consolidation cost in the processing model. It does not add a separate sweep commission to the merchant invoice. A withdrawal route may still display a subsidized network fee. That is a disclosed network cost, not another percentage charged on the settled invoice.

How do chargebacks and refunds change risk cost?

Card payments can enter a formal dispute process after the original authorization. Network rules determine evidence, deadlines, liability, and whether value is returned through the card system. Merchants therefore model both dispute frequency and the operational cost of responding.

Finalized blockchain transfers have no card-scheme reversal. A crypto refund is a new outbound transaction initiated by the merchant. This removes card-style chargeback exposure but does not remove customer complaints, fraud, fulfillment mistakes, or legal obligations.

Price the difference honestly. For cards, include chargeback losses and response work. For crypto, include confirmation controls, refund approval, destination verification, and outgoing network cost. The crypto payment chargeback guide maps those responsibilities in detail.

How does Paymos pricing fit the worksheet?

The Paymos product model keeps the processing boundary narrow. Standard pricing is 1.0% per settled invoice, and Enterprise pricing is 0.3% on request. An unpaid, expired, or canceled invoice has no Paymos processing fee. There is no setup fee, monthly platform fee, monthly minimum, reserve, or held-back balance.

Each project controls who covers the processing fee. At 0%, the merchant pays the complete fee. At 100%, the payer covers it and the merchant receives the original invoice amount. Values between those points split the fee.

Paymos does not force an internal conversion. It therefore adds no separate internal conversion fee. It also takes no processing commission on withdrawal, although the route can include its disclosed network fee and minimum.

How can you work a $100 example without inventing rates?

Set the order value to $100 and the target treasury asset to USDT. Under Paymos Standard pricing, the processing line is $1.00 because the confirmed rate is 1.0% per settled invoice. The payer's inbound network fee belongs in a separate payer-cost column. Paymos's acceptance and consolidation cost does not become another merchant fee.

Let W equal the disclosed withdrawal network fee for the selected route and L_crypto equal the merchant's measured reconciliation and treasury labor. The merchant-side crypto cost is $1.00 + W + L_crypto when the merchant covers the complete processing fee. If the project passes 100% of that fee to the payer, the merchant receives the original invoice amount before W and its own operating cost.

Do not fill the card column with a market average. Use the merchant's contracted acceptance charge C, conversion cost X, payout cost P, measured dispute loss D, and operating labor L_card. Its comparable total is C + X + P + D + L_card. Compare the two only after both paths reach the same treasury asset and destination.

What worksheet produces a fair comparison?

Build one row per cost event and one column per rail:

1. Record the customer's order amount and payment asset.
2. Add acceptance and acquiring or gateway charges.
3. Add the payer, provider, and merchant rail costs separately.
4. Add every conversion required to reach the final treasury asset.
5. Add payout or withdrawal costs and timing.
6. Add dispute losses, held funds, and response labor.
7. Add security, compliance, reconciliation, and treasury operations.
8. Compare the final amount and risk at the same destination.

Use observed provider quotes instead of marketing summaries. Date every variable network or conversion value. The result should explain not only which rail costs less, but why.

The crypto payment gateway comparison framework turns this worksheet into a reusable provider shortlist.