Digital Banking Platform RFP: The Requirements Checklist

By Eurisko Team · Last reviewed November 2026

Candidate proposals scored against a requirements checklist

A digital banking platform RFP should do three things: describe the scenarios and priorities you need instead of a wish list of features, ask every vendor for the same evidence in the same format, and state in advance how answers will be scored. This checklist covers what to settle before writing, how to structure the document, the requirements to copy, and the scoring grid.

It is written for banks and fintechs selecting mobile and internet banking software. Adapt the items to your segments and market, delete what you do not need, and mark every line you keep as must have, should have or nice to have before it goes out.

What should you settle before writing the RFP?

Most weak RFPs are written before the bank has agreed with itself. Settle these five points internally first, in writing, with the sponsor’s sign-off.

  • Scope: which channels (mobile app, internet banking, back office portal), which journeys in the first release, and what is explicitly out.
  • Segments: retail, youth, premium, SME or corporate, and whether one platform must serve several of them.
  • Target operating model: who will change journeys, run releases and operate the platform after go-live: your team, the vendor, or both.
  • Budget envelope: an approved range for the build and for the running years after it, so pricing can be judged as total cost of ownership.
  • Decision makers: one accountable sponsor, a named panel across business, technology, security, compliance and procurement, and scoring rules they have all agreed.

How should a digital banking RFP be structured and worded?

Word each requirement so that answers can be compared. A yes or no question gets a yes from every vendor. Ask for evidence instead: “Describe how this works, state whether it is live in production, configurable, on the roadmap or custom, and attach a screenshot, API specification or client reference.” Fix those response codes, cap the answer length, and require a date and a contractual commitment for any roadmap item that is to be scored.

Keep the document short enough for vendors to answer it properly. A workable structure has seven parts:

  • Context: the institution, its segments, the current estate (core, cards, payments, middleware, identity) and the reasons for change.
  • Scope and phasing: first release, later releases, out of scope.
  • Requirements by section, each line with a priority.
  • Scenario scripts that shortlisted vendors will demonstrate.
  • A commercial template: one pricing sheet that every vendor fills in.
  • Contract positions that are not negotiable, such as data residency, audit rights and exit.
  • Timetable, response format and scoring method.

Functional requirements checklist: which journeys to specify

Describe each journey as a scenario with a start, an end and the systems it touches. For each one, ask what is delivered out of the box, what is configured and what must be built.

  • Onboarding: identity capture, eKYC against the national identity scheme, screening, account opening, save and resume, handover to a branch or agent.
  • Accounts: balances, statements, deposits, multiple currencies, joint and minor accounts.
  • Payments and transfers: own account, domestic, instant payment rail, international, bills, standing orders, beneficiaries, limits, and bulk payments for business users.
  • Cards: issuance, activation, PIN, freeze, limits, virtual cards, wallet provisioning, disputes.
  • Lending: eligibility, application, document upload, decision, e-signature, disbursement, repayment.
  • Service requests: cheque books, certificates and complaints, with status tracking.
  • Notifications: push, SMS, email and in-app, with templates, languages and customer preferences.
  • Back office: customer support view, maker-checker approvals, limit and fee configuration, content management, audit trail, reporting.

Non-functional, architecture and integration checklist

These requirements decide how the platform behaves in year three. State your own targets (peak users, response times, availability, recovery times) and ask vendors for measured results from a comparable production client, not design intent.

  • Performance: load test reports at your stated peak, and behaviour when the core is slow or unavailable.
  • Availability: resilience architecture, recovery time and recovery point objectives, releases without downtime.
  • Accessibility: conformance to WCAG 2.2 at Level AA, the W3C Recommendation that covers content on any kind of device, including mobile, with the latest audit report.
  • Arabic and RTL: true right-to-left layouts, not translated strings: mirrored navigation, mixed Arabic and Latin text, numerals and dates. W3C guidance is to declare right-to-left direction on the document itself.
  • Localisation: languages, currencies, formats and regulatory texts changed by configuration.
  • APIs: documented, versioned APIs for every function the channels use, with specifications you can inspect.
  • Core independence: integration through an adapter or your middleware, with evidence of running on more than one core.
  • Events: real-time event streams for analytics, fraud systems and notifications.
  • Deployment and data residency: on-premises, private cloud or public cloud options; where data, keys, logs and backups sit; who can access them.

Security and compliance checklist

