Real-Time Payments
Real Time PaymentsReal-Time PaymentsReal-time payments
Providers using this tag (27)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Strong 1 Solid coverage with minor gaps
Developing 13 Usable, with meaningful gaps to close
Thin 7 Limited public surface area
Emerging 5 Early or largely undocumented
Minimal 1 Almost no public developer surface
APIs with this tag (25)
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 →
Exemplar 1 Complete, well-documented, and agent-ready
Strong 2 Solid coverage with minor gaps
Developing 5 Usable, with meaningful gaps to close
Thin 13 Limited public surface area
Emerging 3 Early or largely undocumented
Minimal 1 Almost no public developer surface
Companies reaching this through an API (11)
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.
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 27 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.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Developer Ergonomics | 46.3 | 23.4 | +22.9 | 27 |
| Contract Quality | 38.4 | 19.8 | +18.6 | 27 |
| Discoverability | 70.2 | 61.2 | +9 | 27 |
| Operational Transparency | 21.4 | 14 | +7.4 | 27 |
| Contract Governance | 11 | 6.4 | +4.6 | 27 |
| Access Clarity | 30.4 | 26.5 | +3.9 | 27 |
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.
| Artifact | This cohort | Catalog | Difference |
|---|---|---|---|
| MCP server (any) | 15% | 10% | +5 |
| MCP server (first-party) | 11% | 13% | -2 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 22% | 11% | +11 |
| Security | 100% | 97% | +3 |
| Arazzo workflows | 0% | 2% | -2 |
| Governance rules | 4% | 14% | -10 |
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.
- 1 Zepto 54.7
- 2 Azupay 53.7
- 3 Monoova 52.8
- 4 Zai 52.6
- 5 TabaPay 52
- 6 VoPay 51.9
- 7 Aeropay 49.9
- 8 ACI Worldwide 49.3
- 9 Interchecks 45.7
- 10 Form3 45.1
- 1 Fifth Third Bancorp 43.7
- 2 Zepto 43.6
- 3 Zai 41.5
- 4 TabaPay 41.5
- 5 Aeropay 41.5
- 6 Azupay 40.8
- 7 KeyCorp 40.1
- 8 VoPay 38.6
- 9 Interchecks 37.6
- 10 Form3 36.1
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.