{{ summaryTitle }}
{{ summaryPrimary }}
{{ summarySubtitle }}
{{ selectedPreset.label }} {{ effectiveRateDisplay }} effective {{ selectedAddOnProfile.label }} {{ summaryFeeBadge }} {{ countDisplay }} {{ warnings.length }} notes
Review fee inputs {{ selectedPreset.label }}
Charge Fee Net
Payment processor fee inputs
Processor rates vary by country, plan, card type, payment method, and negotiated pricing. Use the presets as editable starting points and verify against your account.
Use gross-up mode when preparing an invoice amount that should land as a clean target net.
Choose a processor baseline, then adjust the rate, fixed fee, or add-ons below.
{{ amountHelp }}
{{ currency_symbol }}
Use 1 for a single invoice, or enter the count of equal payments to see total fees.
payments
Percentage charged on the payment amount before the fixed per-transaction fee.
%
Flat amount charged once per payment, in the display currency.
{{ currency_symbol }}
{{ addOnProfileHelp }}
{{ addOnPercentHelp }}
%
Default USD. Change only the display symbol after entering rates that match that currency.
Use 0 when the fixed-fee field already includes the whole flat charge.
{{ currency_symbol }}
Enter 0 for no minimum-fee rule.
{{ currency_symbol }}
Enter 0 for no cap, or the maximum fee deducted per payment.
{{ currency_symbol }}
Use 0 for pure per-transaction processor math.
{{ currency_symbol }}
Nearest cent matches most published examples; round up is conservative for fee pass-through estimates.
Use a short label such as Monthly SaaS plan or Client invoice.
Line item Amount Detail Copy
{{ row.label }} {{ row.value }} {{ row.detail }}
Processor Rate Fee Net Gross-up charge Copy
{{ row.processor }} {{ row.rate }} {{ row.fee }} {{ row.net }} {{ row.grossUp }}
Strategy Customer charge Net received Use when Copy
{{ row.strategy }} {{ row.charge }} {{ row.net }} {{ row.note }}
Assumption Setting Detail Copy
{{ row.topic }} {{ row.setting }} {{ row.detail }}
{{ jsonText }}
Customize
Advanced
:

Introduction:

Payment processing cost is usually quoted as a small percentage plus a small fixed charge, yet that simple-looking price can change the economics of a sale. A card fee of 2.9 percent plus 30 cents is not the same as a flat 3.2 percent on every order. The percentage follows the sale amount, while the fixed part is taken once per payment, so the real fee rate is much higher on small purchases than on large invoices.

Merchants, freelancers, marketplaces, and subscription businesses run into this math whenever they price products, prepare invoices, compare checkout providers, or decide whether a minimum order size makes sense. The amount that lands in the bank is only one part of the decision, but it is the part that affects margin immediately. A low headline percentage can still be expensive when a plan adds fixed transaction fees, cross-border uplifts, currency conversion, manual-entry pricing, platform fees, or monthly costs that need to be spread across a small number of payments.

Gross charge
The amount the customer pays before payment fees are deducted.
Processor fee
The modeled payment cost from the percentage rate, fixed charges, add-ons, minimums, caps, and rounding.
Net received
The gross charge minus the processor fee, before taxes, refunds, disputes, reserves, and other business costs.
Effective fee rate
The processor fee divided by the gross charge. This is the best single number for comparing the cost of different ticket sizes.
Customer charge split into net received and processor fee.

A useful fee estimate separates the parts that scale from the parts that do not. A 30 cent fixed fee on a 5 dollar sale is 6 percent before the percentage fee is even counted. On a 500 dollar invoice, the same 30 cents is nearly invisible. That is why payment method choice, ticket size, subscription billing, and minimum order policy often matter as much as the advertised percentage rate.

Gross-up pricing reverses the usual calculation. Instead of asking how much remains after fees, it asks what charge would leave a chosen net amount. That can help with quotes and invoice planning, but it does not decide whether passing a fee to a customer is allowed. Card-network rules, processor terms, customer disclosure duties, tax treatment, and local surcharge law can all limit what may be added to a bill.

Published fee schedules are best treated as starting points. The account statement, pricing page, or merchant agreement is the source of truth because country, card type, payment method, risk review, negotiated pricing, refunds, disputes, reserves, payout timing, and added services can all change the final cost.

How to Use This Tool:

