Why BFSI employees leave and how to understand why
Sales producers, branch staff and operations teams in financial services leave for different reasons. How to ask what shaped their decision and act on it.
7 min readRead articleA payment service provider moves money between customers, merchants and banks through software that must run at all hours. This page covers the people side: engineers, on-call cover, merchant onboarding, dispute handling and security discipline.

Not sure what you need? Tell us about your business in six short steps and we will come to the first meeting prepared.
Share your requirementsA payment service provider lets merchants and customers send and receive money, through gateways, wallets, card or bank links and settlement to merchant accounts. The team has engineers who build and run the platform, product staff, a merchant onboarding and risk team, merchant support who answer failed-payment queries, a reconciliation and settlement team, a disputes and refunds team, and security and compliance staff. Payments run at all hours, so outages and delays reach merchants within minutes. See also HR for banking, financial services and insurance. Staff handle money and personal data, so access control and honest conduct matter, while the pace of change, on-call duty and the stress of support queues make retention and fair rotas the core people issues.
These are the places the people side of this kind of business tends to give way. The rest of this page works through them.
HR here has to work for each of these groups, not only the office. The set-up below is written with all of them in mind.
GullyHR runs talent acquisition for permanent roles in payment service providers. For each role we agree the job description with you, find and screen candidates against it, and support the offer through to joining. Tell us the role and the number of people, and we start there.
We recruit permanent employees. We do not supply contract or temporary staff.
Every business interviews, but few have a written process that works the same way for every role and every interviewer. GullyHR designs yours, from the role brief to the offer, trains your managers to run it, and can run it for you on the roles you hand us.
We agree what the role must deliver, the must-have and nice-to-have skills, and how each will be scored.
Screening call, assessment, interview rounds and decision points, sized to the role and the number of people you hire.
Structured questions for each role family and a rating guide, so two interviewers judge the same answer the same way.
A short briefing for your managers on what to ask, what to avoid and how to give a clear yes or no.
Who approves, how the offer is made, and how candidates are kept informed from first call to joining.
Late-night incidents are handled by the engineers who know the system, and burnout comes before the next release.
Support executives deal with merchants whose money is delayed, and without scripts and backup they burn out quickly.
A mismatch between bank and platform figures takes days to trace, and the team is judged on speed and accuracy together.
Sales wants merchants live quickly while risk staff want careful review, and each blames the other when a bad merchant slips through.
Many staff can see sensitive records, and a casual habit becomes a risk, while honest people worry about being suspected.
Offers from larger firms and startups reach engineers weekly, and a missing second person on a module leaves the system exposed.
Chargebacks and refund cases arrive in waves, and the same questions repeat with little recognition for getting them right.
New features reach support and operations staff without notes, and merchants know more than the people answering.
Start with the topics that matter most here: HR Technology and Automation; Retention and Attrition Management; Health, Safety and Wellbeing. Then work through the rest. Each topic is written for banking, financial services and insurance, not in general.
Records that survive people, and approvals that do not queue.
Who leaves, when, why — and which of them mattered.
Induction, records, incident reporting and follow-through.
How many people, in which roles, by when — and what they will cost.
Structure, reporting lines and who is allowed to decide what.
Requisition to joining, the same way every time.
A first day that is the same for the fifth joiner as the first.
Records, attendance, leave and the day-to-day HR that must simply work.
Salary structure, payroll inputs and a month that closes on time.
Goals, reviews and ratings that hold up in a conversation.
Training planned from need rather than from the calendar.
Named backups for the roles that cannot be vacant.
Communication, recognition and the conditions people actually work in.
Two routes — one for complaints, one for conduct — kept separate.
Policies a manager can apply, and obligations with owners and dates.
Resignation to relieving letter, in a defined order.
A short monthly pack management actually reads.
An HR function that runs the same way every month.
The pieces a payment service providers business puts in place, in an order that makes each easier. Open any card for the detail.
A rota with limits on consecutive nights, rest after incidents and a recognised allowance or time off.
A rota with limits on consecutive nights, rest after incidents and a recognised allowance or time off. The shift and leave rules hold it.
Standard replies, an escalation line, a break after hard calls and weekly feedback.
Standard replies, an escalation line, a break after hard calls and weekly feedback. See the wellbeing routine.
Daily checks, named owners and a log of mismatches with causes.
Daily checks, named owners and a log of mismatches with causes. The documentation process keeps it.
What risk can decide, what sales can request and how a disagreement is settled quickly.
What risk can decide, what sales can request and how a disagreement is settled quickly.
Access by role, removal on exit or role change and a quarterly review, handled with the employee information process.
Access by role, removal on exit or role change and a quarterly review, handled with the employee information process.
A short note and training on each release that touches merchants, before it goes live.
A short note and training on each release that touches merchants, before it goes live. See the learning process.
Before changing anything, find out what is true today. These checks take an afternoon and tell you which of the topics above to start with.
Share your requirementsConfirm with a qualified professional. What applies to you depends on your business, your state and your arrangements, and it changes. This page describes practice. It does not state a legal position.
The services below fit this kind of business best. Each starts by recording where you stand, and every later report compares against that. We do not promise outcomes.
Fair on-call rotas with rest after incidents.
Support for merchant-facing staff under constant pressure.
Role-based access records and clean exits.
Release briefings and role-wise training for operations and support staff.
Start with a free conversation, or see the paid HR Diagnostic.
Understand the business, its workforce, current processes and HR challenges.
Find the missing, weak, inconsistent or person-dependent processes.
Create the structure, processes, policies, SOPs, dashboards and systems needed.
Help HR and department managers actually adopt the new system.
Digitise repetitive and approval-based workflows where it is worth doing.
Track hiring, attendance, employee cost, performance, training and attrition.
Strengthen the people-management system continuously, not once.
From the GullyHR blog: one on HR in banking, financial services and insurance, and one on each of the topics this page points to.

Sales producers, branch staff and operations teams in financial services leave for different reasons. How to ask what shaped their decision and act on it.
7 min readRead article
A simple timesheet routine for IT services teams: a short form, daily entry, light approval and a month-end lock that finance can bill from.
6 min readRead article
What really keeps mobile app and web developers in a small firm: stay conversations, growth paths, fair release rules and a risk sheet an owner can use this month.
6 min readRead article
A shift, weekly and monthly safety routine for rubber plants that names who checks platen guards, mill trip bars, autoclave doors, burst-test cages and slings, and who acts on near misses.
7 min readRead articleMore on the GullyHR blog.
Share the rota across enough people, cap consecutive nights, give rest after incidents and recognise the duty in pay or time off.
Give scripts, an escalation line, short breaks after hard calls and rotation into other work.
Agree a decision rule and a quick escalation path in advance, and review cases together.
Offer growth paths, shared ownership of modules, fair on-call terms and interesting work. Benchmark pay periodically.
Use role-based access, review it regularly and explain that it protects staff as well. Confirm data obligations with a qualified professional.
We would look at how on-call duty is shared, how merchant support is supported and how access is managed. An on-call policy with a support wellbeing routine is a likely opener. We set out scope, timing and fee in writing afterwards, so you decide what goes ahead.
All 39 business types in banking, financial services and insurance · Find another business type
See all HR topics for banking, financial services and insurance, or another industry.
Tell us what is slowing your team down. We’ll help you find a practical way forward, starting with a conversation.