Spreads, Commissions, and Swaps: The Broker’s Decision Tree for Pricing Without Margin Erosion

A broker’s pricing model isn’t just “how we make money.” It’s a set of levers that shape execution quality, client trust, and how often your support team ends up in a swap dispute at 2 a.m.

The hard part is that liquidity markup, commission, and swap are tightly coupled: change one lever, and your profitability, competitiveness, and dispute surface area all move—sometimes in opposite directions. This article gives you a practical decision tree to choose (and govern) a pricing mix that fits your execution model, client base, and operational maturity.

1. Pricing Levers 101: Markup, Commission, and Swap (In Broker Terms)

Liquidity markup, commission, and swap are three different ways to monetize the same trading activity, but they “feel” different to clients and behave differently in your P&L.

Liquidity markup is the spread you add on top of your raw liquidity feed (or the spread you widen via execution configuration). In A-book/STP contexts, it’s often the cleanest revenue line because it’s earned at execution, per trade, and is easy to reconcile against LP statements.

Commission is a fixed fee charged per lot/per million (often per side or round turn). It’s common on ECN-style accounts where you advertise tight raw spreads and make revenue via explicit fees.

Swap (rollover/financing) is the overnight financing adjustment applied to open positions across rollover. Swap can be a meaningful revenue stream, but it is also a top driver of disputes because it’s multi-variable (rates, markups, triple-swap day, symbol settings, holidays, and platform conventions).

a) The key distinction: “visible fee” vs “embedded cost”

Markup is embedded in price. Commission is explicit. Swap is explicit but delayed and more complex.

That difference matters because:

• Embedded costs tend to reduce fee sensitivity but increase “execution fairness” scrutiny.
• Explicit fees increase transparency but can amplify price-shopping and comparison.
• Delayed fees (swap) increase misunderstanding and complaint probability.

b) Where each lever shows up operationally

Each lever lives in different systems and teams:

• Markup: bridge/aggregator settings, symbol configuration, platform groups, risk backoffice reporting.
• Commission: platform group settings, CRM fee schedules, IB rebates, accounting reconciliation.
• Swap: symbol specs, swap schedules, holiday calendars, disclosure pages, support macros, and audit logs.

2. Why This Decision Is Hard: Profitability vs Competitiveness vs Dispute Risk

Most brokers don’t fail because their pricing is “wrong.” They struggle because pricing wasn’t designed as a controlled system with guardrails, monitoring, and clear client communication.

There are three forces pulling you in different directions:

1. Profitability and predictability: You want revenue that scales with volume and is stable across market regimes.

2. Competitiveness: You want a headline offer that competes on spread/fees without destroying your net capture after LP costs, slippage, and rebates.

3. Dispute risk: You want fewer “why did you charge me swap?” tickets, fewer escalations, and fewer regulator-facing complaints.

a) The hidden cost: operational load and reputational drag

Even if swap revenue looks attractive on paper, a high dispute rate can erase it via:

• Support headcount and management time
• Payment disputes/chargebacks (especially around “unexpected fees” narratives)
• Negative reviews that raise your CPA and reduce conversion
• Increased compliance workload (disclosures, complaint logs, root-cause analysis)

b) The broker reality: your client mix changes over time

Early-stage brokers often attract price-sensitive, high-churn flow. As you mature, you may shift toward longer-horizon traders, IB-driven books, or multi-asset clients.

Your pricing model should be adaptable by account type, instrument, and client segment—not a single global setting that forces constant exceptions.

3. How the Money Actually Flows (Step-by-Step) in A-Book, B-Book, and Hybrid

Before choosing a pricing lever, you need a mental model of where revenue is created and where it can leak.

a) A-book/STP flow (typical)

In a clean A-book setup:

• Client sends order on MT4/MT5/cTrader/other platform.
• Your bridge/aggregator routes to LP(s).
• You receive an execution price and fill confirmation.
• Your revenue is primarily:
  • Spread markup (difference between client spread and LP spread)
  • Commission (if configured)
  • Swap (if positions held over rollover)

Leak points that reduce net profitability:

• LP spread widening in volatile sessions
• Rejections/last look causing worse fills
• Slippage asymmetry (clients get positive slippage, broker eats negative)
• IB rebates that exceed net capture

b) B-book flow (market making) and why pricing still matters

In B-book, the broker internalizes risk and P&L is driven by client outcomes. But pricing levers still matter because they impact:

• Client lifetime value (LTV) and churn (too expensive = short-lived accounts)
• Toxicity (too cheap + slow = attracts latency arbitrage and news scalpers)
• Dispute narratives (“you hunted stops” often begins with spread behavior)