Start with the fee question you need to answer, then enter the rate structure that matches the payment being modeled.

  1. Choose Net from customer charge when you know what the customer pays, or Gross-up to target net when you know the amount you want to receive after fees.
  2. Select a Processor preset to load a public-style baseline, then replace the rate, fixed fee, minimum, or cap with the values from your account when they differ.
  3. Enter the Customer charge or Target net amount, and set Transaction count when the same payment repeats across a batch, invoice run, or monthly estimate.
  4. Use Processor rate, Fixed fee, Add-on profile, and Add-on percent for international cards, manual entry, currency conversion, platform pricing, or other known uplifts.
  5. Open Advanced for an extra fixed fee, minimum fee, fee cap, allocated monthly cost, display currency, rounding rule, or scenario label.
  6. Read the summary and Fee Math rows first. Warning notes identify public-rate assumptions, stacked add-ons, monthly allocation, cap/minimum conflicts, or gross-up pass-through cautions.
  7. Use Compare, Gross-Up, Fee Chart, Assumptions, and JSON when you need provider comparisons, a gross-up plan, chart exports, or an auditable record of the settings.

Interpreting Results:

The main figure is either the net received after the modeled processor fee or the charge needed to reach a target net. The per-payment result is the cleanest way to understand the economics of one transaction, while the batch total multiplies the same payment across the transaction count.

Payment processor fee result interpretation
Output cue Meaning What to verify
Processor fee The modeled deduction per payment after percentage, fixed, add-on, minimum, cap, and rounding rules. Confirm the account rate and whether the payment method uses the same pricing schedule.
Effective fee rate The processor fee divided by the customer charge, including fixed costs and rule adjustments. Compare this number across realistic ticket sizes rather than judging by the percentage rate alone.
Minimum or cap adjustment A minimum can raise the fee on small payments, while a cap can limit the fee on larger bank-transfer style payments. Check which payment methods actually use a minimum, cap, or capped ACH-style rule.
Gross-Up The plan compares absorbing the fee, charging the exact gross-up amount, using the next .99 price, and multiplying the exact plan across the batch. Review customer disclosure, processor terms, and surcharge rules before billing a pass-through amount.
Compare Provider rows reuse the same amount, add-ons, monthly allocation, count, and rounding rule so preset differences are easier to see. Replace public baselines with account-specific rates before changing providers or quoting margin.

The lowest comparison row is not automatically the lowest real-world cost. Refund fees, chargebacks, risk holds, payout speed, subscription fees, tax products, fraud tools, card mix, and available payment methods can outweigh a small difference in the modeled transaction fee.

Technical Details:

Percentage-plus-fixed pricing is a two-part tariff. The percentage part rises with the gross charge, and the fixed part is charged once per payment. When a monthly platform or gateway cost is allocated across the transaction count, it behaves like another fixed per-payment cost for this estimate.

Minimums and caps are rule overlays on top of the base fee. A minimum protects the processor on small payments by lifting the fee to a floor. A cap does the opposite on large payments by limiting the maximum deduction. If both are entered and the cap is below the minimum, the cap ultimately wins because it is applied after the minimum check.

Formula Core

The base per-payment fee is calculated from the gross charge, combined percentage rate, and fixed costs:

Fraw = G ( r + a ) + c + x + M n

Here G is the gross customer charge, r is the processor percentage as a decimal, a is any add-on percentage as a decimal, c is the fixed processor fee, x is any extra fixed fee, M is the allocated monthly cost, and n is the transaction count. Net received is G - F, and the effective fee rate is F / G.

The rule-adjusted fee starts with the raw fee, then applies a minimum, a cap, the selected rounding rule, and a final limit that prevents the modeled fee from exceeding the gross charge:

F = round ( min ( G , cap ( max ( Fraw , minimum ) ) ) )
Payment fee rule order
Stage Rule Result effect
Percentage Multiply the gross charge by processor rate plus add-on percent. Captures card, international, manual-entry, conversion, or platform percentage costs.
Fixed costs Add the fixed fee, extra fixed fee, and monthly cost divided by transaction count. Raises the effective rate most on smaller payments.
Minimum If a minimum is active and the adjusted fee is lower, use the minimum. Models payment methods with a fee floor.
Cap If a cap is active and the adjusted fee is higher, use the cap. Models capped bank-transfer or ACH-style fee schedules.
Rounding Round the per-payment fee by nearest cent, up, down, or no rounding. Controls displayed fee, net received, and batch multiplication.

