Financial Technology Buyer's Glossary
Plain definitions of the contract, pricing, technology and compliance terms that come up when financial institutions evaluate and buy software.
- Data residency
- A requirement that customer data be stored, and sometimes processed, within a specific country or region. Rules vary widely, from India's payment data localization to GDPR transfer restrictions in Europe.
- Exit and transition assistance
- Contract terms that oblige a vendor to return your data in a usable format and support migration to a replacement at agreed rates. Without them, leaving a vendor can cost more than joining.
- False positive rate
- The proportion of alerts from screening, monitoring or fraud tools that turn out to be legitimate activity. It drives analyst headcount more than almost any other metric.
- Implementation partner (systems integrator)
- A third-party firm that configures, integrates and migrates data onto a vendor's software. Its fees often match or exceed the license cost on core banking and wealth platform projects.
- Material outsourcing
- An outsourcing arrangement important enough that a supervisor expects formal risk assessment, notification or approval, plus audit and exit rights in the contract. Definitions differ by regulator, for example under EBA guidelines, MAS rules or RBI directions.
- Minimum annual commitment
- A contractual floor on fees that you pay whether or not usage reaches it. It's common in per-check KYC, payments and BaaS pricing and can wipe out the benefit of a low unit price.
- Politically exposed person (PEP)
- An individual with a prominent public role, or their close family and associates, who must be subject to enhanced due diligence under AML rules. Vendors' PEP data coverage and refresh frequency differ by country.
- Proof of concept (POC)
- A time-boxed trial in which a shortlisted vendor runs your real scenarios or sample data in a sandbox. A well-scripted POC exposes gaps that demos hide.
- RTO and RPO
- Recovery time objective is how fast a system must be restored after an outage; recovery point objective is how much data loss, measured in time, is acceptable. Regulators in many markets expect both to be defined for critical services.
- Service level agreement (SLA)
- The contractual commitments on availability, support response and incident resolution, plus the service credits owed when they're missed. Check how uptime is measured and what's excluded.
- SOC 2 Type II and ISO 27001
- Independent attestations of a vendor's security controls: SOC 2 Type II reports on how controls operated over a period, while ISO 27001 certifies an information security management system. Most banks ask for at least one during due diligence.
- Source code escrow
- An arrangement where a vendor deposits its source code with a neutral third party, released to the customer if the vendor fails or stops supporting the product. It's more relevant to on-premise software than to multi-tenant SaaS.
- Sponsor bank
- A licensed bank that holds accounts, issues cards or provides payment access on behalf of a fintech, often through a BaaS provider. It carries ultimate regulatory responsibility and sets compliance requirements for the program.
- Straight-through processing (STP)
- The share of transactions, applications or onboarding cases completed end to end without manual intervention. Vendors quote STP rates freely, so ask how they're measured.
- Suspicious transaction report (STR/SAR)
- A report a regulated firm files with its national financial intelligence unit when it suspects money laundering or terrorist financing. Many units, including those using goAML, require specific electronic formats.
- Total cost of ownership (TCO)
- The full cost of a system over a set period, usually five years, including licenses, implementation, integration, hosting, internal staff and exit costs. It's the right number to compare vendors on, not the year-one quote.
D
E
F
I
M
P
R
S
T