Skip to content
GullySales

Payment service providers · CRM

Keep every merchant's path from enquiry to first payment in one record.

A CRM for a payment service provider records each merchant from first contact through documents, activation, integration and first live payment. GullySales sets up the stages, fields and views so field, support and onboarding teams read the same record.

Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

A fintech representative demonstrates a payment terminal to a shopkeeper

What CRM means

A CRM is the record where every enquiry, call and quote is kept against a customer, replacing separate notebooks, spreadsheets and memory. GullySales sets up or cleans an existing CRM and reports from it by enquiry outcome rather than by activity logged.

Last updated 14 Nov 2026. Rules for this trade differ by state and professional body, and they change. We describe restrictions in general terms, so check the current position with your own council or adviser before you publish anything.

For payment service providers

Where it usually goes wrong, and what we would do.

  • “A pipeline that ends at signup hides the real stall”

    The delay happens after the form is signed. A CRM with stages only up to signup shows a healthy pipeline while merchants wait for activation with nobody tracking them.

  • “Field executives record in their own notebooks”

    The merchant's shop, the promise made and the document still missing sit in a notebook or a chat. The activation team starts from nothing and asks the merchant again.

  • “One merchant can have several contacts”

    The owner signs, the accountant sends documents and the developer integrates. A CRM that allows one contact per merchant loses two of the three people the onboarding depends on.

  • “Reasons for a stall are more useful than counts”

    Knowing how many files wait is less useful than knowing why: an unclear document, a failed check, a missing integration step. The record has to capture the reason, not only the stage.

What we do

What we deliver for payment service providers.

The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.

  1. Merchant pipeline stages

    Stages from enquiry to documents, review, activation, integration and first payment, with an owner for each.

    Result: Every merchant sits at a named stage with a named owner.

  2. Fields for stall reasons

    A short list of reasons chosen when a merchant waits, such as missing document or integration pending.

    Result: You can count merchants by the reason they are waiting.

  3. Multi-contact merchant records

    Links between a merchant and its owner, accountant and developer, each with their role.

    Result: Every person involved in a merchant's go-live is on the record.

  4. Mobile entry for field executives

    A simple form for recording a visit, a promise and a document checklist from the shop.

    Result: Visits reach the activation team as structured entries.

  5. Views for field, onboarding and support

    Saved views so each team sees the merchants it must act on.

    Result: Each team opens one screen and sees its own work.

How the result is measured

  • Enquiries logged in the CRM
  • Data completeness
  • Reports generated from CRM data

Recorded as a baseline before work starts, so every later report has an honest comparison.

Fields worth keeping

Fields a merchant record needs so field, onboarding and support see the same merchant.

Merchant type and product
The field executive or web form fills it at entry. It routes the lead to the right product team.
Stage from enquiry to first transaction
Updated by onboarding as papers are verified. It ends at the first payment, not at signup.
Stall reason
Onboarding picks it from a fixed list such as documents pending or integration not done. It shows where merchants stop.
Contacts and their roles
The owner, the accountant and the developer on one record. A call to the wrong person is a wasted call.
Source and executive name
Recorded at the start. It lets you read live merchants by source and by field person.
First transaction date and volume band
Filled by the system when money moves. It separates merchants who transact from those who only signed.

Who it is for

This is written for these payment service providers.

  • Payment aggregators and gateways for online sellers and platforms
  • UPI QR, soundbox and card machine providers for shops and restaurants
  • Payment link and invoice collection providers for small sellers
  • Merchant acquiring resellers and sales partners
  • Payout and vendor payment platforms for marketplaces and businesses
  • Bill payment and recurring collection providers for fees and subscriptions
  • Cross-border payment providers for exporters and freelancers
  • Providers that serve a single sector, such as schools, clinics or logistics

Before you decide

When this may not be the right fit.

  • Your pipeline is thin enough to track in one sheet that the whole team already updates.
  • Field executives will not enter notes from the road, and the CRM would be empty where it matters.
  • Merchant papers would be uploaded into a sales tool that has no access control.

Before you decide

Agree the work. Know how to judge it.

CRM for payment service providers: use these checks to prepare, choose the scope, and review what changes.

Bring the right evidence

List the records your team uses and show how an enquiry becomes an order today. Bring examples of duplicate entries, missing owners, and reports that require manual correction.

Make the scope clear

Agree the stages, required fields, access roles, and integrations before configuring the system. Separate software subscriptions from setup, data work, and training.

Check the work in use

Ask the people who will use the CRM to complete a real handover and find the next action without help. Check that the management report can be traced back to individual records.

Know when to change course

If the process is unclear, buying a more complex CRM adds more places for confusion. Start with the minimum fields and rules the team can use consistently.

These are discussion points, not a fixed package. GullySales confirms the deliverables, responsibilities, fee, and term in writing after reading your brief and speaking with you.

Before we start

What to have ready before the work starts.

The records, access and decisions this work needs from payment service providers. Anything missing is noted in the written scope, with who will supply it.

