Market scan guide · Payments

How to run a payments market scan

Payments scans are narrow and technical: a gateway, a real-time payments connection, a card issuing platform or a payments hub are different purchases with different vendors. The scan has to say which of these the institution is buying and hold vendors to the certifications and rails that purchase needs.

Figures from the Vederca registry as of 2026-11-06: 168 payments vendors, 429 products, 29 countries.

The payments landscape in numbers

Payments software for financial institutions: the Vederca market map
The payments market map: every vendor's own mark, by named customers then name, drawn from the registry. Download the map (PNG, or as SVG).

The registry lists 168 payments vendors with 429 products, headquartered in 29 countries. 95 name at least one financial institution as a customer. 4 of the products mention an AI capability in their own text (1%).

Payments vendors by headquarters country
United States: 46United States46United Kingdom: 32United Kingdom32Australia: 29Australia29France: 7France7India: 6India6Canada: 5Canada5Germany: 5Germany5Singapore: 5Singapore5Brazil: 3Brazil3Belgium: 2Belgium2
Payments vendors by headquarters country: the figures as a table
ItemValue
United States46
United Kingdom32
Australia29
France7
India6
Canada5
Germany5
Singapore5
Brazil3
Belgium2
Capabilities most often mentioned by payments products
Acquiring: 42, 0 confirmedAcquiring42Reconciliation: 42, 0 confirmedReconciliation42Issuing: 37, 0 confirmedIssuing37Payouts: 29, 0 confirmedPayouts29Processing: 28, 0 confirmedProcessing28Cross border: 27, 0 confirmedCross border27Real time: 27, 0 confirmedReal time27Fraud: 26, 0 confirmedFraud26Recurring: 23, 0 confirmedRecurring23Wallets: 20, 0 confirmedWallets20Npp: 17, 0 confirmedNpp17Collection: 12, 0 confirmedCollection12
Capabilities most often mentioned by payments products: the figures as a table
ItemValue
Acquiring 0 confirmed42
Reconciliation 0 confirmed42
Issuing 0 confirmed37
Payouts 0 confirmed29
Processing 0 confirmed28
Cross border 0 confirmed27
Real time 0 confirmed27
Fraud 0 confirmed26
Recurring 0 confirmed23
Wallets 0 confirmed20
Npp 0 confirmed17
Collection 0 confirmed12
Payments vendors founded, by year
2017: 5520172018: 4420182019: 8820192020: 1120202021: 2220212022: 2220222023: 020232024: 1120242025: 020252026: 112026
Payments vendors founded, by year: the figures as a table
YearCount
20175
20184
20198
20201
20212
20222
20230
20241
20250
20261

The largest by named customers

VendorHQ countryNamed customers
BPC Banking TechnologiesSwitzerland16
InsurityUnited States13
Form3United Kingdom12
EnfuceFinland11
AlacritiUnited States10
Token.ioUnited Kingdom9
OpenWayBelgium8
SkaleetFrance8

The newest entrants

VendorHQ countryFounded
Orsun Tech OÜEstonia2026
VeleraUnited States2024
Australian Payments PlusAustralia2022
ConveraUnited States2022
OutseerUnited States2021
PartiorSingapore2021

The full list, with every vendor's flagship product and named customers: Payments software and infrastructure.

How to evaluate payments vendors

  1. Name the rail and the roleAcquiring or issuing, real-time or batch, domestic or cross-border, direct participant or through a sponsor. Vendors that do all of it well are rare.
  2. Check certifications and participationScheme certifications, PCI DSS level, and live participation in the local real-time scheme are facts with dates; ask for the certificates.
  3. Measure resilience, not throughputTransactions per second impress; availability history, failover tests and incident notification terms are what the regulator and the customer feel.
  4. Read the fraud and disputes layerReal-time fraud scoring, chargeback and dispute handling, and who owns the rules.
  5. Price per transaction and per monthPayments pricing is usage based; model your volumes at two growth rates before comparing.

The method for the scan as a whole, longlist to shortlist, is on the market scan page; the report template gives the headings.

The requirements that separate them

Must-haves in most scans of this category: the register's gates. Each needs evidence named beside it.

  • Live connection to the domestic real-time payments scheme
  • Scheme and PCI DSS certifications current and in scope
  • Card issuing and processing on the same platform as acquiring, where both are needed
  • Cross-border payments with foreign exchange and compliance screening built in
  • Documented availability and tested failover
  • Real-time fraud controls the institution can tune

The rules procurement teams ask vendors about

By country, the rules specific to payments procurements. Vederca certifies nobody against these: they say what evidence to ask for.

Australia

  • AML/CTF Act (AUSTRAC): Reporting entities keep customer identification, monitoring and AUSTRAC reporting in step with the Act and Rules.
  • Consumer Data Right: Data holders share consumer data under the CDR Rules and Standards, and recipients hold accreditation.

United Kingdom

  • MLR 2017 and NCA reporting: Customer due diligence, monitoring and suspicious activity reporting meet the Regulations and JMLSG guidance.
  • UK Open Banking (PSRs 2017): Account providers expose Open Banking APIs, and third parties access them with consent and strong authentication.

Canada

  • PCMLTFA (FINTRAC): Reporting entities verify identity, keep records and report to FINTRAC under the Act and Regulations.
  • Retail Payment Activities Act: Payment service providers register with the Bank of Canada and manage operational risk and end-user funds.
  • Consumer-Driven Banking Act: Participants are accredited and share data under the framework's technical and security standards.

United States

  • BSA/AML (FinCEN): Customer identification, monitoring and FinCEN reporting meet the BSA and the CDD Rule.
  • CFPB Section 1033: Data providers make consumer data available through developer interfaces, and third parties use it with consent.

Go further