If you’re searching “Luis Requejo Miami,” you’re likely tired of the same story: you were promised one rate, then your statement arrived looking like a tax code written by someone who hates you.
Here’s the brutal truth: processing pricing is often designed to confuse. Confusion protects margin—for them, not you.
HighTech Payments’ own content leans into transparency and calls out industry middlemen and fee games as common problems.
So this article gives you the practical method: audit the statement, calculate your real cost, identify junk fees, and force a clean pricing structure.
Stop obsessing over the “rate.” Start tracking your effective rate.
Your quoted rate is marketing. Your effective rate is reality.
Effective Rate (simple formula)
Effective Rate = Total Fees ÷ Total Volume
You calculate it monthly, then compare it across 3–6 months.
Why it matters:
- It captures everything (markup, gateway, PCI, platform fees, “misc.” fees).
- It exposes when your costs quietly rise.
- It stops salespeople from hiding behind “starting at” numbers.
The 30-minute Merchant Statement Audit (do this every quarter)
Step 1: Pull the right documents
Get:
- 3 months of processing statements
- your signed proposal (or pricing email)
- any addendums or separate gateway contracts
If you can’t obtain these, that’s already a red flag.
Step 2: Compute your effective rate for each month
Write down for each month:
- total volume
- total fees
- number of transactions
- total chargebacks
- total refunds
You want trends, not a single snapshot.
Step 3: Sort fees into 4 buckets
- Network/interchange related costs (some are pass-through, some are padded)
- Processor markup (where they hide margin)
- Gateway/platform fees (often duplicated or inflated)
- Compliance/PCI/security fees (frequently weaponized)
Step 4: Highlight every fee you can’t explain in one sentence
Anything you can’t explain is either:
- unnecessary
- overpriced
- or intentionally opaque
Your goal is to eliminate or renegotiate those lines.
The most common hidden fee categories (and how they work)
1) Tiered pricing (the classic trap)
Tiered plans sound simple (“Qualified / Mid-qualified / Non-qualified”) but are often a margin machine.
How it hurts you:
- normal transactions get downgraded into expensive tiers
- you can’t predict cost
- you can’t compare providers cleanly
What you want instead: Interchange-plus (or a clearly disclosed flat-rate if you’re tiny and value simplicity).
2) “Downgrades” that punish bad data (and nobody tells you)
If your transaction data is missing or mismatched (address verification settings, business type data, invoice data, etc.), you can get moved into higher-cost categories.
How you fix it:
- verify correct business category and transaction type setup
- confirm AVS/CVV usage fits your model
- for B2B, explore whether Level 2/3 data applies (when relevant)
If the provider can’t explain why downgrades happen, you’re flying blind.
3) Gateway + “platform” fees stacked on top of each other
HighTech Payments describes online payments as a full stack including gateway, reporting, fraud tools, and APIs.
That’s fine—until you get charged separately for pieces that are supposedly included.
Watch for:
- gateway monthly fee
- per-transaction gateway fee
- “platform” monthly fee
- tokenization/storage fee
- API fee
- reporting fee
- “fraud tool” fees that magically appear after month 1
Rule: If you’re paying multiple monthly “system fees,” demand a single consolidated platform fee with a defined scope.
4) PCI fees (and “PCI non-compliance” penalties)
PCI compliance is real—but it’s also commonly used as a revenue lever.
HighTech’s PCI-focused content is blunt about one thing: compliance claims without proof are meaningless, and merchants should demand real evidence (like an AOC) rather than slogans.
What you should do:
- ask what PCI program you’re in (SAQ type, scope)
- ask what the provider supplies vs what you must do
- ask exactly what triggers “non-compliance” fees and how to remove them
- demand documentation—not “trust us”
If “PCI fees” keep recurring even after compliance steps are completed, push back hard.
5) “Regulatory”, “network”, or “assessment” fees used as camouflage
Some pass-through fees exist. That doesn’t mean every mysterious line item is legitimate.
Your job: force the provider to label what is pass-through vs markup.
If they won’t:
- assume they’re blending fees to hide margin
6) Refund, chargeback, and dispute costs you didn’t plan for
Some fees are legitimate, but they often get ignored until they explode:
- chargeback fees per dispute
- retrieval request fees
- representment fees
- excessive chargeback program fees (network-triggered)
HighTech’s high-risk guidance emphasizes that chargebacks and risk controls are central for stability.
So treat dispute cost as a core KPI.
The “Junk Fee Challenge” script (use this on a call)
Here’s the exact language to use:
- “Walk me through every monthly fee and what it covers.”
- “Which of these fees are pass-through and which are markup?”
- “Show me where each fee is referenced in the contract.”
- “If this fee is for a service, show me usage reports or outcomes.”
- “If you can’t justify it, remove it.”
If they can’t explain a fee, it’s either not real value or it’s deliberately hidden.
How to renegotiate without getting played
Step 1: Ask for a clean pricing proposal
Demand:
- a single pricing model (interchange-plus, or explicitly disclosed flat rate)
- a complete fee schedule (monthly + per-transaction + incident-based)
- reserve/hold policy summary (if applicable)
Step 2: Use your numbers, not their promises
Bring:
- effective rate trends
- chargeback rate trends
- refund rate trends
- average ticket size
- monthly volume range
This forces them into reality.
Step 3: Force alignment with your business model
Subscription? High ticket? Cross-border? High-risk?
Your fees should reflect your actual risk and support needs—not some default template.
Quick checklist: What a “clean” statement should look like
A clean statement has:
- one clearly described pricing method
- minimal monthly fees with clear scope
- no vague “misc.” lines
- reconciliation that matches deposits to transactions
- predictable dispute fee structure
If your statement fails this test, you don’t have “processing.” You have financial fog.
