emerging · -1.4 market domain

Real-Time Payments

Score 23.3 / 100 26 providers +9 via APIs 23 APIs Search apis.io →
Business capabilities this tag reaches
Payments & Card Management 1

Providers using this tag (26)

Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.

Strong 3 Solid coverage with minor gaps
Developing 12 Usable, with meaningful gaps to close
Thin 4 Limited public surface area
Emerging 5 Early or largely undocumented
Minimal 2 Almost no public developer surface

APIs with this tag (23)

Ranked by the provider's API Evangelist rating — the Kin Score is scored per provider, not per API, so every API of a provider shares its band. How the rating works →

Strong 1 Solid coverage with minor gaps
Developing 6 Usable, with meaningful gaps to close
Thin 10 Limited public surface area
Emerging 5 Early or largely undocumented
Minimal 1 Almost no public developer surface

Companies reaching this through an API (9)

These companies publish an API, specification or operation carrying “Real-Time Payments” but do not classify their business under it. Listed unranked and kept out of the count above, because one tagged operation is not a statement about what a company does.

Australia and New Zealand Banking Group (ANZ) Cielo Citigroup Commonwealth Bank First Citizens BancShares Mastercard Royal Bank of Canada Scotiabank Sila

Score breakdown

Frequency
45.2
log-scaled weighted occurrences
Breadth
0.6
spread across providers
Quality lift
39.5
mean composite of providers using it
Cohesion
26.1
strength of nearest seed neighbor

Where this tag sits

Payments broader

Related tags

Account-to-Account 16 co-occurrences PayTo 8 co-occurrences New Payments Platform 7 co-occurrences ISO 20022 9 co-occurrences PayID 6 co-occurrences Instant Payments 8 co-occurrences ACH 15 co-occurrences Confirmation of Payee 6 co-occurrences

Where this tag comes from

Provider tag27
Api tag23
Openapi tag1
Openapi op tag1

Cohort brief

Auto-generated

The 26 providers in the APIs.io catalog tagged Real-Time Payments, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.

Providers
26
all scored
Mean Kin Score
37.6
+15.4 vs catalog 22.2
Mean Agent Readiness
26.1
+14.1 vs catalog 12
Spread
0–63.3
median 41 · σ 16.1
How the 26 split by band
Exemplar 0Strong 3Developing 12Thin 4Emerging 5Minimal 2
Facet averages, against the whole catalog
FacetThis cohortCatalogDifferenceScored
Developer Ergonomics 46 23.2 +22.8 26
Contract Quality 36.2 17.2 +19 26
Discoverability 69.8 57.9 +11.9 26
Access Clarity 33.9 23.9 +10 26
Operational Transparency 22 13 +9 26
Contract Governance 13.1 6.5 +6.6 26

A facet is averaged over the members that carry it, not over the whole cohort — the “Scored” column is that count. Averaging an absent facet as zero would score our own coverage gaps as the providers’ posture.

What this cohort publishes
ArtifactThis cohortCatalogDifference
MCP server (any) 23% 13% +10
MCP server (first-party) 19% 12% +7
Agent Skills 0% 0% 0
OAuth scopes 23% 11% +12
Security 100% 98% +2
Arazzo workflows 0% 2% -2
Governance rules 15% 16% -1

mcp_pct counts any mcp/ artifact including ones API Evangelist derived from the provider OpenAPI; mcp_first_party_pct counts only servers the provider publishes. Prefer the latter.

Top by Kin Score
  1. 1 Azupay 63.3
  2. 2 VoPay 62.3
  3. 3 Zai 56.4
  4. 4 NovoPayment 53.8
  5. 5 Zepto 53.6
  6. 6 Monoova 51.2
  7. 7 TabaPay 48.4
  8. 8 Aeropay 47.6
  9. 9 ACI Worldwide 45.7
  10. 10 Interchecks 43.4
Top by Agent Readiness
  1. 1 Azupay 59
  2. 2 Zai 47.1
  3. 3 Zepto 45.7
  4. 4 Fifth Third Bancorp 44.9
  5. 5 Aeropay 42.6
  6. 6 VoPay 42.2
  7. 7 TabaPay 40.7
  8. 8 Volt 37.5
  9. 9 Form3 36.2
  10. 10 Interchecks 35.5
All 26 members of this roster resolve to a scored provider in the catalog.
Coverage caveat. 24 of 26 scored members had under half their catalog-attributable points satisfied at all (catalog_earned / catalog_max < 0.5). They are INCLUDED in the mean above. A large share here means the cohort mean is partly a measurement of how far our enrichment reached, not only of how these providers publish.Generated from the catalog build of 24 October 2026, across 31984 providers, using the same computation served by the APIs.io cohort API. Briefs are published for rosters of 5 or more scored providers; below that a distribution is not meaningful.

Work with this as data

Every tag here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for tags

7 MCP tools reach this
  • find_tagsBrowse and filter every tag in the catalog.
  • get_cohortThis tag as a scored cohort — every provider carrying it, with scores.
  • cohort_statsPRO — the distribution across this tag: mean, median, band split, adoption rates.
  • cohort_rankingsPRO — the leaderboard, on composite AND agent-readiness axes.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This tag
curl "https://apis.io/api/v1/tags/real-time-payments"
All tags
curl "https://apis.io/api/v1/tags?limit=25"
As a scored cohort
curl "https://apis.io/api/v1/cohorts/tag/real-time-payments"
The distribution (Pro)
curl "https://apis.io/api/v1/cohorts/tag/real-time-payments/stats" \
  -H "X-API-Key: $APIS_IO_KEY"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.