Name the standards, then ask for the evidence each one produces. What a vendor holds as a company and what its product is tested against are different things, so ask for both separately.

  • Mobile apps: verification against OWASP MASVS, OWASP’s security and privacy standard for mobile apps, whose control groups cover storage, cryptography, authentication and authorisation, network communication, platform interaction, code quality, resilience and privacy. Ask for the latest independent test report.
  • APIs: testing against the OWASP API Security Top 10, a list that opens with broken object level authorisation and broken authentication.
  • Information security management: ISO/IEC 27001, which defines the requirements an information security management system must meet. Ask for the certificate, its scope statement and the certification body, or a dated plan if certification is in progress.
  • Cards: PCI DSS applies to entities that store, process or transmit cardholder data or sensitive authentication data. Where cards are in scope, ask whether the platform touches that data and who carries which responsibility.
  • Regulator: the cyber security framework of your market’s regulator. In Saudi Arabia, for example, SAMA’s Cyber Security Framework has a third party domain covering contract and vendor management, outsourcing and cloud computing. Ask for a control-by-control mapping.
  • Assurance: penetration test summaries, time taken to fix vulnerabilities, secure development practices, and audit rights for you and your regulator.

Delivery, support and exit checklist

The contract outlives the project team. Ask these questions before you shortlist, because the answers are hard to change afterwards.

  • Team: named roles, CVs, location, share of subcontractors, and who stays after go-live.
  • Methodology: release plan, your team’s role, test strategy, staged go-live.
  • SLAs: severity definitions, response and resolution times, service credits, support hours in your time zone.
  • Releases: product release frequency, upgrade effort, and how long older versions are supported.
  • Source code and IP: who owns configurations, journeys and custom code, and the escrow terms.
  • Exit and transition: data export formats, transition assistance, and fees on termination.

How do you score responses, the demo and the proof of concept?

Publish the weights before responses arrive, and score evidence, not claims. The weights in the table are a rule of thumb to start from, not data: shift them to match your priorities, and treat must haves as pass or fail before weighting anything.

Run the demo from your scripts. Give every shortlisted vendor the same three or four scenarios, such as onboarding a new customer in Arabic or changing a fee without an app release, and have the same panel score each one. Keep a proof of concept for the one or two risks a demo cannot settle, usually integration with your core, and give it a fixed duration, written success criteria and clear rules on test data.

RFP scoring grid (weights are a rule of thumb)
SectionWeightEvidence to request
Functional journeys25%Scripted demo, live client reference
Non-functional10%Load test and accessibility audit reports
Architecture and integration20%API specifications, sandbox access
Security and compliance15%Certificates, test reports, control mapping
Delivery and support15%Named team, plan, draft SLA, references
Commercials15%Total cost of ownership on your template

Which mistakes make digital banking RFPs fail?

The same few errors account for most selections that have to be rerun or that end in a contract dispute.

  • Feature lists with no priorities: when every line counts the same, the vendor that ticks the most boxes wins, not the best fit.
  • No scenario scripts: each vendor demonstrates its best screens and nothing can be compared.
  • Price scored without total cost of ownership: a low licence fee can hide integration, change request, hosting and upgrade costs.
  • Yes or no questions: they invite optimistic answers that nobody can check.
  • Security, data residency and exit left to the contract stage, when the bank’s leverage has gone.

How Eurisko fits

Eurisko has been delivering banking software since 2009, with a team of 200+ engineers. Our digital banking platform, Eurisko DXP, runs in front of any core, deploys in your own data centre or private cloud, treats true right-to-left Arabic and WCAG 2.1 AA accessibility as part of the product, and is aligned with OWASP MASVS. We are glad to be scored against this checklist and to run a demo from your scripts.

One honest limit: Eurisko DXP is not a core banking system, and our ISO/IEC 27001 certification is in progress, not complete. If your RFP needs a ledger replacement, or makes a certificate a pass or fail gate today, we are not the right choice yet.

FAQ

Frequently asked questions.

What should a digital banking platform RFP include?

Context on the institution and its current systems, scope and phasing, prioritised requirements by section (functional, non-functional, architecture and integration, security and compliance, delivery and support), scenario scripts for the demo, a single commercial template, non-negotiable contract positions, and the timetable and scoring method.

Is a digital banking RFP template enough by itself?

No. A template gives you the sections and typical checklist items, but the value comes from your own priorities and scenarios. Mark each line as must have, should have or nice to have, remove what does not apply, and add the journeys that are specific to your segments and market.

Which security standards should a mobile banking RFP reference?

Commonly OWASP MASVS for the mobile apps, the OWASP API Security Top 10 for APIs, ISO/IEC 27001 for the vendor’s information security management, PCI DSS where cardholder data is in scope, and the cyber security framework of your market’s regulator. For each one, ask for the report, certificate or control mapping, not a statement of compliance.

What is the difference between a scripted demo and a proof of concept?

A scripted demo shows the vendor’s existing product running scenarios you wrote, so every vendor is scored on the same journeys. A proof of concept is a short, time-boxed piece of work in or near your environment that tests a specific risk, most often integration with your core, against success criteria agreed in advance.

How should price be scored in a digital banking RFP?

Score total cost of ownership, not the licence line. Give every vendor the same pricing template covering licence or subscription, implementation, integration, hosting, support, upgrades and change requests over the same number of years, and compare the totals.

Let’s build

Have something ambitious in mind?

Start a project →

Popular searches

Jump to