Skip to content
GullySales

Payment service providers · Buyer persona

Know who is buying, who is signing and who is blocking the merchant's go-live.

A buyer persona for a payment service provider describes the person who chooses a provider, the person who signs, and the person who supplies the documents. GullySales builds those personas from your merchant records and your field team's notes, so each message goes to the right reader.

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 buyer persona means

A buyer persona is a plain description of the kind of customer who actually buys from you. It includes what they search, what worries them and who else they ask before deciding. GullySales builds this from real enquiries and past sales rather than a generic template, then uses it to write every page and advert.

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.

  • “The owner decides, the accountant gathers the papers”

    In a small business the owner picks the provider and the accountant or an employee collects the documents. The pitch reaches the owner, and the stall happens on the desk of someone who was never sold to.

  • “An online seller compares on integration, not on charges”

    A seller on a store platform asks whether a plugin exists and how the first test payment works. Charges matter later. The page that answers the plugin question wins the trial.

  • “A developer is a buyer with a veto”

    The founder may want your gateway, and the engineer may refuse after reading the documentation. Treating the developer as a technical afterthought loses deals already agreed in principle.

  • “A finance head wants reports before features”

    At a larger business the finance head asks about settlement reports, reconciliation and support escalation. A pitch built on checkout design misses what that reader needs to feel safe.

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. Four core personas

    Written profiles of the shop owner, the online seller, the developer and the finance head, with what each reads and fears.

    Result: Your team has a shared description of each buyer.

  2. Decision-chain map

    A map of who initiates, who approves, who supplies documents and who integrates, for small and larger merchants.

    Result: You can see who to speak to at each stage.

  3. Message sheet per persona

    The opening line, the proof offered and the likely objection for each persona, in wording compliance has approved.

    Result: Field executives and writers use the same lines.

  4. Questions from real calls

    A set of questions drawn from recorded field notes and support tickets, sorted by persona.

    Result: The personas rest on what merchants actually asked.

  5. Persona tags in the register

    A field in your lead register recording which persona each contact is.

    Result: You can compare progress by persona.

How the result is measured

  • Enquiry match to persona
  • Conversion rate by persona
  • Content aligned to persona

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

Who is asking

The people involved when a merchant chooses a payment provider.

Shop owner who wants a QR
They ask whether the money reaches their account and what it costs. A demonstration at the counter answers better than a brochure.
Accountant gathering the papers
They ask for the document list and the settlement report. Send one checklist and one sample report.
Online seller on a platform
They ask about the plugin, payment methods and failed-payment handling. They compare integrations before charges.
Developer evaluating the API
They look at documentation and a sandbox first. Reply with a working example, not a sales call.
Finance head at a larger business
They ask for reconciliation, refunds and support escalation. A reference call and a sample report speak to them.
Platform or marketplace operator
They ask about payouts to vendors and the compliance steps involved. Provide a clear note on what you handle and what they must.

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.

  • You have not recorded why merchants stall, so a persona would describe a buyer you imagine and not the one you have.
  • Your field team and online team do not share notes, and the personas would reflect only one of them.
  • You sell a single product to a single kind of merchant, and one page already covers the buyer.

Before you decide

Agree the work. Know how to judge it.

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

Bring the right evidence

Write the decision the research must support, such as entering a market or choosing a buyer group. Separate what you know from sales records from what the team currently assumes.

Make the scope clear

Agree which buyers to speak to, which sources to review, and what access you can provide. Include lost enquiries and people who chose another supplier, where they are willing to take part.

Check the work in use

Look for source dates, sample limitations, and evidence that disagrees with the preferred answer. A recommendation should show how it follows from the findings.

Know when to change course

Do not treat a few positive conversations as proof of demand. Test the proposed offer with an actual buying decision before committing to a wider launch.

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.

