Passing Card Fees to Customers (2026 Rules)

Where surcharging is restricted, the reliable approach is to build processor fees into your list prices using reverse math: charge (net + fixed) ÷ (1 − percent). For Stripe US 2.9% + $0.30 to net $100, charge about $103.30; for PayPal G&S 2.99%, about $103.08 (Checkout at 3.49% + $0.49 is about $104.14). Confirm local card-network and legal rules before adding a checkout surcharge.

Calculate with Stripe →Calculate with PayPal →

By Hammad Iqbal · Updated 2026-10-24

Fee-inclusive pricing vs surcharging

Passing fees can mean two different tactics. Fee-inclusive pricing raises the list price so that after Stripe or PayPal takes their cut, you still net your target. Surcharging adds a line item at checkout labeled as a card fee. Many regions and card networks restrict or regulate surcharging; fee-inclusive pricing is usually the simpler default.

This guide is educational, not legal advice. Before you enable any surcharge product feature, read your processor agreement and local rules. When in doubt, bake fees into prices and disclose total price clearly.

How to calculate fee-inclusive prices

Use the reverse formula from our how-to-price-after-fees guide: C = (N + f) ÷ (1 − p). Stripe US: p = 0.029, f = 0.30. PayPal US G&S: p = 0.0299, f = 0. PayPal Checkout: p = 0.0349, f = 0.49. Run /tools/stripe-fee-calculator/ and /tools/paypal-fee-calculator/ in “charge to receive” mode.

If you accept both rails at one list price, price for the more expensive rail you still allow—or publish rail-specific prices if your contracts and UX support that clarity. A single $100 list price nets ~$96.80 on Stripe vs ~$97.01 on PayPal G&S (or ~$96.02 on Checkout); the gap is your silent discount to PayPal users unless you adjust.

1. Set the net you need after fees.
2. Identify every accepted payment rail and its schedule.
3. Reverse-calculate per rail; pick publish price from the costliest allowed rail or separate SKUs.
4. Round up for marketing cleanliness.
5. Document the as-of date (schedules here use 2026-10-24 sources).

Worked example

You need $250 net. Stripe: C = (250 + 0.30) ÷ 0.971 ≈ $257.78 → publish $259 or $265. PayPal G&S: C = 250 ÷ 0.9701 ≈ $257.71; Checkout: C = (250 + 0.49) ÷ 0.9651 ≈ $259.55 → publish $265 if you want one price covering Checkout.

Surcharge-style illustration (only where allowed): list $250 + disclosed card fee. The fee line must match permitted calculation methods—some regimes cap surcharges or ban them on certain cards. Do not copy a percent from a blog; follow current network rules and processor docs.

Creator platforms complicate pass-through: Gumroad customers already see a product price that must absorb ~12.9% + $0.80 blended if that is your rail. You cannot “surcharge Gumroad” separately in a way that surprises buyers—set the public price correctly up front.

Fee comparison when choosing a rail to bake in

Baking in Stripe’s 2.9% + $0.30 yields lower customer prices for the same net than baking in PayPal G&S 2.99%. If PayPal conversion is essential, either accept lower net on PayPal orders or raise the global list price and let Stripe orders carry slightly more margin.

Compare with /tools/compare-payment-fees/. For POS contexts, Square in-person 2.6% + $0.15 may change the bake-in math versus online 2.9% + $0.30—see Square vs Stripe vs Shopify Payments.

When pass-through tactics win or fail

Fee-inclusive pricing wins when you sell in regulated surcharge environments, sell internationally across mixed rules, or want simpler UX. Explicit surcharging (where legal) can win when buyers frequently choose expensive rails and you want visible incentives to pick ACH or other cheaper methods your processor offers.

Pass-through fails when the disclosure surprises buyers at the last step and kills conversion. It also fails when your math uses the wrong schedule (domestic vs international, G&S vs F&F). Never instruct commercial clients to use PayPal Friends & Family to avoid fees—see PayPal G&S vs Friends & Family.

Practical tips

Put the total price in proposals, not “plus processing.” Update prices when processors change rates. Keep Stripe and PayPal source links on your internal rate card (as of 2026-10-24 snapshots in our data files).

Train support staff: if a customer asks to switch from card to a $0 P2P rail, explain risk and policy rather than silently accepting unprotected payments. Pair with hidden payment fees for instant-payout traps.

Messaging that does not sound like a gotcha

Customers accept fee-inclusive prices more readily than last-second surcharges. Present a single total in proposals and checkout. If you itemize for enterprise AP departments, label the line as “processing-inclusive service fee” only when your counsel agrees the wording matches local rules—and still ensure the math matches Stripe 2.9% + $0.30 or PayPal G&S 2.99% as applicable.

For subscriptions, revise prices on renewal notice windows rather than mid-cycle surprises when processor rates change. Keep a changelog of fee-driven price updates with source URLs and as-of dates so finance can audit.

Marketplace sellers sometimes face platform rules that forbid additional surcharges even when local law allows them. Platform policy can be stricter than card-network policy—read both. When blocked from surcharging, reverse-price the listing and move on.

If you operate in multiple countries, maintain country-specific price books. A bake-in that works for US Stripe list rates fails when EU pricing or cross-border add-ons apply. Pair with Wise vs PayPal for international when settlement currency differs from list currency.

1. Prefer one clear total price in customer-facing docs.
2. Log fee-driven price changes with official source links.
3. Check marketplace policies before enabling surcharge toggles.
4. Localize bake-in math per country schedule.

Additional planning notes

Re-verify official pricing before you publish customer-facing numbers for passing payment fees to customers. Our embedded schedules use an as-of date of 2026-10-15 and are planning aids, not contracts. When your processor negotiates custom pricing, substitute those percent and fixed values into the same forward and reverse formulas used throughout these guides.

Bookmark the related calculators linked from this article and re-run them whenever average order value shifts by more than about 20%. Fixed fees change effective rates sharply on small tickets, which is why $10 invoices and $500 invoices deserve separate reverse-price checks rather than linear scaling from a single $100 demo.

Finally, document the schedule name, source URL, and verification date next to every rate card or membership tier. Stale fee assumptions are one of the most common reasons freelancers and creators miss margin targets even when their headline math once looked correct.

Sources

• Stripe pricing (as of 2026-10-24)
• PayPal US business fees (as of 2026-10-24)

FAQ

Related calculators

Related guides