Merchant services leads for ISOs, agents and POS resellers.
ScoutedLead finds local businesses whose own website can't take a card payment, checks each one in a real browser, and puts the lead in your CRM assigned to the agent who covers its ZIP code.
Ask for 25 free merchant leads
Free: up to 25 merchant leads in one market you choose. You judge them before you pay for anything.
Prefer to talk? Call or text (616) 585-0206. Leave a voicemail or send a text and Aaron gets back to you.
- Reason
- Can't pay online
- Evidence
- The order page says "call to order, pay at pickup". No checkout or payment link on any page, loaded in a real browser on desktop and iPhone
- Uses today
- Clover, named on the gift card page
- Neighbors
- How many of the other bakeries we checked nearby take payment online, when the count holds up
- Contact
- Owner named on the About page; phone and email published on the site
- Routed to
- The agent who covers its ZIP code
example · every fact cites its page and the date we checked it
Hi Dana, I saw that cake orders at Maple & Main are phone-only, with payment at pickup. We help bakeries take a deposit online when the order is placed. Would a short look at how that works be useful?
Reasons a merchant is worth a call
Each lead carries one reason to reach out, and each reason has a rule for what must be true on the business's own website before we say it.
Can't pay online
“Your order page says to call in and pay at pickup”
Said only when the page, loaded in a real browser, has no checkout, payment link or online ordering.
Payments ISOs and agents
A POS you can replace
“Your online store runs on another POS system”
The system is named with the page we saw it on, so your agent opens with a switch, not a guess.
POS resellers
Behind the neighbors
“Other bakeries near you take orders and payment online”
Counted from businesses we checked in the same run, and left out of the lead when the numbers are weak.
Anyone selling payments
How to find merchants for credit card processing
The usual ways to find merchants are a bought list, a walk through the territory, or calls from a directory. Each gives you a name and a phone number, but no reason the owner should listen.
The better starting point is a payment gap the owner already lives with. A bakery whose website says “call to order, pay at pickup”. A repair shop that takes deposits by phone. A studio whose site names a POS you can replace. Those gaps are visible on the business’s own website, and they give your agent a first sentence that’s about the merchant, not about rates.
ScoutedLead looks for exactly that, in the markets you choose, and only says it when a real browser shows it.
What a merchant lead includes
Each lead names the business, its website, city and ZIP code, and the reason to reach out in plain words. The evidence comes with it: the page we saw, a screenshot and the date we checked. When the site names the payment or POS system it uses today, such as Square, Clover or Toast, the lead says so and links the page.
You also get the owner’s name when the site gives it, the phone and email the business publishes, and, when the numbers hold up, how many of the nearby businesses we checked already take payment online. An opening line written for your offer comes last, for your agent to review and send. The example at the top of this page shows the shape; the business in it is made up.
How leads reach your agents
You give us the territory map: which ZIP codes, cities or counties each agent, office or reseller covers. Every lead carries its ZIP code, so it lands in your CRM already assigned to the agent who works that area, with the evidence attached to the record.
During the pilot we set up the push into HubSpot or Salesforce with your own fields and owner rules. Until that’s live, the same leads arrive through the ScoutedLead API, on a signed webhook or as a CSV file your ops team can import. Your agents see one new record per merchant, with the reason at the top, not a spreadsheet to sort.
ScoutedLead vs. a bought lead list
A list and a scouted lead answer different questions. A list says who exists. A scouted lead says who needs a payments conversation now, and why.
| ScoutedLead | A bought lead list | |
|---|---|---|
| Who’s on it | Merchants with a payment gap or a POS you can replace | Businesses that match a category and an area |
| Why each one | The reason, with the page it came from and the date we checked | Not stated |
| POS they use today | Named when their own website shows it | Depends on the vendor’s data |
| Contact details | Only what the business publishes on its own site | From the vendor’s database |
| Opening line | Written for your offer, from the reason | Your agents write it |
| Routing | In your CRM, assigned by agent territory | A file to import and assign |
| Opt-outs | One do-not-contact list across every customer | The vendor’s own policy |
Start with 25 free merchant leads
Pick one market, such as a metro area outside California (we don’t work there or in Canada for now), and the kinds of merchants you want. We run the pipeline and deliver up to 25 leads, each with its reason and evidence.
We say “up to” because we only hand over a lead when its reason checks out, and we won’t pad the count. Your team judges the leads before you pay for anything. Use the form below or request access, choose “A software or marketplace company”, and tell us about your territories. How we check every lead explains the browser checks behind each one.
Leads for other platforms
Salon, barber and spa booking software. Shops that still book by phone, text or DM, with the scheduler they use when their site shows it.
Auto repair shop software. Independent shops that still take appointments by phone, with the shop system they use when their site shows it.
Restaurant online ordering and marketing platforms. Independent restaurants with no online ordering of their own, with what they use today.
Field service software. HVAC, plumbing, electrical and landscaping contractors whose customers can't book service online.
Common questions
How is it priced?
We don’t publish prices, because the work depends on your territories and volume. There are two ways to work together: we set the pipeline up for your team for a one-time setup fee, or we run it on our infrastructure and you pay for what you use. We quote after a short call. The first sample of up to 25 leads in one market is free.
How is this different from buying a merchant lead list?
A bought list tells you a business exists in a category and an area. Each ScoutedLead lead tells your agent why this merchant needs you now: no way to pay online, or a POS you can replace, with the page we saw it on and the date we checked. Businesses with nothing worth saying to them are dropped, so your agents don’t spend the day on dead calls.
Which CRMs do the leads go into?
Today, leads arrive through the ScoutedLead API as a pull feed, on a webhook signed with HMAC-SHA256, or as a CSV file. Pushes into HubSpot or Salesforce are set up for each customer during the pilot, with your own fields, lead owners and territory rules, because every sales team’s CRM is set up differently. A CRM that takes a webhook or a CSV import works from day one.
How fresh are the leads?
Each business is checked in a real browser when the lead is made, and the lead carries the date of that check. Websites change, so a finding is checked again before a lead is reused or delivered a second time. When a merchant tells your agent a finding is wrong, we fix the lead and the case becomes a test every playbook has to pass.
How do you handle opt-outs and compliance?
A business that asks not to be contacted goes on one do-not-contact list that every ScoutedLead customer’s runs check, so it never reaches you or anyone else again. Contact details come only from the business’s own website. We never send cold texts and never send for you: your agents send from your systems, under your compliance rules. Drafted emails carry your mailing address and an opt-out line.