Payments & Card Management › Payment Processing Management
Payment Processing Management
BC-1340.20
Level 2
Banking & Capital Markets
32 providers
47 API surfaces
9 rated strong or better
Payment processing, routing, formatting, ISO 20022.
Payment Processing Management (BC-1340.20) is a level-2 business capability under Payments & Card Management in the Banking & Capital Markets model. The catalog holds 47 API surface(s) from 32 provider(s) that can perform some part of it, 9 of them rated strong or better. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.
Where this capability definition comes from.
This capability is part of a published business-architecture model that API Evangelist
did not author. It is redistributed here under
CC-BY-4.0.
Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0
Changes: Consolidated from 333 per-L1 YAML files into one JSON; English only (upstream i18n/ omitted); descriptions whitespace-normalised. No capability was added, removed, renamed or re-parented.
Source repository · NOTICE and third-party framework attributions
API Evangelist annotation.
Audience:
b2bconsumer
Payment Processing Management ("payments", "payment processing", "payment gateway" tags).
This audience annotation is API Evangelist's, not part of the Turbo EA model —
API Evangelist capability extension — https://apievangelist.com, CC BY-NC-SA 4.0.
Sub-capabilities marked
API Evangelist extension below are API Evangelist work, not Turbo EA's —
API Evangelist capability extension — https://apievangelist.com,
CC BY-NC-SA 4.0
·
provenance.
Sub-capabilities
Payment Enrichment and Formatting BC-1340.20.10
Enrichment and ISO 20022 formatting of payment messages.
no catalog coverage
Payment Routing BC-1340.20.20
Routing of payments to appropriate rails and correspondents.
no catalog coverage
Payment Sanctions Screening BC-1340.20.30
Sanctions and restricted party screening of payments.
no catalog coverage
Payment Investigations BC-1340.20.40
Investigation of failed, returned, and queried payments.
no catalog coverage
Payouts & Disbursements AE-937API Evangelist extension, CC BY-NC-SA
b2b
Paying drivers, sellers and creators in bulk to bank accounts (HDFC CBX, Stripe and Juspay payouts in Namma Yatri). Settlement reconciliation stays on Payment Processing.
no catalog coverage
Providers that reach this capability
Ordered by rating band. Reach means a provider publishes an API surface that can perform
some part of this capability — it is not a claim that any particular
organisation has deployed it.
Exemplar
4
Complete, well-documented, and agent-ready
Strong
5
Solid coverage with minor gaps
Developing
14
Usable, with meaningful gaps to close
Thin
9
Limited public surface area
This page carries no rating. Capabilities are not rated. A capability is a description of what a business does, not a thing a company publishes, so a Kin Score would have nothing to measure.
The edge table is a Pro feature.
This page shows
which providers and tags reach Payment Processing Management. The underlying
tag → capability edges — each with the quoted fragment of the provider's own
OpenAPI that evidences it, a calibrated confidence score, and the contract-provenance gate
it passed — are available through the API, along with company-level capability maps.
Only edges at confidence ≥ 0.7 with evidence found verbatim in
the source contract are published at all.
See plans →
·
How the edges are graded →