Payments
PaymentPayments
Providers using this tag (1492)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 27 Complete, well-documented, and agent-ready
Strong 110 Solid coverage with minor gaps
Developing 353 Usable, with meaningful gaps to close
Thin 354 Limited public surface area
Emerging 342 Early or largely undocumented
Minimal 301 Almost no public developer surface
Unrated 5 Not yet scored
APIs with this tag (954)
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 28 Complete, well-documented, and agent-ready
Strong 116 Solid coverage with minor gaps
Developing 311 Usable, with meaningful gaps to close
Thin 292 Limited public surface area
Emerging 181 Early or largely undocumented
Minimal 26 Almost no public developer surface
Companies reaching this through an API (218)
These companies publish an API, specification or operation carrying “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.
Show all 218 companies ↓
Score breakdown
Where this tag sits
1492 providers carry this tag directly, and 1571 counting the 40 narrower tags below and the 1 beneath them — 79 more to reach.
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 1437 providers in the APIs.io catalog tagged 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 | 35.1 | 23.2 | +11.9 | 1437 |
| Contract Quality | 27.7 | 17.6 | +10.1 | 1437 |
| Access Clarity | 33 | 26.5 | +6.5 | 1437 |
| Operational Transparency | 19.6 | 13.7 | +5.9 | 1437 |
| Discoverability | 63.4 | 58.1 | +5.3 | 1437 |
| Contract Governance | 8 | 6.3 | +1.7 | 1437 |
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) | 16% | 14% | +2 |
| MCP server (first-party) | 15% | 12% | +3 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 17% | 11% | +6 |
| Security | 100% | 98% | +2 |
| Arazzo workflows | 3% | 2% | +1 |
| Governance rules | 11% | 14% | -3 |
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 Plaid 86.1
- 2 Airwallex 85.3
- 3 Shopify 83.9
- 4 Stripe 81.6
- 5 Lightspeed Commerce 78.8
- 6 Tabby 77.1
- 7 Cvent Registration 76.9
- 8 Square 75.4
- 9 MandateShield 74.2
- 10 Hilt 72.4
- 1 Natural AI 71.2
- 2 Mollie 69.8
- 3 Ultravioleta DAO 69.1
- 4 Agentcard 68.3
- 5 Allowance 66.9
- 6 SCVD General Store 65.7
- 7 Drippay 64.2
- 8 Goody 63.1
- 9 Appcharge 62.5
- 10 Resolve 62.1
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.