Skip to content
GullySales

Payment and fintech companies · Sales process

Record where each merchant stops between signup and the first live payment.

A sales process for a payment or fintech company is the set of steps from a merchant's first enquiry to a first live payment, with a person named for each step. GullySales writes the steps in your own terms, adds the papers each one needs, and records where merchants stop.

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 sales process means

A sales process is the fixed sequence of steps, such as enquiry, site visit, quote and order, that every deal is expected to pass through in the same order. GullySales writes this sequence down for your business and checks that every salesperson actually follows it.

Plan the next part of the work

Last updated 21 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 and fintech companies

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

  • “Sales stops at signup but revenue starts at the first payment”

    A merchant who signed and never sends a transaction pays you nothing, yet the salesperson counts the deal as closed.

  • “Self-serve and assisted sales sit in one pipeline”

    A small seller who needs a plugin and a document list follows a different path from a company needing a security review, but both are tracked as one.

  • “The rate is quoted before the volume is known”

    A rate given before anyone asks about the platform, average order and refund pattern gets renegotiated, or turns out not to pay.

What we do

What we deliver for payment and fintech companies.

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

  1. Steps named in your own terms

    Enquiry, qualification, documents, integration, test payment, rate agreement and go-live, each with an owner and a record.

    Result: Everyone says the same word for the same stage.

  2. Qualification questions

    Platform, goods or service sold, payment methods wanted, refund pattern and current provider with the reason for leaving, set out as a call script and a form.

    Result: The first call finds out what the second call needs.

  3. A document checklist by type of business

    A one-page list for proprietorships, partnerships, companies and trusts that sales can send straight away. Rules vary by provider and partner bank.

    Result: A merchant starts KYC with the right papers.

  4. Quote rules

    Who may quote, what must be known before a rate is discussed and who approves an exception, written on one page.

    Result: Rates stop being invented on the phone.

  5. An integration handover

    A named support engineer, a test checklist and a go-live sheet shared with the merchant's developer.

    Result: The developer knows who to ask.

  6. Stage record and reasons for stopping

    Each merchant's stage, date and reason for stopping, so you can see whether KYC, integration or price is where they leave.

    Result: You fix the step that loses merchants.

How the result is measured

  • Enquiries with a named owner and next action
  • Opportunities meeting the stage evidence
  • Time waiting at each decision
  • Handovers returned for missing information

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

Steps of a sale

The steps from a merchant's first message to the first live payment, in the words a payments team uses.

Enquiry
Record how the merchant arrived, their platform and what prompted the search. Reply as a person with the document list for their kind of business, not with a brochure.
Qualify
Ask what they sell, which platform they run, the methods they want and the provider they use now. Note any refund or chargeback history, since your risk team will ask.
Documents and KYC
Send the checklist for their type of business, track what has arrived, and say what is missing in one message. Record the stage in the CRM so nobody asks twice.
Integration and test payment
Introduce the support engineer and share sandbox keys with a test checklist. Record when the first test payment succeeds and any error the merchant hit.
Rate agreement
Quote once the earlier steps are known. Put the fee lines, what each covers and what costs extra in writing, and record who approved any exception.
Go-live and first payments
Confirm the first live transaction and the first settlement credit with the merchant. Treat the sale as won only then, and ask what nearly stopped them.

Who it is for

This is written for these payment and fintech companies.

  • Payment gateways and aggregators for online sellers
  • UPI and QR providers with soundboxes and card machines for shops
  • Prepaid wallet and card issuers working with a partner bank
  • Digital lenders and buy-now-pay-later apps working with a bank or NBFC
  • B2B payment, vendor payout and payables platforms
  • Payroll, expense and corporate card tools for companies
  • Cross-border payment and remittance platforms
  • Neobanks and current account apps for startups and small businesses

Before you decide

When this may not be the right fit.

  • Your merchants sign up entirely on their own and no person speaks to them, so a sales process would have no calls to shape.
  • You cannot yet say where merchants stop between signup and the first payment, and the process would be built on a guess.
  • Engineering and sales will not agree who handles an integration problem, and the steps would break at the first stall.

Before you decide

Agree the work. Know how to judge it.

Sales process for payment and fintech companies: use these checks to prepare, choose the scope, and review what changes.

Bring the right evidence

Bring examples of deals that moved forward and deals that stalled. Record what the buyer had actually agreed at each stage rather than relying on the salesperson's confidence.

Make the scope clear

Define the entry and exit rule for each stage, the owner, and the document or decision that moves the deal. Agree how exceptions will be handled before rolling the process out.

