The short answer
When a fintech sells infrastructure to a bank, a sponsor and a dated event open the deal, and reviews can stop it: information security, risk, compliance, legal and procurement, and often the board. A strong demo does not carry it through them.
I work this on a company like Juspay: use sourced research, a buying group draft and selected questions from Helix to prepare for the bank's review. Then run the review work by hand with the champion: get the bank's template, name its review owners, submit the evidence and record their decisions. No bank data moves before approval. The tool outputs below are preparation material, not a bank risk assessment or an approval plan.
Why trust-led deals stall after the demo
At Seclore, where I was Director of Product Marketing from July 2016 to October 2017, we delivered Rs 2.35 Cr TCV in 6 months through account-based marketing, with 225+ sales meetings across Seclore's target accounts. At Happay, where I was Vice President Marketing from November 2019 to January 2022, enterprise deal size rose 178%. CMO Asia named me B2B Marketer of the Year 2020, Fintech. The steps below are my own method, worked on public and illustrative inputs, not a client result.
Take a small public test of a fintech product. Three days after the PhonePe and OpenAI deal was announced, "I paid my gas bill on PhonePe" and asked the new ChatGPT strip "Can you analyse my last 3 months' expenses?" The reply: "I cannot access your PhonePe account or any of your personal financial data." (LinkedIn, 19 Nov 2025.) That was a consumer app, and I went on to read the deal through EPIC as an ecosystem play. I use it for one point: test what a product does with the data, rather than read the announcement. My own stated view: "I'm just not comfortable with AI mining my health data, bank account and PII data." (Interview, 5 Oct 2026.)
A bank reviewer has a text behind that caution. RBI's outsourcing directions for commercial banks, 28 November 2025, leave "ultimate responsibility" with the Board and senior management, and senior management evaluates materiality under a framework the Board approves. The contract must cover audit rights, RBI's inspection of the provider and its sub-contractors, prior consent to subcontractors and data stored "only in India (as applicable)". The policy needs an exit strategy. In the EU, DORA has applied since 17 January 2025. My reading, checked 1 November 2026, not legal advice.
With no sponsor and no dated event, such as a contract ending or a regulator's finding, no review opens. Once one does, plan for a reviewer you never met asking for evidence your champion cannot produce: where the data sits, what happens to live payments in an outage, whether the arrangement is material. Plan in months, not weeks, and ask each bank.
If you sell cybersecurity to banks, the positioning guide covers the CISO message. The documents here still apply, but the seats move: there the CISO is often the buyer, not the reviewer.
The method, and where free tools help
The first three moves prepare a conversation and an evidence pack; the fourth is a manual review tracker. Start with a sourced account brief, then use the buyer group analyzer to list seats to verify, the trap setter to draft discovery questions and the champion kit to identify evidence to request. Read those drafts before using them: none of the quoted runs establishes this bank's owners, approvals or risk decision. Research helps you ask; the champion and review owners supply the bank process.
Use the sector notes as preparation, then ask the bank
In the recorded Revenue Enablement runs I set your_sector to fintech; the buyer group analyzer inferred "fintech, payments and banking APIs" from the inputs. The sector notes said "The CTO or Head of Payments signs; engineering leads evaluate the interfaces and champion". That does not establish who signs for this bank, and the analyzer suggested a Chief Financial Officer I had not named. I use the resulting seats as questions for the champion, then write the confirmed roles in a separate bank review tracker.
Worked example: a company like Juspay selling to a mid-sized private bank
About this example. Juspay is a real company. Juspay has not reviewed this guide. Facts about Juspay come from public sources, linked alongside with the date I checked them. The deal is an exercise: the bank, its stack, budget and contract dates, the value points, the strengths as worded and every number marked illustrative are inputs I chose. They are not Juspay's data, claims or customers, and the tool outputs are exercise results, not Juspay's real strategy. The "I" in the steps is an exercise role, not a seller at Juspay.
The public facts I use: in January 2026 Juspay raised $50 million in a Series D follow-on at a $1.2 billion valuation. It says it works with more than 500 enterprises and banks (company-reported). Its banks page describes a "cloud-native, modular platform" for merchant acquiring, "deployable under your bank's brand", and does not say where data sits. Its site lists PCI DSS 4.0.1, ISO 27001:2022 and SOC 2 Type 2, and lists Payment Aggregator (HyperPG) under Compliances. The buyer is "a mid-sized private bank with a merchant acquiring business", a type, not a named bank, and the $500,000 a year deal is illustrative.
Step 1. Name the event and verify the buying group
Before any tool, three questions for the champion. What forces a decision, and by when? Here, illustrative: the support contract for the current stack ends in 9 months. Whose budget pays? Here, illustrative: the payments business. Can I see the bank's vendor onboarding steps or template? If the champion cannot get them, that is your first finding: the sponsor may be too junior.
Input to the buyer group analyzer: product "cloud-native merchant acquiring platform for banks"; company Juspay; "$500,000 a year (illustrative)"; "mid-sized private banks in India with a merchant acquiring business"; champion Head of Merchant Acquiring; stakeholders Chief Digital Officer, CIO, CISO, Chief Risk Officer, Head of Procurement.
The useful output here is a list of seats to ask about, including a suggested business owner beyond my champion. It is not a confirmed buying group: every seat is marked a hypothesis. It left my Chief Digital Officer as "Authority unconfirmed" and put "Chief Financial Officer (usual in fintech, payments and banking APIs; none of your stakeholders fits this role)" in the economic buyer seat, a title I never gave it. It does now place the CIO as the technical evaluator, and the same "none of your stakeholders fits this role" wording still sits on the user seat. I then reran it with confirmed_budget_owner set to Head of Payments Business. That title took the economic buyer seat ("Confirmed in your answer: Head of Payments Business"), the influence map and the economic buyer questions changed with it, and the first open item moved from budget authority to "Internal advocate". So the budget owner is an answer I get from the champion before I rely on that seat. My next question to the champion is whose budget pays and who can sign, then who owns technical evaluation. I write their answers beside the draft and leave unconfirmed seats open; a title match is not authority.
The 6 November run has India in the company size, and this time the tool adds an India section. Its first line asks who owns the budget and who must approve, and it still leaves the Chief Digital Officer's authority unconfirmed. For the CIO it asks "Who owns technical acceptance, and where are their agreed criteria recorded?"; put that question to the champion and keep the budget and technical decisions separate. The India section opens with "Who owns the budget, security review, data permissions and final purchase approval for this Indian buyer?" and then lists Reserve Bank of India checks, each with a scope note and a source. It is a draft for owner review, so I check each rule against the bank myself before I rely on it.
Now a question from the public research that this tool run did not raise. RBI's due diligence list for IT outsourcing includes "conflict of interest, if any", and this vendor lists an aggregator licence. A bank may ask whether its platform vendor also serves merchants directly. The issue is public. Inc42 reported in March 2025 that several fintech platforms had moved to discontinue integrations with Juspay, and that the launch of its payment aggregator service "seems to have sparked this exodus". Juspay calls reports of gateways ending partnerships "factually incorrect", says it is a technology service provider, and says "we have no interest in growing our PA business". MediaNama reported that it denies any conflict. Those reports concern gateways, not banks; the step to a bank is my inference. So the fair ask is what the bank needs in writing: how the two businesses are separated, who sees its merchant data, whether those merchants can be solicited, and who controls routing.
One open point. RBI's IT chapter leaves RBI-authorised payment system operators out of its definition of service provider, with a qualifying Explanation. Whether that touches this vendor is for the bank's compliance team. Raise it; do not argue it.
My own preparation checklist for the champion to confirm, replacing the single CISO reviewer row:
Ask the champion which people in the CISO's team, vendor risk and compliance review this purchase, and when the Chief Risk Officer is involved. Ask what each needs on third-party risk, data location, outages and vendor conflict. Prepare the completed bank questionnaire, certificates, data location statement, subprocessor list, uptime record and continuity plan, proposed audit and inspection rights, exit plan, financial statements, conflict statement and rules mapping. Confirm the submission route before sending the pack, then offer your CISO to theirs.
My suggested gate: no formal proposal until the review owners have named their steps and timing, and the vendor risk lead has your pack. A Chief Risk Officer may not meet a vendor this early, so do not make that the gate.
Step 2. Draft questions before any formal process opens
This step has a limit. A regulated buyer must defend its choice, so criteria that trace to one vendor put your champion at risk. Once an RFP is open, ask what the bank's rules allow and shape nothing. Check the real alternative too. If the bank is renewing what it has, your case is the cost of staying. If it buys from a processor its reviewers already approved, that processor is the rival.
Input to the competitive trap setter: competitor "a legacy on-premise acquiring stack", a category; your_solution "Juspay, a cloud-native merchant acquiring platform for banks in India"; early stage; all trap types; evaluator CIO; strengths "Modular platform deployable under the bank's own brand", "One integration for many payment methods and PSPs", "Adaptive 3DS and network tokenisation built in"; weaknesses "New payment methods take months to add", "Reconciliation runs as overnight batches"; priorities "merchant onboarding in days instead of weeks; fewer failed payments for merchants; passes the bank's outsourcing and data localisation review"; your_sector fintech. The weaknesses and priorities are illustrative.
Two questions came back ready for discovery: "Which systems must this work with, and who owns each one?" and "What does your security review need and how long does it take?" Ask those before drafting a proposal; put the answers into the evidence request list and the bank's review tracker. The criteria were less useful: they repeated my three strengths, not independent requirements from the bank. By hand, turn the business priorities into outcomes to agree with the bank: a new merchant live in days on its onboarding rules, and a new payment method added without a core change. These are proposed outcomes for this exercise, not measured results or agreed pass marks. The tool says "No terms of your own were given", so prepare audit rights, data location, service levels with remedies and exit support for the bank to review. I changed one input, the stage from early to finalist. Only the stage text and the stage tactics moved. The early text says "Put the 3 things you can show live on the buyer's criteria list before the shortlist is made, and offer to help the CIO structure the evaluation." The finalist text says "Reduce the buyer's risk by showing your strongest criterion on their own case, give the CIO access to your own executives, and close with the terms you can put in the contract." The questions and the three criteria were identical, so the stage does not change what I take from this run. With India in the description the tool added a region section. I use one line of it as a question for the bank: "Ask the bank to confirm whether the proposed IT service is material outsourcing and which risk review and approval evidence it requires."
Discard the instruction "ask to see it live on the buyer's own data": in this run it appeared before any bank review approval. I also discard the offer to help the CIO structure the evaluation, which sits in the early stage text, and the vendor strengths presented as requirements. My working rule is no bank data before the bank clears its use. Before that, propose synthetic test data and ask the CISO's team to agree the environment; masking bank data is not permission to use it. The reader agrees the test conditions with the bank by hand, outside the tool.
Step 3. Prepare evidence requests and a champion note
Use this step to prepare for review, not to write the bank's assessment. Get its questions and template through the champion, then map your evidence to them. The champion's short note states what is being proposed, why now and who owns the business case. The bank decides materiality and the approval path in step 4.
I tried the champion kit with asset_type risk_assessment and the inputs alongside, with India added to your_solution. I would not send the assessment it produced; I would extract evidence requests for my preparation list. Its opening makes the boundary plain: "Likelihood and impact are not rated here: set them from our own assessment". The outage request is usable: "the uptime record of Juspay for the last twelve months, the service level it will commit to in writing and what it pays if that level is missed". Put those three items on the vendor evidence list, with a person responsible for obtaining each document. Juspay's banks page claims 99.999% uptime (company-reported); that claim is not the requested record.
The kit went wrong when it concluded "I request validation of the business case for Juspay, on the condition that the pilot settles the points above". I named no pilot, and validating a business case is not the purpose of this preparation note. The earlier run asked the vendor for "a yes or no" on materiality. This one no longer does: the materiality answer says "Treat this as the buyer's classification, not a sales point: ask the buyer's risk team whether the arrangement counts as material, and which approvals and evidence follow." I keep that line. The 6 November run added a block that says "Decision owner and authority for this purchase: Unknown; identify who can authorize it." That is honest, but it sits beside the pilot condition, so the kit asks for validation of the business case while saying the decision owner is unknown. I changed one input, the target stakeholder from Head of Vendor Risk to Head of Procurement. This time the reader view changed with it. The concerns moved from outsourcing and outages to price, exit and paperwork, and the next step became "Ask Head of Procurement for the vendor onboarding checklist and the list of due diligence documents this week". That part is usable for a procurement reader, with light edits to the dates and the price comparison. The risks, the conclusion and the pilot condition did not change with the stakeholder, so my objection to the conclusion stands. Delete the conclusion and the pilot condition: ask the vendor for scope, data flows and a location statement; leave the materiality assessment to the bank. My hand-written closing for this illustrative champion note is: "The current support contract ends in nine months. Please confirm the business owner and the route for submitting the vendor evidence pack. The bank review, purchase decision and any test using bank data remain open."
This is the point where I would want a second pair of eyes: the trust pack or review message stalls before the formal bank review. Bring me your review map, evidence gaps and champion note, and we will work it through in 45 minutes.
Step 4. Run the bank review tracker by hand
Template and free tool: Mutual action plan template for B2B deals
I also tried the mutual action plan generator; I do not use that output for this review step. For traceability, the inputs were all illustrative: deal "Juspay at a bank in India"; target close 2027-04-30; stage discovery; champion Head of Merchant Acquiring; economic buyer "Head of the payments business"; evaluator CIO; your_solution as above; your_sector fintech. I supplied vendor risk questionnaire, information security review, the bank's materiality assessment, compliance review, test on masked data, legal and contract terms, procurement, and board or committee approval as the process steps.
What came back explains the manual choice: "Run the test on live volume" appeared before the vendor risk questionnaire, and the CIO was assigned both the materiality assessment and the compliance review. In this bank exercise those are unconfirmed owners and an unsafe test sequence; the supplied process steps did not make the generated plan reliable. I changed one input, the target close from 2027-04-30 to 2027-01-29. The plan shrank from 125 to 60 working days and every date moved. This time the schedule check reacted too. With the April date it said "Verdict: the date holds only if steps run in parallel". With the January date it said "Verdict: the date is at risk", listed five steps that no longer fit, and added "so the plan is short by 4 weeks". I keep that warning. The faults stayed, though: "Run the test on live volume" still came before the vendor risk questionnaire, and the CIO still owned the questionnaire, security, materiality, compliance and masked-data steps. The run also ends with a question about which region applies, although the deal name already says India. The tool did not read the country from the deal name, so no India section came back. Start a blank tracker with the champion and copy the bank's own review steps into it, in the order its review owners confirm. For each step, record the bank owner, the vendor document and version requested, who will supply it, any unresolved question, the agreed date and the written decision. Keep missing owners, dates and decisions marked open; a submitted document is not an approval. The bank's risk and compliance owners confirm who assesses materiality and which approvals are required; the reader records those answers rather than assigning them from a job title. Confirm dependencies before scheduling tests or cut-over, and keep bank data out of any test until the bank has approved that use. Use the table alongside as my illustrative list of questions to cover, replacing its months and roles with the bank's confirmed process.
Now the sum on these illustrative dates. Counting from November 2026, signature at the end of month 6 leaves three months before support ends in month 9. In my judgment that covers one merchant segment at best, so ask now what a support extension costs, and put that in the case. Internal audit may ask for the file later, so keep every answer in one place.
What to do this week
- For each live deal, name the event that forces a decision, its date, and who holds the budget.
- Use the buying group draft to ask the champion who owns each decision, then get the bank's vendor onboarding steps.
- List the documents every review will ask for, and close the gaps, a conflict statement included.
- Before any formal process opens, rewrite your criteria as the bank's outcomes and agree a test that moves no bank data.
- Build the review tracker by hand with bank owners, evidence, open questions, dates and decisions, then ask what a support extension costs.
Five mistakes in trust-led enterprise deals
- Meeting the reviewer last, or cold. Have the champion bring you in early, then put your CISO with theirs.
- Taking the sector notes as the bank's view. Add its rules and its template.
- Asking for bank data before the review.
- Setting your strengths as the criteria, or shaping criteria once an RFP is open.
- Writing the bank's risk view for it. Supply the evidence; leave materiality and the recommendation to the bank.
Questions and answers
Who reviews a payments infrastructure purchase at a bank?
In my suggested reading, the business head who owns the line champions it and the CIO evaluates it. The CISO's team, vendor risk, compliance, legal and procurement review it, and the Board-approved framework decides how high it goes. Ask your champion for the bank's own steps.
What should a fintech vendor prepare before a bank's risk review?
The bank's questionnaire completed, your certifications, data location and subprocessors, uptime record, audit and inspection rights, an exit plan, financial statements and a statement of any conflict of interest.
Can a vendor test on a bank's transaction data before the review?
My working rule is no bank data before the bank's own reviews clear that use. Until then, propose synthetic test data in an environment its security team agrees; masking is not approval.
What fintech marketing recognition has Shashwat Ghosh received?
Shashwat Ghosh was named B2B Marketer of the Year 2020, Fintech, by CMO Asia, and is one of CMO Asia's Most Admired Marketing Leaders 2025.
Run these tools free with your team, or bring Shashwat in
- Run it with your team
Use ICP Intelligence
Free, with no sign-in, for everyone on your team. Run it in your browser, or connect it to Claude, ChatGPT, Cursor, VS Code and Windsurf.
- Bring Shashwat in
Fractional CMO
When you want a senior operator to run this with your team, own the marketing and demand generation plan and pressure-test your numbers, start with a 45-minute call.
Related guides
- One B2B Deal From MEDDPICC Discovery to a CFO-Ready ROI Case and a Dated Close Plan
- Account-Based Plays Without Burning SDR Hours: Account Research, an Account Plan, Category Traps, Lookalikes and Roundtable Follow-Up
- When High Adoption Hides Churn Risk: A GUARD Health Check, Save Plan, Expansion Case and QBR on One Book of Accounts
- All 30 guides
About the author. Shashwat Ghosh is Co-Founder and Fractional CMO of Helix GTM Consulting, the brand he has worked under in Bengaluru since 2022. He has 24+ years of B2B marketing, 10+ years fractional and 37+ client engagements. He created the EPIC, IMPACT, CRAFT and GUARD frameworks and the Hub-Spoke Brand Messaging Methodology. More about Shashwat. How these guides are made.
Last updated 6 November 2026
Choose your app
Connectors work in Claude, ChatGPT, Cursor, VS Code and Windsurf. The Helix GTM Suite skills package supports Claude Code, ChatGPT, Gemini CLI, Antigravity, Cursor and VS Code, and is available through skills.sh. Individual plugin installation steps below or on their pages remain specific to that plugin.
Connector setup guides · Skills package setup guide · Find the skills on skills.sh