About half of all community banks in the United States still have no fintech partner. The Conference of State Bank Supervisors (CSBS) asked 330 of them for its 2026 Annual Survey of Community Banks, and 52 per cent reported no relationship with a fintech firm, down from 69 per cent a year earlier. On the other side, the wish to partner is strong and the patience is thin. PYMNTS Intelligence and Velera surveyed 100 fintech executives in April 2026. Of the fintechs already selling to credit unions, 56 per cent named complex procurement as a key obstacle. In 2023 it was 28 per cent.
Fintech conferences sit in exactly that gap. Banks, credit unions, payment firms and startups travel to the same hall for the same reason: to find partners. Many go home with business cards instead.
Picture the head of partnerships at a regional bank on the Monday after your event. Her risk committee meets on Thursday, and it will ask what she brought back. Fourteen friendly conversations are not an answer. A shortlist of three vendors is, if each one comes with a named business owner, a reference bank and the documents her vendor risk team needs.
This guide is for the organiser who wants to send her home with the second result. At a fintech event, a meeting between a bank and a fintech is the first page of a due diligence file, not a networking chat. Plan your meeting programme around that file and it will produce partnerships.
Why a bank cannot say yes at your event
The Monday scene has a regulatory reason. A bank that works with a fintech enters a third-party relationship, and supervisors expect the bank to manage it from the first step.
In the United States, the Federal Reserve, the Federal Deposit Insurance Corporation (FDIC) and the Office of the Comptroller of the Currency (OCC) published joint guidance in June 2023. It describes five stages of such a relationship: planning, due diligence and third-party selection, contract negotiation, ongoing monitoring and termination. It also says that using a third party does not diminish the bank’s own responsibility (Interagency Guidance on Third-Party Relationships: Risk Management, 2023).
In the European Union, the Digital Operational Resilience Act (DORA) has applied since 17 January 2025. It covers, among other things, how financial firms manage risk from technology providers (European Supervisory Authorities). This article is not legal or regulatory advice, and the rules differ by country and by type of institution.
For you as the organiser, the consequence is the same everywhere. Nobody from a bank can agree a partnership at a high table. The most she can do is decide that a fintech is worth opening a file for. That decision is the real product of a bank-fintech meeting, and your programme should make it easy.
A lounge cannot open a file.
Not every bank in the room is looking
If the meeting is the start of a file, the next question is which banks want to start one. The CSBS survey shows how uneven the bank side is.
How US community banks stand on fintech partnerships
Nearly two thirds of the banks in that survey (62.5 per cent) rely on their core service provider and are not looking for fintech partners at all. About one in five has an open search. Community banks are only one part of your audience, but the pattern is familiar from most fintech events: fintechs are many, and banks with a live need are scarce.
So your first job is to find out which banks have a need, and what kind of deal they mean. The word partnership covers very different things.
| Pairing | What the bank wants | Who has to be at the table | What a first meeting should settle |
|---|---|---|---|
| Bank buys a fintech product | A tool for a named problem, such as onboarding or fraud checks | The business owner of the problem, later risk and IT | Is this vendor worth a due diligence file? |
| Bank acts as partner bank | Fintech programmes that operate under its banking licence | Head of the partner programme, compliance | Does the fintech’s model fit the bank’s risk appetite? |
| Bank distributes a fintech service | A new product for its own customers | Product owner, legal | Who owns the customer and the revenue? |
| Bank invests | A stake in the company | Corporate venture team | Does the company fit the investment thesis? |
The last row is an investor meeting. It belongs in your investor programme, which follows different rules, and our guide to deal flow at startup events explains what funds look for there. The first row is a purchasing conversation. That makes the bank a buyer, in the sense our guide to venture clienting uses the word for corporates at startup conferences. Banking adds one thing to that model: a supervisor looking over the buyer’s shoulder.
Collect the due diligence basics before anyone books
Because of that supervisor, the questions a bank will ask are predictable. In August 2021, the same three US agencies published a guide for community banks that are considering a fintech relationship. Its use is voluntary. It sorts the work into six areas. They are business experience and qualifications, financial condition, legal and regulatory compliance, risk management and controls, information security, and operational resilience (Conducting Due Diligence on Financial Technology Companies: A Guide for Community Banks, 2021).
You are not doing the bank’s due diligence, and your terms should say so. But you can turn those areas into a short readiness profile that every fintech completes at registration:
- Reference clients: which regulated institutions already use the product, and in which countries.
- Funding: the last funding round, and whether financial statements are available on request.
- Licences and compliance: which licences or registrations the company holds, or which partner holds them.
- Controls and security: which independent audit or security reports exist, and how old they are.
- Integration: which core banking systems the product already connects to.
The bank side fills in the mirror image, a brief of four lines. What is the problem? Which business unit owns it? Which systems must a solution work with? And how far is the decision, from exploring to budget approved?
Keep both forms short. Our guide to registration questions for matchmaking shows how to tell fields that filter from fields that only tire people.
Two things follow from the profile. A bank can filter by what its vendor risk team will ask anyway. And a fintech without a single reference at a regulated institution no longer takes six slots from a bank that could not onboard it this year.
Schedule two meetings, not one
With briefs and profiles in place, the format decides the rest. Meeting-led fintech events have shown that volume works. Fintech Meetup, a US event built around pre-scheduled meetings, reports more than 5,000 attendees, over 700 financial institutions and more than 50,000 double opt-in, one-to-one meetings. Its first European edition, in Lisbon in October 2026, used 15-minute slots (organiser’s figures, fintechmeetup.com, accessed November 2026).
Fifteen minutes is enough to screen a vendor. It is rarely enough to open a file, because the person who owns the problem and the person who owns the risk seldom sit at the same table. The practical answer is a plan in two steps.
One meeting screens. The second one decides.
A two-step meeting plan for banks and fintechs
- 8 weeks Collect bank briefs Each bank names the problem, the business owner and how far its decision is.
- 6 weeks Publish fintech profiles Fintechs complete the readiness profile. Incomplete profiles are not shown to banks.
- 4 weeks Open meeting requests Both sides send requests. A meeting exists only when both have accepted it.
- 2 weeks Fix the calendar First meetings of 15 to 20 minutes go into shared free slots, each with a table.
- Event day Hold first meetings The business owner screens. Afterwards each side marks whether it wants a second conversation.
- Day 1 or 2 Run second meetings Thirty minutes in a quiet room, with risk, compliance or IT joining on the bank side.
- 30 days Ask what was opened One question to every bank: which fintechs entered your vendor process?
What matters most is the second slot. Hold back a block of rooms on the afternoon of day one or the morning of day two, and release it only to pairs that both asked for more.
A bank’s information security lead will not fly in for a first look. She may well join for thirty minutes, in person or by video, once her colleague has found a vendor worth her time. Slot lengths for other meeting types are compared in our guide to B2B meetings at events.
Tell the fintechs what the second meeting is for. It is not a second pitch. It is the moment to hand over the reference list, name the integration path and agree who sends the non-disclosure agreement (NDA).
Protect the bank side
A plan in two steps only works if the banks stay in it, and they are the side that gets flooded. A bank with a visible brief can receive dozens of requests in a day. Three rules keep the programme usable.
First, cap the requests. Limit how many each bank contact can receive and how many each fintech can send.
Second, let the bank’s choice count first. Sponsors may get earlier access to the request window, but a meeting the bank did not accept is not a meeting.
Third, consider hosting the scarce side. Fintech Meetup, for example, states that qualifying banks and credit unions may receive a complimentary pass. A free ticket or travel support in return for an agreed number of meetings is the hosted buyer model. We explain it in what a hosted buyer programme is and, for technology events, in hosted buyer summits in B2B tech.
One more point matters to this audience in particular. Meeting suggestions can follow visible rules, such as product category, institution size, region and decision stage, or come from a learning model that ranks profiles. A bank, however, will sooner or later ask why a certain vendor appeared on its list. Rules you set yourself let you answer that. A ranking nobody can explain is harder to defend in front of a compliance officer.
The scarce side sets the rules.
What to measure, and when
Even a well-run programme will not show signed partnerships in the first weeks, and the PYMNTS survey gives a hint why. Among the fintechs already selling to credit unions, 54 per cent named slow decision-making as an obstacle and 46 per cent lengthy implementation. That comes on top of the 56 per cent who named procurement (PYMNTS Intelligence and Velera, 2026). Credit unions are not banks, but they buy technology in a similar way.
If you promise sponsors signed deals within a quarter, you are measured against a clock you do not control. Measure the steps you can see instead:
- At the event: second meetings requested, as a share of first meetings held.
- After 30 days: fintechs that entered a bank’s vendor process, for example with an NDA or a due diligence questionnaire.
- After 90 days: pilots or proofs of concept that are being scoped.
- Before the next edition: contracts signed, asked in one short survey of both sides.
Missed meetings belong in the same report. Which of the possible no-show figures to use is the subject of our guide to event meeting no-shows.
Then think back to the head of partnerships. On Thursday she tells her risk committee that three vendors are entering the process, each with a named owner and a reference bank. That sentence is your renewal argument, for her ticket and for every fintech stand in the hall.
Count files opened, not hands shaken.
Solution: Converve runs this kind of programme on a rule-based meeting matrix. You define which groups may meet, for example banks with fintechs but not fintechs with each other. You choose which profile fields from registration filter the suggestions, and you limit how many requests each participant receives. Confirmed meetings are placed in free slots of each personal agenda and get a table. Because every suggestion follows a rule you set, you can explain it to a bank that asks. The details are on the page for B2B matchmaking, and the set-up for founders and investors under startup and investor events.
Conclusion: plan for the file, not the handshake
A fintech event cannot shorten a bank’s vendor process. It can decide how that process starts. Treat every bank-fintech meeting as the first page of a due diligence file. Ask banks for a brief and fintechs for a readiness profile. Schedule a short first meeting, and hold rooms for a second one with risk at the table. Cap the requests, and count the files that were opened afterwards.
The head of partnerships who goes home with three vendors her risk committee can work with will come back. So will the fintechs she met.
If you are planning a fintech event and want to see how briefs, profiles and meeting rules can be set up for it, get in touch with Converve.
Frequently Asked Questions
Why do bank-fintech partnerships take so long after an event?
Because a bank has to manage every fintech as a third-party relationship. Joint guidance by three US banking agencies describes five stages, from planning and due diligence to ongoing monitoring and termination (Interagency Guidance on Third-Party Relationships: Risk Management, 2023). A meeting at an event can only start that process.
Who should a bank send to a fintech event?
Send the person who owns the business problem, not only the innovation team. For a second meeting, someone from risk, compliance or IT should join, in person or by video, because they decide whether the vendor can pass due diligence.
How long should a meeting between a bank and a fintech be?
Plan two lengths. A first meeting of 15 to 20 minutes is enough to screen a vendor. A second meeting of about 30 minutes, held on the same or the next day, gives room for references, integration and next steps.
What should fintechs prepare for meetings with banks?
The basics a bank’s vendor risk team will ask for. A 2021 guide by US banking agencies for community banks names six areas of due diligence, from business experience and financial condition to information security and operational resilience. Reference clients and audit reports save the most time.
How do you measure whether a fintech event led to partnerships?
Measure steps, not signatures. Count second meetings requested at the event, fintechs that entered a bank’s vendor process after 30 days, pilots being scoped after 90 days and contracts signed before the next edition.
