Canada RPAA Payment Service Providers (Bank of Canada registry + Payments Canada)

Where this market publishes its structure

• Bank of Canada RPAA PSP registry (bankofcanada.ca/core-functions/retail-payments-supervision/psp-registry/; the page's own public JSON rps-api/cif2/accounts/list + accounts/{id}) machine-readable, 1,775 registered, 57 refused, 15 revoked, 420 in review; 1,846 account details read (own website on 1,349); 120 registered linked, 4 negative findings (2 refused, 2 revoked) recorded as evidence
• Payments Canada directories (payments.ca/payment-resources/directories: Members, ACSS direct/group clearers, Lynx participants) machine-readable, 133 members (51 banks, 26 authorized foreign banks, 16 PSPs, 19 trust/loan, 10 centrals), 12 ACSS clearers, 16 Lynx participants; names only; 20 linked; foreign bank branches held
• Payments Canada 'Our members' page (payments.ca/about-us/our-members) not machine-readable: 404; the live page is about/our-members-stakeholders/members, which links the directories read above
• Registry bulk export / CSV not machine-readable: none exposed; the list + detail JSON the page itself calls is the export
• FINTRAC MSB registry not machine-readable: not re-read: consumer-lending-licensing recorded FINTRAC unreadable (connection refused)

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 151 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 9 · other companies invest to build on it

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

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

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

core 2 · builds the connectors its customers need

mixed 14 · no single mode dominates

list 3 · a long list on its own page, mostly unevidenced

distribution 1 · only sells through cloud marketplaces

undeclared 11 · 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: 96; bridges: 0.