c) Hybrid routing: the most common “real world” model

Hybrid models route some flow to A-book and internalize other flow. In hybrid, pricing must be consistent enough to avoid client confusion, but flexible enough to protect margin.

This is where a dedicated risk backoffice (like Brokeret’s RiskBO) becomes practical: you need real-time exposure monitoring, routing logic, and post-trade analytics to see whether your pricing and routing are working together.

4. Decision Tree: Start With Your Client Segments and Holding Time

The fastest way to choose a pricing mix is to classify your book by holding time, because it determines whether swap is a major factor and how sensitive clients are to spreads.

a) If most volume is intraday/scalping (minutes to hours)

Prioritize:

• Competitive spreads (markup must be tight and stable)
• Transparent commission (often acceptable for active traders)
• Swap is less important for revenue, but still important for trust

Common approach:

• Raw spreads + commission for “Pro/ECN” accounts
• Slight markup + zero/low commission for “Standard” accounts

Operational note: intraday flow is more likely to include toxic patterns. Your pricing decision should be paired with toxicity controls (execution protections, routing rules, and monitoring).

b) If most volume is swing/position (days to weeks)

Prioritize:

• Swap policy clarity and governance
• Competitive all-in cost over time (spread + swap + any commission)
• Dispute-proof disclosures

Common approach:

• Moderate markup (clients tolerate slightly wider spreads)
• Lower commission (or none)
• Carefully designed swap markup with strong disclosure and audit trails

c) If you serve multi-asset (FX + indices + metals + crypto CFDs)

Treat pricing as instrument-specific:

• FX majors: competitive spreads/commission drive acquisition
• Indices/metals: spreads can be wider; swap/financing becomes a larger LTV driver
• Crypto CFDs: spreads and financing are highly scrutinized; disclosure must be strong

5. Liquidity Markup: Where It Wins, Where It Breaks

Liquidity markup is often the simplest lever to operate, especially for STP brokers, because it’s earned immediately at execution and is easy to reconcile.

But markup can quietly become your biggest competitiveness problem if it’s not managed per symbol/session.

a) Benefits of markup-led pricing

Markup tends to work well when you want:

• Simple client messaging: “No commission” accounts are easy to sell.
• Predictable revenue per trade: revenue scales with volume.
• Cleaner accounting: spread capture can be monitored against LP spreads.
• Flexible segmentation: different account groups can have different markups.

b) The main risks: spread optics and execution complaints

Markup increases the visible spread. That can trigger:

• “Your spreads are too wide” churn
• Comparison-site pressure (clients benchmark against raw-spread brokers)
• Execution fairness complaints during volatility (“spread spikes”)

To reduce dispute risk, you need to:

• Separate “normal market widening” from “configured markup” in your monitoring
• Publish typical spreads by session (where allowed) and avoid misleading marketing
• Keep an internal audit trail of symbol/group markup changes

c) Practical markup governance

A workable governance setup looks like:

• Markup tables by symbol group (majors/minors/exotics/indices)
• Session-aware monitoring (London/NY/Asia)
• Maximum spread thresholds and alerts
• Weekly review of spread capture vs LP costs and IB rebates

6. Commission: The Transparency Lever (and the Rebate Trap)

Commission-based pricing is attractive because it decouples your revenue from spread optics. You can advertise tight spreads and still earn a stable fee per volume.

However, commission introduces second-order complexity: rebates, tiering, and “all-in cost” misunderstandings.

a) When commission is the best primary lever

Commission-led pricing is usually strongest when:

• You target experienced traders who understand ECN-style fees
• You run raw feeds and want spreads to reflect LP conditions
• You need predictable revenue per million/lot for forecasting

It also pairs well with hybrid models because you can keep client-facing pricing consistent while routing changes behind the scenes.

b) The biggest operational risk: IB/affiliate economics

Commission accounts often become rebate-heavy. If you don’t control it, you can end up with:

• Negative net revenue per million after IB payouts
• Incentives that attract low-quality traffic (bonus hunters, churn loops)
• Disputes when clients think “my IB said zero fees”

A practical control is to define a minimum net capture policy:

• Set a floor for net revenue per million after rebates
• Enforce it via CRM rules for IB tiers and client groups
• Review it monthly with finance + dealing

c) Commission disclosure that reduces tickets

Reduce “hidden fee” complaints by:

