Hiring a Head of Payments: the rails and the P&L

Three different jobs

The most common hiring error we see is a lender hiring an aggregator's commercial leader because the title matched, then discovering the person has never been accountable for a success rate and has no instinct for the operational detail. The reverse error, hiring a strong operator into a revenue seat, is less common but equally expensive.

A useful test when writing the brief: if the role has a revenue target, it is the first job. If it has an uptime or success-rate target, it is the second. If it has neither and has partner acquisition goals, it is the third.

What the operating version owns

This is the most common version in Indian fintech outside the aggregators, and the one most often under-specified.

Payment success rate. The headline number, and a deeper one than it appears. Success rate varies by rail, by issuing bank, by time of day, by amount and by customer cohort. A leader who quotes one blended figure has not been managing it. Managing it means routing, retries, failover between acquirers and bank-level diagnosis, which is why the role has to be technically credible.

Cost per transaction. Rails have different costs, and the mix is partly controllable through presentation order, defaults and nudges. The arrival of MDR on UPI above ₹2,000 changes that calculus for the first time in six years and makes rail mix a live cost question rather than a settled one.

Routing and orchestration. Multiple acquirers, multiple PSPs, dynamic routing on success rate and cost, failover. Most scaled Indian fintechs either build an orchestration layer or buy one, and this role usually owns the decision.

Collections and mandates. NACH, UPI AutoPay and e-mandate registration, presentation, failure handling and re-presentation. For any subscription or lending business, mandate success is a bigger revenue lever than most product work.

Disbursals and payouts. IMPS, NEFT, RTGS and UPI payouts, with the idempotency discipline that keeps a retry from paying twice.

Settlement, reconciliation and float. Knowing what has actually settled, matching it, and resolving breaks. The function is described in reconciliation and breaks, and payments leaders who treat it as finance's problem tend to discover otherwise during an audit.

Partner and bank relationships. Acquirers, sponsor banks, PSPs, aggregators and, where relevant, NPCI. Commercial terms here often move the cost base more than any internal optimisation. Where this is a large part of the job it may be a separate seat; see hiring a VP of Banking Alliances.

Chargebacks, disputes and refunds. Operationally heavy, conduct-sensitive and usually inherited rather than designed.

Regulatory perimeter. Whether the company needs a payment aggregator licence, what it can do under a partner's licence, and where the line falls. Getting this wrong is an existential rather than commercial error.

What the commercial version owns

In an aggregator, gateway or PSP, the same vocabulary describes a different job.

Revenue and take rate across the merchant base. Pricing architecture, including the floor and who may go below it. Merchant acquisition, onboarding economics and churn. Category strategy, which has become sharper under the new UPI rate card, where capital markets at 0.02% and general merchants at 0.40% are now different businesses. Cost of processing negotiated with banks and networks. And the licence obligations that come with being a regulated payment aggregator, including settlement timelines, escrow discipline and merchant due diligence.

Candidates for this version should be able to talk about net take rate after processing cost, not gross MDR, and should have a view on which merchant categories are worth acquiring at what price. Those who talk only about GMV are describing a growth role.

Which backgrounds transfer

How to assess

Ask for their numbers. Success rate by rail, cost per transaction, mandate registration and presentation success, settlement T+n reliability. Candidates who have owned payments quote these without hesitation and know the seasonal and bank-level variation. This is the fastest and most reliable filter in the whole process.

Ask about a drop in success rate. A specific incident: one issuing bank degrading, an acquirer outage, a scheme change. How it was detected, how long before it was understood, what the fix was, what changed afterwards. Everyone who has run payments has this story.

Probe the rail-mix economics. "UPI now carries MDR above ₹2,000. What does that change about how you present payment options?" There is no single right answer, but there is a clear difference between a candidate who reasons about cost, success rate and customer preference together and one who has not considered it.

Test the reconciliation instinct. "Finance says ₹40 lakh is unreconciled from last month. What is your first move?" A payments leader who treats this as somebody else's problem is the wrong hire regardless of the rest.

Check partner negotiation. Ask about a commercial term they changed with a bank or acquirer and how. This separates leaders who accept the terms they inherit from those who manage them.

Assess technical credibility honestly. The role sits between engineering and commerce. Ask them to explain a payment failure path end to end. They do not need to write code, but a candidate who cannot describe what happens between a declined transaction and a refund will not hold the respect of the engineering team.

The search reality

Define the job before going to market. This is the whole brief problem for this title, and it causes more failed payments searches than any other factor. Companies that start with "we need a Head of Payments" and have not decided which of the three jobs it is will get a shortlist that cannot be compared.

Grade inflation is common. Payments has had rapid title inflation, and a Head of Payments at a Series A company may be running what a scaled company would call a manager's scope. Calibrate against scope and numbers, not against title.

The strong candidates are in a short list of companies. The payment aggregators, the large consumer fintechs, two or three banks and the broking platforms. Most are employed and are approached rather than applying, which is the method described in how we search.

Expect the UPI monetisation transition to move the market. The 15 October 2026 MDR change makes payments pricing experience newly valuable and has already begun repricing the people who have it. Companies benchmarking offers against last year's data are losing candidates. The specifics of that transition are covered in hiring a Head of UPI Business.

Settle the boundary with engineering. Payments sits across commerce and systems, and the most common cause of a Head of Payments leaving within a year is an unresolved boundary with the engineering leadership over who owns the orchestration layer. It is worth deciding before the offer, not after.