Current merchant list from every source
The new records start from what you already hold: the onboarding sheet, executives' notebooks and any existing tool. Duplicates are acceptable. Without this list the register starts empty and your team keeps working in the old places.
A written description of your risk review
Merchants wait at the review stage, so the register must show it. A short note on who reviews, what they check and how a merchant is told will do. When it is missing, the review is a single box and stalls there cannot be explained. If the review has a second step for certain businesses, such as trusts or partnerships, describe that step too.
Phones and logins for field executives
Mobile entry only works if each executive can sign in on the phone they carry. A test with each person is enough. If some executives share a phone, we set separate logins before launch, because shared logins hide who entered what.
The software you may already be paying for
Tell us what tools you hold, even if they are lightly used. We can configure what you have, but we need to see it. If a tool cannot hold multiple contacts per merchant, we say so and you decide whether to change it.
One person to own the record
Someone must be told that the register is theirs. Not a committee. If no owner is named, fields drift, executives enter what they like and the stall reasons stop meaning anything. The owner also decides who may change stages or add stall reasons later, so the pick-list stays short enough to be useful.

How it works

How the CRM work runs

The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.

  1. 1

    Draw the path from enquiry to first payment

    We sit with your sales head, onboarding head and one field executive and draw the path a merchant walks: enquiry, call, documents, risk review, integration, first payment. You correct the boxes until they match what really happens, including the steps where the merchant waits for your side. We note where the merchant is waiting on your side, such as a risk review, because the register should show who holds the delay.

  2. 2

    List stall reasons your team already uses

    We collect the reasons executives give for lost or stuck merchants and turn them into a fixed pick-list. You choose which are real and which are excuses. Afterwards, a merchant cannot be moved to stalled without a reason, which later becomes the field you will read first in the register. We keep the list short enough for an executive to choose from at the shop counter.

  3. 3

    Set up merchant and contact records

    One merchant can have an owner, an accountant and a developer, each with a number. We configure the record so contacts hang under a single merchant. You confirm which fields are mandatory for field entry and which belong only to onboarding.

  4. 4

    Build the three views your teams open

    Field executives see their own leads and next calls. Onboarding sees merchants waiting for documents or reviews. Support sees merchants live but silent. We build each view with your team leads sitting beside us, and they mark what is missing.

  5. 5

    Run a test with copied merchant files

    We load a batch of old merchants into a test copy and ask staff to update them as they would on a normal day. Mismatched stages and mobile entry problems show up here. You decide whether the stages are right before the live switch. Executives enter a lead from a phone while standing at the shop, and onboarding staff update the same record from a desk, so we watch both.

  6. 6

    Switch over and compare the funnel

    Once the switch is made, the old notebooks are retired. We compare the funnel against the starting figures: enquiries, documents complete, integrated, first payment. You decide which stall reason deserves attention first and who owns it.

Where this fits

Three pieces of sales work, in this order.

This work sits inside sales management. A target, a review routine and someone who owns the number.

  1. Step 1

    Sales audit

    Find where deals are being lost and what to fix first.

    Start here if you cannot say where orders are lost.

  2. Step 2

    Sales process design

    One written way to sell, from first enquiry to repeat order.

    Start here if every salesperson sells differently.

  3. Step 3 · you are here

    Sales management

    A target, a review routine and someone who owns the number.

    Start here if the team has targets and no routine.

Tell us what you need Your brief is read before we call. Scope, fee and term in writing.

FAQ

Questions owners ask before they call.

Not here? More answers, or ask on WhatsApp.

Do we need to buy new software?
Not necessarily. We set up the pipeline in the tool you already use where it can hold the stages. If it cannot, we help you compare options and leave the choice to you.
Who keeps the CRM updated?
The people who touch the merchant. We design entries to be short so field and onboarding staff can update them without extra effort, and we review whether they are kept current.
Is merchant data safe in a CRM?
Merchant documents and identity details are sensitive. Decide with your compliance and security teams what is stored, who can see it and where it sits, and keep documents out of casual chat.
Should the CRM link to the payments dashboard?
A link that shows first transaction date and status is useful, because the CRM then knows when a signup goes live. Keep the merchant's financial data in the payments system with its own access rules, and pass only the status across.
Should the CRM connect to our payments dashboard?
It helps, but start without it. The first connection worth making is the one that marks a merchant as live when the first payment arrives, since that closes the loop on every lead. Your engineers decide whether the dashboard can send that event safely. Until then, onboarding staff mark go-live by hand. We specify what is passed across and keep card and bank details out of the CRM altogether.
What if our executives refuse to use another system?
Then the design is wrong, and we change it. The mobile screen asks for the few fields an executive can fill in standing at a shop counter, and the rest is filled by onboarding. We show executives what they gain: their follow-ups listed in order and fewer calls from onboarding asking for status. If someone still resists, you decide the rule, such as paying incentives only on leads in the register.
How much does it cost?
There is no price list, because the work differs by business. The fee is scoped after we have read your brief and spoken to you, and put in writing before anything starts, split into our time, your media spend and production.
How long is the contract?
The term is agreed in writing after we have spoken, along with the fee and the reporting. It is never a default twelve months, and renewal is decided on the numbers against the baseline recorded at the start.
How soon will we see results?
It depends on the trade, the channel and what is already in place. After we have read your brief and spoken to you, we say what we would expect to move first and how it will be measured against the baseline. Nothing here is guaranteed.
Who will actually do the work?
The person you speak to before anything starts. We work from one office in Nagarbhavi, Bengaluru, with no account managers in between.

Your next practical step

Tell us what you are trying to grow, and we will read it before we call.

Eight short steps, mostly taps. Skip anything you would rather answer on the call.