• Stating whether commission is per side or round turn
• Showing examples in the account type page (e.g., 1 lot EUR/USD)
• Including commission in platform trade confirmations where possible
• Ensuring your support team can reproduce the calculation quickly

7. Swap: The Highest Margin Lever With the Highest Dispute Surface

Swap can materially improve revenue, especially for longer-hold books and CFD products with financing costs. But swap is also where brokers get the most “unfair charge” complaints.

The goal isn’t to avoid swap revenue—it’s to make swap predictable, explainable, and auditable.

a) Why swap disputes happen (common root causes)

Most swap disputes come from a few patterns:

• Clients don’t understand rollover time or triple-swap day
• Symbol specs differ from expectations (e.g., metals/indices/crypto financing)
• Swap rates change and clients assume they are fixed
• Holidays create unexpected multi-day swaps
• Marketing implies “swap-free” but operational rules are unclear

b) Swap-free / Islamic accounts: high sensitivity area

Swap-free offerings are a commercial tool, but they are also a compliance and abuse risk area.

Best-practice controls include:

• Eligibility rules (jurisdiction, documentation, account history)
• Alternative admin fees disclosed clearly (if used)
• Abuse monitoring (long-hold strategies designed to exploit differential financing)
• Consistent treatment across symbols (avoid “surprise exceptions”)

Always check local regulations and consult compliance counsel for how swap-free products must be described and administered in your target markets.

c) The operational requirement: auditability

If you can’t reconstruct a swap charge from:

• Symbol settings
• Swap schedule and rollover timestamp
• Trade open/close times
• Holiday calendar inputs

…then you’re exposed. Swap revenue without auditability is not “revenue,” it’s future support debt.

8. Deep Dive: Building a Pricing Model That Minimizes Disputes (Without Giving Up Margin)

Dispute minimization is a design problem. You want fewer surprises, faster explanations, and fewer edge cases.

a) Create an “All-in Cost” narrative per account type

Clients experience cost as a bundle:

• Spread paid at entry/exit
• Commission charged at execution
• Swap charged at rollover

Your website and onboarding should explain this bundle with one or two concrete examples per account type. Keep the example stable and avoid cherry-picking best-case spreads.

b) Standardize disclosures and support artifacts

A dispute-proof setup usually includes:

• A public page explaining rollover time, triple-swap day, and variable nature of swap
• Symbol specification tables accessible from the client portal
• A support macro that asks for ticket essentials (symbol, ticket ID, timestamps)
• Internal runbooks for how to reproduce a swap calculation

c) Log every pricing change like a production deployment

Treat pricing config like code:

• Change requests with owner and reason
• Effective time (with timezone)
• Before/after values (markup, commission, swap)
• Impacted account groups/symbols
• Rollback plan

This is where broker tooling matters. A broker CRM + risk/backoffice stack should make it easy to prove “what the settings were” at the time of the trade, not just what they are today.

9. Modern Applications: Pricing by Account Type, Symbol, and Client Profile

The most effective brokers don’t argue about one perfect pricing model. They run a controlled portfolio of models.

a) Two-account architecture (common and effective)

A practical baseline:

• Standard account: modest markup, no commission, conservative swap policy
• Pro/Raw account: raw spreads, commission, tighter markup, same swap framework but clearer disclosure

This structure lets you:

• Acquire beginners with simple pricing
• Retain advanced traders with competitive spreads
• Reduce “bait-and-switch” perceptions by offering a clear choice

b) Pricing by symbol group

Avoid one-size-fits-all by grouping instruments:

• FX majors: tighter markup / lower commission
• FX exotics: wider markup due to liquidity cost and risk
• Indices/metals: spread + financing tuned per session
• Crypto CFDs: conservative risk controls, clear financing disclosure

c) Pricing by client profile (with compliance guardrails)

In hybrid setups, you may segment pricing by client group. If you do, ensure:

• Terms are disclosed and non-deceptive
• You avoid discriminatory practices prohibited in your jurisdictions
• You can justify differences as product/account-type driven

When in doubt, keep segmentation to published account types rather than invisible per-client pricing.

10. Best Practices Checklist: Implementing the Decision Tree in Operations

Use this checklist to operationalize pricing decisions so they survive real-world volatility and client scrutiny.

a) Pricing design checklist (pre-launch)

• Define target client segments (intraday vs swing vs mixed)
• Choose 2–3 account types maximum to start (avoid complexity)
• Set a minimum net capture target (after LP costs + rebates)
• Document swap principles (variable, rollover time, triple-swap day)
• Confirm platform configuration matches your published specs

b) Monitoring checklist (weekly/monthly)

