Where does the Head of Payments sit in an iGaming org chart?

Most commonly under the COO or CFO. Smaller operators sometimes have payments reporting into product or commercial — that usually changes once volume grows because the cross-functional load on engineering, finance, compliance, and customer experience becomes too much for a non-payments leader to coordinate.

What's the typical compensation range?

In licensed European iGaming in 2026, Head of Payments base salaries range from €90K-€180K depending on operator size, with significant bonus components tied to deposit-conversion lift, decline-rate reduction, and PSP cost optimisation. London and Malta tend to set the upper bound; Estonia and Bulgaria the lower.

What are the key KPIs the Head of Payments owns?

Approval rate (overall and by PSP/method), deposit conversion rate (from cashier-open to deposit-success), decline-recovery rate (% of declines retried successfully), withdrawal NPS, fraud loss ratio, chargeback rate, and total payment cost as % of GGR. Strong operators track all seven monthly.

What's the team size around a Head of Payments role?

At smaller operators (€100K-€1M monthly volume), it's often a one-person role with shared services from finance and engineering. At mid-size (€1M-€10M monthly), 2-4 reports — typically a payment-ops analyst, a PSP relationship manager, and possibly a fraud lead. At enterprise scale, 8-15 with sub-functions.

How does the Head of Payments interact with vendors like Fluid?

They're the buyer for cashier and orchestration vendors; they're also the day-to-day operator partner once a vendor is live. Strong vendor relationships are weekly cadence with the Head of Payments' team, monthly cadence with the Head of Payments themselves, and quarterly business reviews with the COO/CFO above them.

What a Head of Payments at an iGaming Operator Does

What the Head of Payments role looks like inside a licensed iGaming operator in 2026 — scope, KPIs, daily and quarterly priorities, and team structure.

The Head of Payments role at a licensed iGaming operator is one of the most cross-functional jobs in the business. It sits in the cracks between product, engineering, finance, customer support, fraud, and compliance — and when payments go wrong, every one of those functions feels it within minutes.

This guide is for two audiences: people considering or moving into a Head of Payments role at an iGaming operator, and anyone (vendors, peers, executive teams) trying to understand what the role actually entails day-to-day.

What the role owns

There’s no perfect job description, but the scope clusters into five areas:

1. PSP and gateway relationships

Owns the contractual and operational relationships with payment service providers. At even a mid-size operator, that’s typically 3-7 PSPs across geographies, plus the alternative-payment-method providers (Trustly, Pix processors, Apple Pay program), plus the orchestration or cashier vendor sitting on top.

Day-to-day: monitoring approval rates by PSP and method, escalating when one PSP’s performance degrades, scheduling QBRs, negotiating renewals, evaluating new PSPs.

2. Deposit and withdrawal experience

The player-facing flow. This is where the role overlaps with product — and where the line between “payments problem” and “product problem” blurs. The Head of Payments typically owns the cashier UI in partnership with product, and is the senior accountable owner for deposit-conversion KPIs.

3. Fraud and chargeback management

In iGaming, fraud and risk sit closer to payments than at retail e-commerce because the regulatory framework binds them tightly. The Head of Payments often owns chargeback strategy, fraud-rule configuration, and the vendor relationships with fraud tools like Sift, Featurespace, or Forter.

4. Cost optimisation

Payment processing fees plus chargeback fees plus fraud losses plus FX spread plus interchange = the second- or third-largest cost line at most operators. The Head of Payments is the only person who can pull all those levers coherently. Saving 15-30 bps on processing across an operator doing €10M monthly is a million euros a year.

5. Compliance liaison

Payments are heavily regulated. The Head of Payments is the operational interface with compliance — making sure the cashier respects deposit limits, that affordability checks are surfaced when required, that AML thresholds trigger the right KYC step-ups, that source-of-funds checks fire on high-value deposits.

A typical week

Roughly:

