EMV Card Terminals (card acceptance hardware and kernels)

Where this market publishes its structure

• EMVCo Approved Products, Acceptance Device (emvco.com/approved-products-search; admin-ajax emvco_algolia_search) machine-readable, 10,381 approvals (2,667 active), 1,006 companies; 11 in-market providers linked by register-name; 9 linked holders held out-of-market; most terminal makers (PAX, Ingenico, Newland, Nayax, Castles, Sunmi...) have no repo (harvest candidates)
• PCI PTS POI approved devices (PCI SSC listings) machine-readable, reused: read by sweep-compliance-assurance.py; no new edges; PTS holders enter the cohort
• EMVCo Card & Mobile / Security Evaluation / 3-D Secure approvals machine-readable, not acceptance devices (issuer cards, chips, 3DS servers); out of scope, not read
• Visa approved terminal lists (Visa Ready / Technology Partner) not machine-readable: partner portal login (partner.visa.com 502, technologypartner.visa.com 404 behind login); not read
• Mastercard Terminal Quality Management (TQM) / approved terminals not machine-readable: mastercard.com TQM page 403 to non-browser; label lists live in Mastercard Connect (login); not read

Own = declares at least one integration itself; covered = visible only because an aggregator, standards body, regulator or partner contract names it; distribution-only = listed only on cloud marketplaces it sells through, a channel reported beside, never counted as its own declared integrations; undeclared = nothing we can read, so no number; declares_compatibility = providers with a `compatible` shape vote, report only (kin, 2026-10-13): never counted as own, never in depth or position.

Taxonomy how this market maps onto apis.io

Derived 2026-10-23 from the 35 providers in this market we could resolve in the catalog. The percentage is the share of those providers carrying each one; it describes the market, not the tag or industry. Tag groups have no page of their own yet, so they are listed unlinked.

share of resolved cohort carrying it; tags >=0.20 & >=3 members (max 12, junk dropped), tag_groups >=0.20 (cooccurrence, non-cross-cutting; max 8), industries >=0.20 (max 6), areas >=0.10 (max 6; areas are keyword-matched and sparse), capabilities L1 >=0.20 (max 8); derive-market-taxonomy.py

Leaders by position (provisional)

Provisional: grouped by position, depth compared within a position only. Distribution (cloud marketplaces) and iPaaS bridges are counted beside position, never inside it. Unknown-builder listings are left out of position shares and counted here.

gravity 4 · other companies invest to build on it

builds-on 3 · publishes apps on other platforms' stores

regulated 6 · named in a regulator's register or partners' contracts

standard 9 · listed by a voluntary standard's own directory

mixed 2 · no single mode dominates

distribution 3 · only sells through cloud marketplaces

undeclared 8 · declares nothing we can read: no number

Top workflows by market votes

Workflows (Arazzo) and their phrasing are generated by API Evangelist, ranked by market votes (integration edges in the graph, weighted by channel).

In-market workflows only: a step on the market provider's side maps to this market's business capabilities (), and the partner is not a generic export/notify app. Other workflows are counted as bridges (including any whose steps do not resolve to a capability yet). Methodology. In-market: 71; bridges: 0.