• Track revenue per million by account type and symbol group
• Compare LP spreads vs client spreads (spread capture analysis)
• Monitor rejection rates, slippage, and execution quality metrics
• Review swap revenue vs swap complaints/tickets (cost of disputes)
• Audit IB payouts vs net capture floors

c) Dispute-prevention checklist (support + compliance)

• Maintain a public, plain-language swap explainer
• Provide symbol specs inside the portal (not just PDFs)
• Keep timezones explicit (server time vs local time)
• Store configuration history for markups/commissions/swaps
• Train support to reproduce fees from logs, not assumptions

11. Common Misconceptions That Create Pricing Mistakes

Pricing errors often come from assumptions that sound reasonable but fail in production.

a) “Lower spreads always win market share”

Lower headline spreads can attract volume, but if you can’t sustain net capture after LP costs, slippage, and rebates, you’re buying volume at a loss.

A better goal is competitive and stable spreads with transparent account choices.

b) “Commission is more transparent, so disputes go down”

Commission disputes are usually lower than swap disputes, but they still happen—especially around:

• per side vs round turn confusion
• IB promises that conflict with your fee schedule
• platform reporting mismatches

Transparency reduces disputes only when your disclosures and platform outputs match.

c) “Swap is just a platform setting; it’s not a business lever”

Swap is a business lever with:

• revenue impact
• reputational impact
• compliance impact

Treat it like a product feature with governance, not a backoffice afterthought.

12. Evaluation Criteria: How to Choose Your Primary Lever (Markup vs Commission vs Swap)

If you need a simple scoring model, evaluate each lever across four dimensions.

a) Profitability predictability

Ask:

• Does revenue scale linearly with volume?
• How sensitive is it to volatility and LP conditions?
• Can finance forecast it with acceptable error?

Typical pattern:

• Commission: high predictability
• Markup: medium-high predictability (depends on spread regime)
• Swap: medium predictability (depends on holding time and rate changes)

b) Competitiveness and client perception

Ask:

• What do your target clients compare (spread, commission, or both)?
• Do you compete on “no commission” simplicity or “raw spread” sophistication?
• Can you explain total cost in one minute?

c) Dispute risk and explainability

Ask:

• Can a support agent reproduce the charge from logs in under 10 minutes?
• Are the rules stable and documented?
• Are edge cases (holidays, triple swap) covered in public docs?

Swap usually scores worst here unless you invest in process.

d) Implementation complexity (systems + people)

Ask:

• Do you have tools to segment account types and enforce fee schedules?
• Do you have risk/backoffice reporting to validate spread capture and routing?
• Can your CRM manage IB tiers without breaking net capture?

A modern broker stack (CRM + risk backoffice + platform management + integrations) is what turns “a pricing idea” into a controlled operating model.

13. Future Trends: Where Broker Pricing Is Heading (and What to Prepare For)

Broker pricing is moving toward more transparency, better analytics, and tighter alignment between execution quality and commercial terms.

a) More emphasis on measurable execution quality

As clients become more sophisticated, they ask for:

• slippage statistics
• rejection rates
• spread stability

That pushes brokers to monitor execution and ensure markup decisions don’t create “spread spike” reputational events.

b) More granular segmentation (but with stronger compliance)

We’re likely to see more:

• account-type portfolios (Standard/Pro/Swap-free variants)
• instrument-specific pricing policies
• tighter governance and disclosure requirements

The winners will be brokers that can prove what they charged, why, and how it was disclosed.

c) Automation of pricing governance

Expect more automation around:

• configuration change logs
• fee reconciliation dashboards
• toxicity-driven routing tied to commercial outcomes

This is exactly where broker technology providers add leverage: fewer manual processes, fewer disputes, and faster iteration without breaking controls.

The Bottom Line

Liquidity markup, commission, and swap aren’t interchangeable—they create different client perceptions, operational burdens, and dispute risks. If your book is intraday-heavy, prioritize tight spreads and/or transparent commissions, and treat swap as a trust feature more than a revenue engine. If your book is longer-hold, swap governance and disclosure become as important as spread competitiveness.

The most resilient approach is a portfolio: two clear account types, pricing by symbol group, and strict guardrails on net capture after LP costs and IB rebates. Whatever mix you choose, invest in auditability—configuration history, reproducible calculations, and support runbooks—because the cheapest dispute is the one you designed out.

If you want help implementing a pricing model that aligns execution, profitability, and dispute prevention across your CRM, risk backoffice, and platform stack, Brokeret can help you map the decision tree into production. Get started at /get-started.