MerchantCardLeads · For payments professionals

    How Do You Avoid Duplicate Leads?

    We reduce duplicate merchant leads with a 30-day phone/email deduplication window. Matching repeat inquiries are filtered rather than treated as new leads during that window. You should also check every purchase against your own CRM before outreach. Our shared leads cost $25 each, and exclusive leads cost $45 each.

    Last updated October 26, 2026

    How much do merchant leads cost?

    Shared

    $25.00 / lead

    Exclusive

    $45.00 / lead

    Aged from

    $0.75 / lead

    Shared: up to 3 buyers. Fresh exclusive: one platform buyer. High-risk, volume and aged profile adjustments can change prices.

    Updated Oct 22, 2026

    What inventory is available?

    8

    Received in the last 30 days

    928

    Aged inventory pool

    Updated 10/26/2026, 9:00:00 PM UTC. Pool totals are not a promise of matching inventory for your account.

    e-commerce

    Not provided, Not provided

    Volume: Under $10K

    Received 506h ago

    other high risk

    Not provided, Not provided

    Volume: Under $10K

    Received 509h ago

    other high risk

    Not provided, Not provided

    Volume: $50K – $250K

    Received 590h ago

    How does our 30-day duplicate protection work?

    Our duplicate check uses phone and email to identify repeat inquiries within a 30-day window. That helps keep a merchant’s repeated submission from becoming another new lead during the protected period. The purpose is to reduce repeated delivery, not to promise that every merchant is someone your team has never encountered.

    A time-limited check is different from permanent account exclusion. You may already know a merchant through prospecting, a referral, another provider or an earlier purchase. A merchant may also use a different phone number or email address on a later inquiry. We recommend treating our duplicate protection and your CRM checks as complementary controls: we screen repeat inquiries within our window; you screen against your full relationship history.

    What happens when an inquiry matches a recent lead?

    Matching repeat inquiries within our 30-day phone/email window are filtered from the new-lead flow. A repeat submission should not become a reason for your representatives to restart the same sales conversation independently.

    If a delivered lead appears to overlap with an existing CRM contact, hold automated outreach while you review the match. Compare purchase timing, previous conversations and the phone or email responsible for the overlap. Keep the purchase reference and a concise explanation together so you can raise a clear support request.

    Our return window is 72 hours. Eligible returns receive wallet credits, not cash refunds; a CRM match alone should not be treated as an automatic credit. Aged lead returns are limited to bad phone numbers. Review purchases promptly rather than waiting until a duplicate has triggered multiple outreach attempts.

    How should you dedupe purchased leads against your CRM?

    We recommend checking incoming leads before creating new sales tasks or starting an outreach sequence. Use a consistent process across all representatives and lead sources:

    1. Standardize phone formatting, including country codes, so punctuation does not hide a match. 2. Trim extra spaces from email addresses and use consistent capitalization for matching. 3. Search phone and email separately. A match on either deserves review, even when the other differs. 4. Compare the merchant’s business identity and prior activity before merging contacts. 5. Route a confirmed match to the existing owner instead of assigning a second representative. 6. Preserve purchase history, conversation notes, consent evidence and suppression preferences.

    Avoid merging solely because two businesses have similar names. Conversely, a changed business name does not necessarily mean a new buying opportunity. Your review should distinguish a repeated contact from a separate merchant location or a genuinely separate business.

    How should your team handle older matches and shared business contacts?

    Your CRM review should extend beyond our 30-day window. An older contact may still have an active proposal, a scheduled follow-up or an instruction not to contact them. A later inquiry does not justify erasing that history.

    Shared phone numbers and email addresses also require care. Multiple locations may use one central office, while several employees may discuss processing for the same merchant account. We recommend linking related contacts to the appropriate business account and keeping one clear sales owner.

    For uncertain matches, pause the new sequence and request a manual review. For confirmed duplicates, update the existing relationship rather than creating competing tasks. Keep the later inquiry’s date and origin so your representative can understand what changed without losing the earlier context.

    Does buying exclusive leads eliminate duplicate concerns?

    No. Exclusivity concerns distribution; deduplication concerns repeated identity. Our $25 shared leads can reach up to three buyers. Our $45 exclusive leads offer a different distribution choice, but neither option establishes that the merchant is absent from your CRM.

    Fresh exclusivity does not prohibit later disclosed aged resale. If you buy across fresh and aged options, check both against the same CRM history rather than maintaining separate lists that cannot recognize overlaps. Pricing can vary for high-risk or high-volume leads.

    We recommend choosing distribution based on your sales approach while applying the same duplicate controls to every purchase. Keep acquisition cost attached to the purchase history, not to an inflated count of new prospects. That gives you a more useful view of spend and workload. We require no contracts; you can pause anytime.

    How should consent and opt-outs survive a duplicate merge?

    Our own campaigns display this disclosure: “By submitting, you agree that MerchantCardLeads and its partner payment-processing providers may contact you by phone, text and email about merchant services, including via automated technology. Consent is not a condition of purchase.”

    New campaign leads carry the captured consent text, timestamp and source page in dashboard, email and webhook delivery. When you merge duplicate contacts, preserve that evidence alongside earlier communication history rather than replacing everything with the newest entry.

    You are responsible for TCPA and DNC rules in your own outreach. Deduplication is not permission to call or text, and an aged purchase does not establish renewed consent. Keep opt-outs visible during review and resolve conflicting preferences before outreach. Your buyer SMS alert opt-in is separate from a merchant’s permission to receive your messages.

    Where these leads come from

    Our owned merchant-services sites and campaigns attract business owners searching for processing quotes, savings reviews and provider comparisons. New campaign inquiries are inbound and include partner-contact consent. Historical aged leads retain their original source and consent evidence; they are not new inquiries.

    Explore our lead sources

    What should you know before contacting a merchant?

    Our campaigns capture merchant inquiries with a disclosure naming MerchantCardLeads and partner payment-processing providers. New campaign leads include the captured consent text, timestamp and source page in your dashboard, email and webhook delivery. You are responsible for following TCPA and DNC rules in your own outreach.

    By submitting, you agree that MerchantCardLeads and its partner payment-processing providers may contact you by phone, text and email about merchant services, including via automated technology. Consent is not a condition of purchase.

    Buyer SMS alerts use a separate opt-in: “I agree to receive automated lead-alert text messages from MerchantCardLeads at this number. Msg frequency varies. Msg & data rates may apply. Reply STOP to opt out, HELP for help. Consent is not a condition of purchase.”

    No contracts. Pause anytime.

    Real-time return requests: within 72 hours. Approved returns become wallet credits; “already has a processor” is not a valid return reason. Aged returns: bad phone only.

    Chad Buchanan · Founder, MerchantCardLeads · (248) 686-6955

    What else do payments reps ask?

    Should we require both phone and email to match before flagging a duplicate?

    We recommend flagging a match on either for review. Requiring both can miss a merchant who changes an email address but keeps the same phone number.

    Should a duplicate go to the original representative or the next person in rotation?

    We recommend retaining the existing owner unless your team deliberately reassigns the relationship. Check ownership before creating tasks so two representatives do not contact the merchant independently.

    Can we delete the newer entry after merging it?

    Preserve its purchase reference, inquiry date, source and relevant consent evidence first. We recommend retaining an audit trail so your team can reconstruct the relationship and review any support request.

    Who can we contact about a recurring duplicate issue?

    You can contact our founder, Chad Buchanan, at (248) 686-6955. Have your purchase references and a concise description of the overlap ready so the discussion stays focused.

    Related lead guides