Notes for owners · Industry playbooks
Why signed-up merchants never take a live payment
Merchants stall between signup and the first live payment at a few known points: KYC paperwork, a site that fails review, the integration, and silence. How to find which one and clear it.
The GullySales team · Updated 6 Oct 2026 · 5 min read
Rules for this trade differ by state and professional body, and they change. Check the current position with your own council or adviser before you act on anything here.
On this page
Most merchants who sign up and never take a live payment stalled at one of four points: documents they did not have to hand, a website that failed the review, an integration nobody helped them finish, or silence from your side after the form. Which one it is differs from application to application, and most companies cannot tell, because they record signups and nothing after. The fix starts with knowing the stage each application stopped at.
Why does a signup mean so little?
Filling a form costs the merchant two minutes. Taking a first live payment means they have found their documents, passed a review, connected your code or plugin to a real store, and decided to let a customer's money pass through you. Those are different levels of commitment.
A marketing report that says signups rose tells you the advertisement worked. It says nothing about whether any of those people ended up as merchants. The number that matters is the first live payment.
Where do applications actually stall?
Four places, in the order the merchant meets them.
Paperwork. The merchant is asked for business documents, a bank account in the business name, and proof of identity. A small online seller often has some of these in a drawer and some with their CA. The application sits until the missing item turns up, and no one on your side knows that is why.
The website review. Your partner bank and the rules expect a merchant's site to show certain things, such as what is sold, a refund policy, contact details and terms. Rules differ by body and change, so check them with your own compliance adviser. What you can see from the sales side is that a store with no refund page gets rejected, and the merchant is told only that the application did not pass.
The integration. Someone has to put your plugin or API into a real checkout. A developer friend who does this on weekends will do it once and give up if the documentation is behind a login or the error message is unclear.
Silence. After the form, nothing arrives for days. The merchant has already forgotten why they applied, or has signed up with a rival who rang.
What should you record for each application?
One row per application, with a stage and an owner. Not a dashboard, a plain sheet or CRM view that the whole team opens every morning.
| Stage | What it means | Who owns it |
|---|---|---|
| Form filled | Contact details only | Sales |
| Documents received | Merchant sent something | Operations |
| Documents complete | Nothing further to ask | Operations |
| Site reviewed | Passed, or failed with a reason | Compliance |
| Integration started | Sandbox key issued or plugin installed | Support or developer relations |
| First live payment | Real customer, real money | Everyone |
The reason column on the failed rows is where the learning is. After a few weeks of honest entries you will see that most failures sit in one or two stages, and that is where the page, the email or the call needs to go.
What can marketing do about each stall?
It cannot approve anything. It can remove surprises.
For paperwork, publish a plain page listing the documents commonly asked for, written in general terms and approved by your compliance officer, with a line that the final list depends on the partner bank and the rules. For the website review, publish what a merchant's store should show before applying, so they fix it first. For the integration, put the documentation where a developer can read it without signing up. For silence, give every application a named person and a first reply the same day, in the merchant's language, on WhatsApp if that is how they came to you.
Say the uncomfortable part on those pages too. Some merchants will not be approved. A page that says so honestly saves both sides a week.
For example: a payment gateway and a seller of handloom sarees on Instagram
Take a seller in Kanchipuram who takes orders on Instagram and signs up for payment links after a friend recommends your gateway. She uploads a photo of her shop licence and stops, because the form asks for a business account and hers is personal. Nobody calls. A month later she is taking payments through a competitor's link that a cousin set up.
If her application row had a stage and an owner, someone would have seen it sit at documents received on the first morning and rung her to say which account is needed and what the options are. That call is not marketing and not sales exactly. It is the work in between, and it is where the money is.
What about shoppers whose payment failed elsewhere?
If your inbox fills with people whose payment to some other shop failed, tag them in a separate queue and answer them with a short pointer to their own bank or the merchant. Do not let them sit in front of real merchant enquiries. The payment and fintech companies page covers how to keep the two apart.
What to do next
List the last twenty applications that never reached a live payment, and for each one write the stage it stopped at and what the merchant was last told. The gaps in that list are your marketing brief. The sales process page and the content marketing page for your trade show how to turn those gaps into pages and follow-ups. The free audit is a 90-minute call on how enquiries arrive and what happens to them, with a written, scored report after.