Permission to interview some merchants
Interviews need introductions from your side, because merchants answer a provider they know. A short list with consent to be called is acceptable. When none are given, personas rest on records alone and miss the reasons people give in conversation. Say also whether any merchant has asked not to be contacted, so the list we receive is one we may actually use.
Rejected and abandoned application files
The stalled merchants show where each persona blocks. Files with identity details removed are fine. Without them, we only hear from successes, and the personas will look easier to win than they are.
A field executive for ride-along calls
Listening to an executive pitch a shop owner shows what the buyer asks first. One executive willing to be observed is enough. If nobody agrees, the shopkeeper persona is written from second-hand accounts. Tell us which kind of shop the executive visits, since a pitch to a pharmacy differs from one to a restaurant or a tuition centre.
A developer who integrated recently
Developer personas need someone who has just been through the sandbox. A conversation with an engineer from a merchant, or your own team member who supported them, is acceptable. Without that voice the developer persona carries guesses about what blocks them.
Your own view of the best merchant
Only you can say which merchant you would like ten more of. A short description is enough. If it is missing, personas weigh every merchant alike and may lead messages toward volume that does not suit you. If your best merchants share a trait, such as taking payments on a platform, a counter or an invoice, name it and we will test it in the interviews.

How it works

How the buyer persona 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

    Choose which buyers to describe first

    We ask your sales head which merchants stall and which carry the highest value for you, then pick four buyers to study. Typical choices are a small shop owner, an online seller, a developer and a finance head. You can change the four before any interviews are arranged.

  2. 2

    Pull recent onboarding files and call notes

    We read a sample of merchant files, rejection reasons and notes from calls. You choose which merchants we may read and hide names where needed. Out of this step comes a list of facts already recorded: who signed, who sent papers and who asked about integration. We note too which papers arrived from the accountant and which from the owner, because that shows who gathers and who signs in each merchant type.

  3. 3

    Interview merchants who went live or left

    With your introduction we speak to some merchants who completed onboarding and some who dropped out. We ask who first raised the need, who compared providers and who delayed the papers. You decide who is called, and we note what they say in their own words.

  4. 4

    Trace the decision chain in three merchants

    For one shop, one online store and one platform business, we draw who touched the decision: owner, accountant, developer, a relative who sends documents. The map shows where a veto sits. You read it against your own memory of those deals and correct it.

  5. 5

    Write the personas and test them with your team

    We write the four personas with their questions, worries and the messages that answer them. Your field executives and onboarding staff mark anything that does not match what they hear. We rewrite the sheets until the people who speak to merchants recognise them.

  6. 6

    Tag the register and read what changes

    Each lead in the register receives a persona tag. We then compare conversion to first payment by persona against the starting figures. You decide which persona gets more attention in the website, the follow-up messages and the field visits. Tags are added by field executives and onboarding staff, so we write one line per persona that tells them how to recognise it on a call.

Where this fits

Three pieces of sales work, in this order.

This work sits inside sales process design, at stage 0, foundation. 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.

Where does the persona information come from?
From your field executives' notes, your support tickets, onboarding records and a few conversations with merchants. We do not invent details about buyers.
How many personas do we need?
As many as there are distinct decision roles in your merchant mix, and no more. The segments in your business point to the shop owner, seller, developer and finance head.
Do personas change the website?
Yes. Each persona gets its own entry page and message, so the shop owner is not asked to read an API diagram and the developer is not given a sales brochure.
Should a persona name the merchant's bank?
Not by name. A persona describes the role and the question, such as the owner who wants to know where settlement lands. A bank name is a detail on the lead record. The point of a persona is to guide what the caller says first.
Do we need to pay for market research for personas?
No. This work uses what you already hold: onboarding files, support tickets, rejected applications and recorded calls, along with a small number of conversations with merchants and your own staff. We do not buy survey panels or invent audience data. The personas describe the buyers you have actually met, and the sheets say which part came from a file and which from a conversation, so you can judge how far to trust each line.
Can a persona include the merchant's turnover?
Only if you hold it in your own records and approve its use. We describe merchants by what they sell, who decides and how they pay, not by invented sales brackets. If your register already carries a turnover band, we can group by it. We will not insert figures from outside sources or estimate turnover for the persona sheet. A persona is a description of a buyer, not a forecast of what they will spend.
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.