How do you capture leads at a fintech or payments conference?
Scan the badge or card, tag channel versus direct, capture what they process, score intent, and sync to your CRM. Offline and on-device.
The middle clause is what makes a payments floor its own animal. Money20/20 USA 2026 runs October 18-21 at The Venetian Expo in Las Vegas, with more than 380 exhibitors on the show floor and 11,000+ attendees from 85 countries, and a large share of the people walking your booth are not end buyers at all. They are ISOs scoping your line, agents shopping a new residual split, partners deciding whether to put you in front of their book. This piece is for the field or event marketer at an ISO, MSP, payfac, processor, or banking-fintech vendor working that floor, or the MidWest Acquirers Association (MWAA), or MoneyLIVE North America. For the generic capture flow, the event lead capture pillar covers it. This is the payments-specific layer on top.
What makes Money20/20 or MWAA different from a generic trade show?
A channel-heavy floor where much of your traffic is partners not buyers, long compliance-aware cycles, and a crowd that asks where the data goes.
Start with the motion. Payments is built on partnerships. The acquiring stack runs through ISOs, agents, referral banks, ISVs, and payfacs, and a show like MWAA exists largely so those parties can find each other. So a booth at a payments conference produces partnership conversations as often as direct leads, and treating every scan as a prospect for your closers misreads the room badly. The relationship type is the first thing you have to capture, before the email.
Then the deal shape. A payments deal is rarely one signature. Switching processors or signing a new payfac drags in finance, the people who own the current integration, a risk or compliance reviewer worried about PCI and underwriting, and whoever owns the merchant relationship. The person at your booth is a champion or a scout, not the committee. So the asset you capture is not the email. It is the context: what they process, who they process with today, monthly volume, and the compliance or cost driver forcing the conversation. A thin lead record dies in that nurture. A rich one survives it.
Why does offline capture and clean data handling matter at a payments event?
The hall RF dies under load, and a payments buyer wants to know where captured data sits. Capture on the device, sync over a connection you control.
This cuts two ways at a payments show. The first is plain reliability. A hall packed with tens of thousands of radios and dense metal is a bad place to depend on a live connection. A scanner that confirms each capture against a server will spin, time out, or quietly drop leads, and your staff will not catch it mid-conversation. Offline-first capture writes the lead to the device and syncs later.
The second is specific to who you sell to. Payments people live inside PCI scope, underwriting, and data-handling reviews for a living. They notice how your booth treats data, and a buyer whose whole job is controlling where cardholder-adjacent information flows will clock a sketchy capture app the same way they would a sloppy vendor. So capturing on-device first, then syncing later over a connection you control into the CRM your team already vetted, does double duty: it protects the lead from the dead RF and it matches a room full of people who audit data flows for a living. The universal badge scanner explainer covers the offline mechanics, and the phone badge scanning security breakdown walks the data path a payments prospect will want to see before they trust your booth with their card.
How do you handle the long, multi-stakeholder payments sales cycle?
Note the processor, the volume, the PCI and underwriting driver, and who signs. Score it, sync with attribution, and it survives months of nurture.
The conversation note is the highest-value object you capture at a payments show. "Processing about $4M a month through a legacy acquirer, frustrated with chargeback handling, evaluating us because their PCI audit flagged the current setup, ops lead wants a pilot" is worth ten times the raw badge. That note is what your sales team works for the next two or three quarters, and it has to be captured as voice or text at the point of contact, with tags, while the detail is fresh. A name typed into a form back at the hotel loses all of it.
Capture the committee too. The ops lead kicking your tires can champion you, but finance signs, the integration owner gates the technical work, and a risk or compliance reviewer may sit in between on anything touching cardholder data. So the note should record who else approves, the current processor or partner, the volume band, and what is actually forcing the project. Then score it. AI lead scoring that reads the notes and interaction data sorts the live pilot candidate from the agent collecting brochures, so your reps work the right leads first. Because the cycle is long, the record has to survive months in the CRM with the source intact. The event leads to CRM hub covers the field-mapping that keeps the attribution clean so the deal that closes next year still traces back to Money20/20.
How do you route leads when you sell through ISOs, agents, and partners?
Tag partner versus direct versus channel at capture, then route by type and territory so an ISO inquiry never lands in a direct closer's queue.
This is the wrinkle that separates a payments floor from a normal trade show. A real share of your booth traffic is channel: an ISO weighing your processing platform, an agent shopping residuals, an ISV looking to embed payments, a referral partner sizing you up. Route every scan into the same direct-sales queue and your closers burn cycles on people who never buy directly, while a genuine partner opportunity gets cold-shouldered by the rep who does not own partnerships.
So tag the relationship at the moment of capture: direct merchant or buyer, ISO, agent, ISV, referral partner, distributor. Then route by both type and territory. Team collaboration across booth staff shares, dedups, and routes the lead in real time, so the partner inquiry reaches your channel manager and the direct deal reaches the right account owner. At a busy payments booth you have several people scanning at once, and two of them will catch the same visitor. Dedup at the team level keeps that from turning into two competing follow-ups to one partner who now thinks you are disorganized. The trade show follow-up guide covers the cadence once the lead is routed to the right owner.
What badge formats do fintech and payments conferences use?
Money20/20 prints a unique barcode tied to email and the app. Others vary. The honest move is to OCR the badge or card and enrich, offline.
Formats are inconsistent across the payments circuit. Money20/20 issues a unique barcode on the badge, linked to the attendee's email and the show app. Smaller acquiring shows like MWAA and MoneyLIVE run their own setups, and you should not assume any two work the same way. The thing that stays constant is what the code actually holds: on most major shows the badge barcode is an opaque registration ID, like a license plate that means nothing without the organizer's database, which is exactly why the organizer can rent you a scanner that resolves it only at that show.
So the honest mechanism for a standalone app is to OCR the printed badge face, business cards, and handwritten notes, then enrich from named data partners, and to read NFC or vCard payloads where a badge actually carries them. A standalone tool does not decode the organizer's opaque ID. It reads the contact off the badge and the card, and it works offline. The universal badge scanner approach does that in one motion across whatever format a given show throws at you, which matters on a circuit where the format changes every event.
What does a fintech or payments trade-show lead actually cost?
First Page Sage puts fintech blended CPL near $452 and financial services near $653. Trade shows convert near 24% to MQL. Too pricey to drop a scan.
Run the math, because it reframes the tooling decision. Per First Page Sage's cost-per-lead report, fintech's blended cost per lead sits around $452 (roughly $490 paid, $413 organic) and financial services around $653 (roughly $761 paid, $555 organic). These are separate rows. If you sell payments software, fintech is your line. If you are a bank or a regulated financial-services vendor, the $653 figure fits you better. Note that this is the full-funnel blended number, paid and organic together, not a Google-Ads cost per click.
From there, First Page Sage's lead-to-MQL channel data shows trade shows converting at about 24%, conferences at 28%, and executive events at 54%, so the format of your event matters as much as the vertical. Its MQL-to-SQL benchmarks put fintech in a contested range: First Page Sage reports about 11% while Data-Mania puts it nearer 19%, so treat it as roughly 11-19%, with financial services around 13%. Close rates run about 14% for fintech and 16% for financial services. Lead-to-MQL for financial services is about 29%; First Page Sage does not publish a fintech-specific figure for that stage, so I will not invent one.
Acquisition cost is heavy too. First Page Sage's fintech CAC report puts the trade-shows channel B2B CAC near $1,390, SMB fintech CAC around $1,450, and payment-processing SMB near $1,467. Stack all of that. You pay real money per lead, only a slice become qualified pipeline, and the all-in cost to land a customer runs well over a thousand dollars. So every lead a cloud-only scanner drops when the hall RF fails, and every lead that sits unsynced and goes cold, is hundreds of dollars of spend and a slice of a multi-year processing relationship walking off the floor. The trade show ROI breakdown puts the rest of that math in one place.
Should you rent the organizer's scanner at a payments conference?
Usually no. Rentals run $400-700 per device per show, your data leaves when the show ends, and you relicense at every event. Bring your own.
The organizer rental is the default trap. Verified 2025-26 lead-retrieval order forms put device rentals at $400-700 per device per show, reaching about $735 onsite at the largest shows, and many organizers now charge as much again for API or CRM-integration access on top. A five-person booth renting handhelds across ten shows a year runs roughly $25,000 to $35,000 in scanner rentals alone, before the integration fees. And you rent the same constraints every time: the data lives in the organizer's system, your access ends when the show closes, and many of these tools assume a live connection that a crowded payments hall will not reliably give you.
You also get organizer lock-in. Every show is a different portal, a different export, a different login, and your event history scatters across vendors instead of compounding in one place. The hidden cost of organizer badge scanners post breaks the full rental bill down. The alternative is to bring one app that works at every show, captures offline, and syncs to your own CRM, with a side-by-side on the standalone options in the alternatives hub.
How does Tendro fit a fintech or payments exhibitor's stack?
Tendro captures any badge offline, takes notes, tags channel versus direct, scores intent, and syncs to destinations you control. I build it.
Disclosure: I build Tendro. Filter accordingly.
Here is the honest fit for a payments exhibitor, mapped to what actually matters on a Money20/20 or MWAA floor. Offline mode handles the dead hall RF and the data-handling question at once: full capture with no internet, stored on-device, synced later over a connection you control into the CRM your team already vetted. The universal scanner reads the badge face, business cards, QR, NFC, and handwritten notes through one OCR-and-enrich pipeline, so a show printing a unique barcode and a show printing something else both work the same way for your staff. Note capture takes voice and text plus tags at the booth, which is where the real value of a payments conversation lives, the processor and the volume and the compliance driver, and AI scoring sorts the live pilots from the brochure collectors.
For the channel problem, the lead record carries a relationship tag, direct or ISO or agent or ISV or referral partner, and team collaboration shares, dedups, and routes across booth staff in real time, so partner and direct inquiries split cleanly to the right owner. Then it syncs to your CRM in under ten seconds across 17 destinations, including Salesforce, HubSpot, Pardot, Marketo, Pipedrive, and Zoho, plus tools like Slack, Airtable, and Webhooks. On the data questions a payments prospect will ask, the connection is a scoped, encrypted, revocable OAuth grant, the data model is multi-tenant and team-scoped, and enrichment runs against named providers (Apollo, Hunter, People Data Labs), all walked through in the phone badge scanning security page.
What Tendro does not do: it is not a badge-printing or registration system, and it does not replace your nurture engine. It is the capture layer between the handshake at the booth and the lead record your sales team works for the next year. If you exhibit on the payments circuit and you are tired of renting a cloud-dependent scanner that drops leads, scatters your history across portals, and asks your prospects to wonder where their data went, that is the gap it fills.