Payments & Card Management

BC-1340 Level 1 Banking & Capital Markets 3 providers 39 API surfaces 2 rated strong or better

Payment initiation, processing, clearing/settlement, card issuance and transaction processing.

Payments & Card Management (BC-1340) is a level-1 business capability in the Banking & Capital Markets model. The catalog holds 39 API surface(s) from 3 provider(s) that can perform some part of it, 2 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

Sub-capabilities

Payment Initiation Management BC-1340.10

Payment instruction capture, validation, authorisation.

2 providers, 12 API surfaces

Payment Processing Management BC-1340.20

Payment processing, routing, formatting, ISO 20022.

2 providers, 3 API surfaces

Clearing & Settlement Management BC-1340.30

Domestic clearing - ACH, BACS, SEPA, FPS - and settlement.

no catalog coverage

Cross-Border Payment Management BC-1340.40

International payments, correspondent banking, FX.

no catalog coverage

Real-Time Payment Management BC-1340.50

Real-time / instant payment rails.

no catalog coverage

Card Issuance Management BC-1340.60

Card production, personalisation, dispatch, activation.

2 providers, 8 API surfaces

Card Transaction Processing Management BC-1340.70

Switching, authorisation, fraud screening, chargebacks.

1 provider, 5 API surfaces

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.

Workflows that realise this capability

Arazzo workflows whose own sourceDescriptions call APIs that carry this capability. The link is derived, not asserted: each workflow declares x-realizes-capability-ids with the spec and confidence behind it.

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 Payments & Card 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 →