Card Payments
Workflows using this tag
Efí Boleto Charge Issue · Efí Pay (Gerencianet)
Efí Account Webhook Setup · Efí Pay (Gerencianet)
Efí CNAB Statement Schedule · Efí Pay (Gerencianet)
Efí Pix Charge Revise · Efí Pay (Gerencianet)
Efí Card Charge Refund · Efí Pay (Gerencianet)
Efí Pix Charge Status and Refund · Efí Pay (Gerencianet)
Efí Pix Cash-Out Send · Efí Pay (Gerencianet)
Efí Bill Payment by Bar Code · Efí Pay (Gerencianet)
Business capabilities this tag reaches
Payments & Card Management 3
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 15 Usable, with meaningful gaps to close
Thin 6 Limited public surface area
APIs with this tag (18)
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 1 Solid coverage with minor gaps
Developing 13 Usable, with meaningful gaps to close
Worldpay Card Payments APIThe Card Payments API from Worldpay — 2 operation(s) for card payments.Trust Payments Webservices APIServer-to-server JSON API (the Secure Trading Payment Platform / STPP) for card processing and management o...iyzico Payment APIREST API for accepting card payments (NON-3DS and 3D Secure), hosted CheckoutForm and Pay with iyzico flows...Increase Card Payments APICard Payments group together interactions related to a single card payment, such as an authorization and it...Mercado Pago Checkout APIFull server-side checkout control. Tokenise cards client-side, create a payment server-side, manage 3DS cha...Cardstream Gateway - Direct IntegrationServer-to-server integration. The merchant collects payment details on its own secure server and sends a UR...Cardstream Gateway - Hosted IntegrationHosted Payment Pages (HPP) integration. The merchant's browser POSTs a URL-encoded request to the Gateway, ...Cashflows Payments APIREST/JSON API for cardholder-not-present card payments with 3-D Secure support — authorisation, capture, vo...Westpac PayWay REST APIFirst-party Westpac payment API (beyond CDR). PayWay is Westpac's merchant payment platform; its public RES...Westpac QuickStream REST APIFirst-party Westpac payment API (beyond CDR). QuickStream is Westpac's online payment gateway; its public R...GOV.UK Pay Card payments APIThe Card payments API from GOV.UK Pay — 5 operation(s) for card payments.ACI Open Payment Platform — Server-to-Server APIThe core RESTful payment API of the ACI Open Payment Platform (PAY.ON gateway). Server-to-Server integratio...eWAY Rapid APIThe eWAY Rapid API is a versioned HTTP payments API (v47) for processing card transactions. It exposes tran...
Thin 2 Limited public surface area
Emerging 1 Early or largely undocumented
Companies reaching this through an API (9)
These companies publish an API, specification or operation carrying “Card 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
Frequency
45.3
log-scaled weighted occurrences
Breadth
0.7
spread across providers
Quality lift
53.3
mean composite of providers using it
Cohesion
10.1
strength of nearest seed neighbor
Where this tag sits
Related tags
Acquiring 12 co-occurrences
Payment Gateway 20 co-occurrences
Payment Processing 14 co-occurrences
3D Secure 7 co-occurrences
In-Person Payments 5 co-occurrences
Bank Transfers 6 co-occurrences
Payment Links 7 co-occurrences
Refunds 15 co-occurrences
Where this tag comes from
Provider tag26
Api tag18
Openapi tag2
Openapi op tag6
Cohort brief
Auto-generatedThe 26 providers in the APIs.io catalog tagged Card 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
43.3
+20.4 vs catalog 22.9
Mean Agent Readiness
27
+15.1 vs catalog 11.9
Spread
11.1–65.2
median 46.1 · σ 11.3
How the 26 split by band
Exemplar 0Strong 3Developing 15Thin 6Emerging 2Minimal 0
Facet averages, against the whole catalog
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Developer Ergonomics | 56.7 | 23.2 | +33.5 | 26 |
| Contract Quality | 42.4 | 17.6 | +24.8 | 26 |
| Operational Transparency | 31 | 13.7 | +17.3 | 26 |
| Discoverability | 71.3 | 58.1 | +13.2 | 26 |
| Access Clarity | 37.2 | 26.5 | +10.7 | 26 |
| Contract Governance | 11.9 | 6.3 | +5.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
| Artifact | This cohort | Catalog | Difference |
|---|---|---|---|
| MCP server (any) | 15% | 14% | +1 |
| MCP server (first-party) | 12% | 12% | 0 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 12% | 11% | +1 |
| Security | 100% | 98% | +2 |
| Arazzo workflows | 8% | 2% | +6 |
| Governance rules | 15% | 14% | +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 PayMongo 65.2
- 2 Paymob 57.5
- 3 Paymentsense 55.1
- 4 Dojo 53.6
- 5 Fat Zebra 52.2
- 6 Pinch Payments 51.7
- 7 Beam Checkout 51.1
- 8 Monoova 50.6
- 9 Trust Payments 49.1
- 10 Iyzico 48.7
Top by Agent Readiness
- 1 Moneris 52.6
- 2 Paymob 47.6
- 3 Pinch Payments 38.8
- 4 Dojo 35.7
- 5 Fat Zebra 35.4
- 6 Till Payments 35.4
- 7 Zettle 34.6
- 8 Monoova 32.1
- 9 PayMongo 29.6
- 10 Yoco 28
All 26 members of this roster resolve to a scored provider in
the catalog.
Coverage caveat. 20 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 5 October 2026, across 29093 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.
Coverage caveat. 20 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 5 October 2026, across 29093 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.