Selling payments infrastructure to a bank runs in seven stages. They are discovery, technical scoping, a pilot, an MOU, commercials, third-party risk and legal review, then go-live in one product line or region. The third-party risk stage usually sets the timeline.
Who from the bank attends each stage, and what ends it?
Each stage brings in a different bank team and ends with a written output. The stages fit payments, card issuing and core add-on vendors.
- Discovery. The head of payments or a payments product owner attends. It ends when the champion confirms the numbers and names the economic buyer.
- Technical scoping. The architecture board and payments engineering design the integration. It ends when the board accepts the design for a sandbox.
- Sandbox, then live pilot. Engineering, payments operations and reconciliation attend. It ends when the champion and operations sign the results.
- MOU or LOI. The economic buyer, the champion and procurement attend. It ends when the economic buyer signs.
Then the deal runs to go-live:
Commercials. The economic buyer, procurement and finance agree price, minimum volume and term.
Legal, risk and compliance. Third-party risk, resilience, security, legal and compliance review you. It ends at the signed contract.
Go-live. The first business line goes live. It ends with a review that names the second slice.
The bank version differs most from an enterprise stablecoin payments deal at stages 2 and 6.
What gives a bank a reason to start a project now?
A dated change to a rail, a scheme or the core system. Banks rarely replace payments infrastructure on product merit alone, so find the change that forces the work.
- ISO 20022. Swift ended the coexistence period for cross-border payment instructions on 22 November 2025 (Swift). A bank that met the date with a conversion layer may still run older formats inside.
- Longer hours. The Federal Reserve plans to run Fedwire 22 hours a day, six days a week, in 2028 or 2029. Batch processes built for a shorter day need rework (Federal Reserve).
- Instant payments. Banks in non-euro EU states must receive instant euro payments by 9 January 2027. They must send them by 9 July 2027 (ECB).
- Core replacement. This is the slowest trigger, because it reopens every payments integration. Ask in discovery if a core change is planned, and when.
The economic buyer is often the business line head who funds the change. The head of payments is often the champion.
What should the pilot prove?
It should prove the numbers the head of payments reports, on the bank's own traffic. Agree the baseline before the sandbox opens. Measure four things:
- Straight-through processing rate: the share of payments that need no manual repair.
- Latency: time from instruction to settlement, at the 95th or 99th percentile.
- Uptime: availability against the contract target.
- Reconciliation breaks: unmatched items per day, and the time to clear them.
Run the sandbox on test messages. Then run a live pilot capped by volume, corridor or client segment. Contracts for critical functions under the Digital Operational Resilience Act (DORA) need "precise quantitative and qualitative performance targets". The pilot metrics become those targets (Article 30).
What goes into the MOU, and why sign one before price?
The non-binding MOU fixes the scope while the pilot result is fresh. It names the signers, success criteria, timeline and economic buyer. Add how the bank expects to classify the service. A critical or important function gets a deeper review at stage 6. Read what goes in an MOU or LOI.
How do commercials usually work with a bank?
Banks compare a price per transaction with a platform fee. Expect three subjects: the price model, any minimum volume or fee, and the term. A long term with no workable exit fails review, so write the exit terms first.
What do third-party risk, legal and compliance check?
They check if the bank can monitor, audit and exit your service safely.
EU banks. DORA has applied since 17 January 2025 (EIOPA). Its Article 30 sets the contract terms (EUR-Lex):
- For every ICT service: data locations, service levels, incident help and termination rights.
- For critical or important functions, add: unrestricted access, inspection and audit rights, and an exit strategy with a mandatory transition period.
Services delivered by people fall under other rules. On 18 September 2026, the EBA published final guidelines on non-ICT third-party risk. The application date was still to be confirmed (Arthur Cox). Split your service into software and people in writing.
US banks. The Federal Reserve, FDIC and OCC issued joint guidance on 6 June 2023 (Federal Reserve). It sets five stages: planning, due diligence and selection, contract negotiation, ongoing monitoring, and termination. Bring a written termination plan to the first security review.
In both regions, the bank asks what happens if your service fails. Answer with your failover design, the pilot recovery time and a manual fallback.
What does go-live in a first slice look like?
Go live in one product line or region that the pilot covered, such as outbound corporate cross-border payments. Review the first full month against the MOU criteria.
Each new slice is a contract change, and it can send you back through stage 6. For timing, read how long it takes to sell to a bank.
To start stage 1 with banks that have a dated reason to change, get five named buyers, free.