For a 100 dollar charge at 2.9 percent plus 30 cents, the raw fee is 100 x 0.029 + 0.30 = 3.20. Net received is 96.80 dollars, and the effective fee rate is 3.20 percent. For a 5 dollar charge at the same rate, the fee is 45 cents and the effective fee rate is 9 percent, which shows how the fixed fee dominates small-ticket payments.

Gross-up mode works from the target net instead of the customer charge. When there are no minimums, caps, or rounding complications, the simplified equation is gross = (target net + fixed costs) / (1 - percentage rate). With caps, minimums, allocation, and cent rounding, the safer method is to test possible gross charges until the resulting net reaches the target, then round the charge up to the next cent.

Provider comparisons are sensitivity checks, not live account quotes. They hold the current amount, add-on profile, fixed adders, monthly allocation, transaction count, and rounding rule constant while changing the preset processor rate, fixed fee, minimum, and cap. That makes the rows useful for rough comparison, but it does not model volume tiers, interchange-plus billing, refunds, disputes, payout fees, reserves, regional tax on fees, or product-specific eligibility unless those costs are manually entered.

Accuracy Notes:

This is a planning estimate, not financial, legal, tax, accounting, or payment-provider advice. No card details are needed, and the calculation does not sign in to a processor account or verify live account pricing.

  • Public processor rates can vary by country, plan, payment method, card type, risk review, business category, negotiated pricing, and settlement currency.
  • Gross-up amounts do not decide whether fee pass-through is legal, contractually allowed, properly disclosed, or taxable.
  • Refunds, disputes, chargebacks, reserves, instant payout fees, tax products, fraud services, and platform subscriptions can change total cost even when the transaction fee estimate is correct.
  • The currency symbol only changes display formatting. It does not convert currencies or change provider fee schedules.

Worked Examples:

A 100 dollar card payment at 2.9 percent plus 30 cents produces a 3.20 dollar modeled fee and 96.80 dollars net before other costs. The effective fee rate is 3.20 percent, which is higher than the stated 2.9 percent because the fixed 30 cents is included.

A 5 dollar payment at the same rate produces a 45 cent fee and 4.55 dollars net. The effective rate is 9 percent, so a seller with many low-ticket payments may care more about fixed fees, minimum order size, or batch billing than about a small percentage-rate difference.

A 100 dollar target net with the same 2.9 percent plus 30 cents structure needs a customer charge of about 103.30 dollars before other costs. The exact charge can change when add-ons, minimum fees, caps, monthly allocation, or conservative rounding are enabled.

For a 120 dollar payment repeated 25 times, a 3.78 dollar per-payment fee becomes 94.50 dollars in total fees. That batch view is useful for monthly subscription estimates, but the result still assumes every transaction uses the same amount, rate, add-ons, and payment method.

FAQ:

Why is the effective rate higher than the processor percentage?

The effective rate includes fixed fees, add-on fixed fees, monthly allocation, minimums, caps, and rounding. A fixed fee has a larger effect on small payments because it is charged once per transaction.

Can I use the gross-up amount on an invoice?

Use it as a math check first. Before passing fees through, confirm the processor contract, card-network rules, required disclosures, tax treatment, and local surcharge law.

Do processor presets match my account rate?

Not necessarily. Presets are editable public-style baselines. Use the rate, fixed fee, minimum, cap, and add-ons from your own pricing page, statement, or merchant agreement when accuracy matters.

Why can small payments look so expensive?

The fixed fee is charged once per payment. If the fixed fee is 30 cents, it is 6 percent of a 5 dollar sale before the percentage fee is counted, but only 0.06 percent of a 500 dollar invoice.

Why am I seeing a validation error?

The calculator needs a positive amount, at least one transaction, a valid calculation mode, and total percentage fees below 99.9 percent. Fix those inputs and the result will return.

Glossary:

Gross charge
The amount paid by the customer before payment processing fees are deducted.
Fixed fee
A flat amount charged once per payment, such as 30 cents or 49 cents in common card examples.
Minimum fee
A floor that raises the fee when the percentage-plus-fixed calculation is below the provider's minimum.
Fee cap
A ceiling that limits the maximum modeled fee for a payment method.
Net received
The gross charge minus the modeled processor fee, before taxes, refunds, reserves, disputes, or other business costs.
Effective fee rate
The processor fee divided by the gross charge, shown as a percentage.
Gross-up
A reverse calculation that raises the customer charge so the net received reaches a target amount.