Crypto exchange software requirements: a checklist for your RFP
What to put in a crypto exchange software RFP: deployment, keys, liquidity, custody, console, apps, evidence and exit, each with the proof to ask vendors for.
BitPolaris Engineering
English original
An RFP for crypto exchange software usually arrives as a feature list: matching engine, wallets, KYC, mobile apps, admin panel. Many vendors can tick the same high-level boxes, and the real differences only surface after signature: who holds the keys, where the liquidity comes from, and what your team operates during an incident. This crypto exchange software requirements checklist is written for RFP scoring and vendor due diligence by a licensed operator: each requirement comes with the evidence to ask for. It is written from the vendor side, so where BitPolaris has a published answer it is linked; demand the same level of detail from everyone on your shortlist.
How to use it
- Put each requirement in the RFP with its evidence column. A demo recording, a document or a contract clause counts; a slide does not.
- Weight the first two groups highest. Deployment and key control decide whether the platform can be evidenced under your licence at all.
- Ask every vendor for the same three artefacts: a year-one price with modules itemised (licence, modules, hosting, support and third-party costs for the first twelve months), a live walkthrough of the operations console, and the technical-file sections and evidence the vendor can provide for your application. What regulators ask for lists those sections.
1. Deployment and key-control requirements
| Requirement | Evidence to ask for |
|---|---|
| Runs on infrastructure we control (own cloud account or bare metal), with the option of a vendor-hosted instance for a first phase | Deployment page or contract schedule naming the models and what changes between them |
| Private keys generated and held inside our perimeter; vendor has no standing access after installation | Key-ceremony procedure; access model (session credentials we issue, logging, revocation) |
| Data residency per our licence (EU, GCC, Türkiye, other) for production data, backups, logs and support access; sub-processors listed | Reference installations by region; backup-location and sub-processor clauses |
| Security practice: penetration test and remediation, dependency policy, privileged-access review | Latest pen-test summary; remediation targets; access-review procedure |
| High availability and disaster recovery: recovery time and point objectives, backup encryption, restore tests | DR plan; last restore-test record |
| Updates delivered as releases we approve; staging environment and rollback plan | Release-notes sample; update-window clause |
| Licence survives if support lapses; full data export at exit; source access or escrow | Licence terms; export format; escrow or source-code option |
BitPolaris evidence: three models side by side on the deployment page (self-hosted, source code, hosted cloud); keys in your perimeter on self-hosted and source code; no standing access; perpetual licence; 90 days of onboarding with the source-code licence. Self-hosted crypto exchange software describes what your team runs.
2. Matching and market requirements
| Requirement | Evidence to ask for |
|---|---|
| Spot matching with limit, market and stop-limit orders, self-trade prevention, deterministic order of execution | Engine specification; implementation language and transport; test coverage |
| Market configuration by our operators: tick size, minimums, fees per market, maker-taker schedule, maintenance mode | Live demonstration in the console, not a screenshot |
| Market integrity controls: price bands, circuit breakers, cancel-on-disconnect, kill switch, surveillance exports | Configuration screens; an incident example |
| Market data over WebSocket and a documented REST API with key scopes, IP allow-lists, sub-accounts and rate limits | API documentation URL; sample client |
| Throughput and latency measured on a stated configuration | Load-test report naming hardware, order mix, sustained orders per second and p50/p95/p99 latency |
BitPolaris evidence: matching engine in Go with gRPC and AMQP transport; limit, market and stop-limit orders; self-trade prevention; market and fee configuration in the 53-screen console; API and WebSocket feeds on the exchange page and in the docs.
3. Liquidity requirements
| Requirement | Evidence to ask for |
|---|---|
| A stated liquidity model: own market making, external liquidity providers, a shared network, or mirroring with hedging | Written description of who funds inventory, who carries risk between fill and hedge, settlement with the venue, and what the vendor earns on flow |
| Our own market makers can connect through the API | API scopes for market-making accounts; rate limits |
| Reference price protection: minimum source count, deviation brakes, stale-price handling | Configuration screens; incident examples |
| Working-capital requirement for 50 and 100 markets, and the outage playbook when a venue is down | A worked estimate, not “liquidity included”; the playbook |
BitPolaris evidence: the Mirror engine quotes order books on 97 markets today from reference venues and hedges fills there, subject to venue availability, balances and risk limits, so you hold working balances on the hedging venue rather than inventory; price guards described in when three price sources are not enough; how mirroring works in exchange liquidity without parking capital.
4. Custody and chain requirements
| Requirement | Evidence to ask for |
|---|---|
| Hot, warm and cold tiers with policy-driven moves; M-of-N approvals; whitelists; delays; mandatory 2FA for approvers | Policy-engine screens; approval-log sample |
| Automated ledger-versus-chain reconciliation on a schedule, with alerts on mismatch | Reconciliation report sample; alert routing |
| Supported chains and assets, with RPC failover and the cost of each chain’s operations (TRON energy, Solana expiry, XRP tags) | Chain list; failover design; a stuck-withdrawal runbook |
| Asset listing and delisting policy, token due diligence, fork and airdrop handling | Listing policy; a recent listing file |
| Address and sanctions screening on deposits and withdrawals: when checks run, hold and block rules, who contracts the provider, alert workflow | Integration list; screening workflow demo; audit export |
BitPolaris evidence: nine chains (BTC, ETH, BSC, TRON, XRP, SOL, DOGE, LTC, AVAX C-Chain) with RPC pools and failover; the custody block is self-hosted only, with vault tiers, M-of-N approvals, whitelists and delays, automated ledger-versus-chain reconciliation around the clock and mandatory 2FA; listing practice in how a crypto exchange lists a token; operational detail in why crypto withdrawals get stuck and MPC vs multisig.
5. Operations console requirements
| Requirement | Evidence to ask for |
|---|---|
| KYC queue with tiers, provider integration and manual review; account actions with reasons and an audit log | Live walkthrough; audit-log export |
| Hooks for transaction monitoring, sanctions re-screening, case notes and report export | Integration list; case-handling demo |
| Withdrawal approval queue with limits per role; four-eyes on sensitive changes | Role matrix; approval demo |
| Support tooling: user search, balance history, ticket or chat integration, email templates in our languages | Template list; language list |
| Alerting with hysteresis, so repeated threshold crossings do not create alert storms, routed to the channels our team uses | Alert catalogue; an example of a closed incident |
BitPolaris evidence: 53 screens covering KYC queues, approvals, market and fee configuration, the Mirror console, Earn, live support and 60 email templates; identity service with KYC tiers and a Sumsub integration; alert design in 607 alert emails. Ask to see it running; the demo page has a console tour.
6. Apps and client requirements
| Requirement | Evidence to ask for |
|---|---|
| Web terminal with a simple buy-and-sell view and a full order-book view; our languages; right-to-left where needed | Live site under a demo brand |
| Native iOS and Android apps published under our developer accounts, with store review handled | Existing store listings of the vendor’s own or client apps; submission process |
| App maintenance: OS and SDK update cadence, store-rejection handling, crash reporting, release ownership | Release history; maintenance clause |
| Branding and configuration without code changes: logo, colours, domains, legal texts | Branding checklist |
BitPolaris evidence: React web terminal with Easy and Pro modes in Turkish, English and Polish; React Native apps for iOS and Android published under your accounts as priced modules; videos on the exchange page and the mobile apps page; store-review lessons in how to build a crypto wallet app.
7. Evidence, support and exit requirements
| Requirement | Evidence to ask for |
|---|---|
| Technical-file sections for our licence application: architecture, custody design, business continuity, access control, logging | Redacted sample or template sections, with no client-confidential information |
| Support hours, severity definitions, response targets, escalation path, channels, languages and maintenance windows written into the order; what the annual fee covers | Support schedule |
| Price list with modules, taxes and third-party costs separated; year-one and year-three totals | Public price list or a binding quote |
| Exit: sample exports for users, balances, orders, trades, audit logs and address history; licence continuity; migration between deployment models | Contract clauses; a test export |
BitPolaris evidence: the licence technical pack service prepares the technical sections; prices and a year-one configurator on the pricing page; updates and support at 20% of licence a year on self-hosted, with hours and residency written into the order; migration between models typically about two weeks, scoped in the order.
Scoring
Score each group from 0 to 3 on evidence received, not on promises, and multiply deployment and key control by two. A vendor that scores zero on either of those two should leave the shortlist regardless of the rest: where your authorisation requires evidence of asset control, other features do not compensate for missing custody evidence. Among the remaining vendors, the year-one total and the live console walkthrough usually separate them.
Crypto exchange software requirements FAQ
What are the core requirements for crypto exchange software?
Seven groups: deployment and key control, matching and markets, liquidity, custody and chains, an operations console with approval queues and an audit log, web and mobile clients, and evidence, support and exit terms. Write each as an evidence request so that vendors demonstrate rather than assert.
What should a crypto exchange software RFP ask vendors to show?
Three artefacts from everyone: a year-one price with modules itemised, a live walkthrough of the operations console, and the technical-file sections the vendor can provide for your licence application. Add the key-ceremony procedure and the liquidity model in writing, and a redacted pen-test summary.
How do I compare a hosted platform with a self-hosted licence in an RFP?
Score them on the same sheet. Hosted platforms need extra key-control evidence: who holds the keys, who the custodian is and what access the vendor retains. Self-hosted licences move operations onto your team, so add staffing to the cost. Our vendor comparison shows how fourteen vendors answer these questions on their public pages, and works as a vendor due diligence checklist.
Which requirement is most often missing from RFPs?
The operations console. Most RFPs specify trading features and forget approval queues, audit logs and support tooling, which are what compliance reviewers and support teams use every day and what takes longest to build.
BitPolaris publishes its answers to this checklist: deployment models, prices, chains, console and liquidity are on the product pages, and the system can be seen running before you sign.