Monday: monitoring dashboards and last-week trends. Approval rate by PSP, decline patterns by reason code, deposit conversion by geo/method/device. Calls with PSPs whose numbers slipped.
Tuesday: vendor cadence calls. Cashier vendor weekly stand-up. PSP technical syncs. Roadmap reviews.
Wednesday: internal cross-functional. Fraud team review of the prior week’s flagged transactions. Customer support escalations involving payments. Engineering check-in on the deposit-flow backlog.
Thursday: strategic / project work. Whatever the bigger initiative is — onboarding a new PSP, evaluating a new market, prepping for a regulatory change.
Friday: finance and reporting. Settlement reconciliation. Cost-of-payments tracking. Forecasting next month’s volume + cost.

Quarterly add-ons: roadmap planning with product, vendor QBRs, executive payment reviews, license-specific compliance reporting.

KPIs the role lives or dies on

Operators differ in their dashboard, but seven KPIs come up universally:

Approval rate — % of transactions approved by the PSP. Tracked overall and per PSP/method.
Deposit conversion rate — % of cashier opens that result in a successful deposit. End-to-end UX KPI; the Head of Payments shares ownership with product.
Decline-recovery rate — % of declined transactions that succeed on retry (auto via smart routing, or via a different method).
Withdrawal NPS / withdrawal time — withdrawal speed is a top-3 retention driver in iGaming surveys.
Fraud loss ratio — fraud losses as % of total volume. Industry benchmark: 0.05-0.20% in mature operators.
Chargeback rate — chargebacks as % of total transactions. Card schemes will deplatform you above 1%.
Total payment cost — all-in cost of payments (processing + chargebacks + fraud + FX + cashier license + ops headcount allocation) as % of GGR.

Strong operators report these monthly to the executive team. The Head of Payments is typically the one presenting.

How the role evolves with operator size

Three rough sizes:

Small operator (€100K-€1M monthly volume)

Often a single Head of Payments with no direct reports, supported by one engineer (part-time), one finance analyst (part-time), and one fraud reviewer (often outsourced). The role is heavily hands-on — configuring rules in the cashier, reading PSP dashboards directly, sometimes coding the integration glue.

Mid-size operator (€1M-€10M monthly volume)

Team of 2-4. Typically: a payment-ops analyst (operations), a PSP relationship manager (commercial/technical), and a fraud lead. Engineering is partnered but reports elsewhere. The Head of Payments is now more strategic, less hands-on.

Enterprise operator (€10M+ monthly)

Team of 8-15+, often split into sub-functions: payment ops (incident response, vendor management, daily KPIs), payment engineering (cashier and integration code), payment risk (fraud and chargebacks), payment finance (reconciliation and reporting). The Head of Payments is now mostly executive-facing, with strong directors running each sub-team.

Skills that distinguish strong Heads of Payments

We’ve worked with dozens of these roles across our customer base. The common thread among the strong ones:

Numerical fluency without losing the player. They can read a decline-rate report and explain it in product terms.
Vendor management with leverage. They negotiate from real performance data, not from gut.
Cross-functional credibility. Engineering respects them, finance listens to them, compliance works with them.
Honest about trade-offs. They can articulate why their cashier picked X over Y, and what the cost was.
Comfortable with regulation. They don’t need a compliance officer to read a license requirement.

The weak ones, candidly: drift into pure vendor management, lose touch with the player UX, and end up arguing about basis points while the deposit conversion rate quietly erodes 200 bps.

What this role buys (and how vendors like us think about it)

When a Head of Payments evaluates a cashier or orchestration vendor like Fluid, they’re not buying software. They’re buying:

A reduction in the number of relationships they have to manage themselves.
A roadmap they can trust without owning.
A conversion-rate uplift they can defend to the COO.
A fraud and risk posture that compliance will sign off on.
A negotiating position with their existing PSPs (multi-PSP setups give the Head of Payments real leverage).

The vendor’s job is to deliver all five without becoming a dependency the Head of Payments regrets at year 2. That’s actually a high bar.

For more on what we mean by that bar, see our iGaming Payment Solutions Comparison and the iGaming Payment Provider Evaluation Checklist.

If you’re a Head of Payments mid-evaluation and want a non-pitchy second opinion, we’d love to talk. And if you’re a candidate moving into one of these roles for the first time, the same offer stands — happy to share what we’ve seen across our operator base.