Check the work in use

Take a live enquiry through the proposed stages with the team. Two people reviewing the same evidence should place it at the same stage and agree the next action.

Know when to change course

If a stage produces no useful decision or handover, remove it. The process should help someone do the next piece of work, not create administration for its own sake.

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 and fintech companies. Anything missing is noted in the written scope, with who will supply it.

One merchant's full trail of messages
Emails, chat and call notes for a single merchant from first contact to first payment. Names may be removed. Without a real trail we write the process from memory, and it misses the steps that cause delay.
The onboarding team's list of required papers
The exact documents your partner bank and compliance require by business type, as they stand. If it lives in someone's head, write it down before we start. A checklist with a missing paper sends merchants back to the beginning.
Your rule on who may quote and discount
The people allowed to name a rate or concede one, and any limits you want. An informal habit is acceptable, as long as we record it. Missing this, each salesperson invents a rule.
A salesperson and an onboarding lead
One person from each side, available to review the steps with us. If sales and onboarding do not speak to each other today, this is where the process breaks, and we start by getting them in a room.
Access to the system holding merchant records
Read access to the CRM or sheet where merchants are tracked, so we see the stages used now. If the records live in several places, tell us which is the main one.

How it works

How the sales process 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

    Walk the path of a real merchant with sales

    We begin by sitting with a salesperson and following one real merchant from the first enquiry to the first live payment, through each email, call and document request. You choose which merchant. We write down every step as it happened, including the ones nobody had named, which becomes the draft of your sales process.

  2. 2

    Name each step in your own terms

    We turn the walk into stages with names your team already uses, such as documents received, bank verified, test payment done. You decide the names and who owns each. We avoid generic labels, since a stage called qualification means nothing on the onboarding desk.

  3. 3

    Write the qualifying questions with onboarding

    We write the questions a salesperson asks in the first call, including the type of business, the products to be sold, the expected volume range and the documents the business holds. The onboarding team tells us which answers decide whether a merchant can be accepted. We agree what is asked before the quote.

  4. 4

    Build the document checklist by business type

    We write a checklist for each kind of merchant: sole proprietor, partnership, private company, trust or society. Your onboarding and compliance team supply the exact papers asked for. We keep it consistent with your policy and link it from the sign-up page.

  5. 5

    Set the rule for when a rate is quoted

    We write down who may quote a rate, based on what information, and who may agree an exception. Your head of sales and finance approve it. A rate quoted before the volume and business type are known has to be withdrawn, and we try to stop that.

  6. 6

    Read where merchants stop against the earlier record

    We add a stage and a reason-for-stopping field to each record in your system. After the team has used the process, we compare how many merchants reached each stage with the figures recorded before the work began, and review the reasons given. You decide which stage to improve next.

Where this fits

Three pieces of sales work, in this order.

This work sits inside sales process design, at stage 1, prospecting and lead generation. The audit comes before it, and sales management keeps it running.

  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 · you are here

    Sales process design

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

    Start here if every salesperson sells differently.

  3. Step 3

    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.

Who should handle integration support, sales or engineering?
Sales owns the relationship and the document list. A named support engineer owns the technical steps. A merchant should never be passed between the two without being told who has the next action.
When should we quote a rate?
After you know the platform, the kind of goods, the average order and the refund pattern, and after risk has a view. A rate quoted earlier gets screenshotted and renegotiated.
How do we handle a buyer who wants only the lowest rate?
Ask what they pay now and what it includes: settlement, refunds, support and hold policy. Show what a held settlement does to a seller's cash flow, and let them decide. If they leave on price, record it as price, not as lost.
What goes in the CRM after a call with a merchant?
The merchant's platform, the provider they use now, why they are looking, which papers are pending, and the next action with a name and a date. Add other notes only if someone will read them.
What should the CRM record after a call with a merchant?
The stage reached, the date, who spoke, the answers to the qualifying questions, the next step with a date, and the reason if the merchant stopped. Keep rate quotes and exceptions in a field of their own so finance can see them. Do not store documents or bank details in it. We write the fields as a short form that a salesperson can finish within the call, and the rest stays in your onboarding system.
Who decides that a merchant is not accepted?
Your onboarding and compliance team decide, from their own policy and your partner bank's requirements. Sales passes the case and the papers and tells the merchant the decision in words onboarding has cleared. We write the step so that sales never promises acceptance before verification is complete. The reason for a refusal is recorded as far as your policy allows, and reviewed so that sales stops sending merchants who cannot be accepted.
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.