Payments & Card Management › Cross-Border Payment Management

Cross-Border Payment Management

BC-1340.40 Level 2 Banking & Capital Markets 46 providers 157 API surfaces 8 rated strong or better

International payments, correspondent banking, FX.

Cross-Border Payment Management (BC-1340.40) is a level-2 business capability under Payments & Card Management in the Banking & Capital Markets model. The catalog holds 157 API surface(s) from 46 provider(s) that can perform some part of it, 8 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

Cross-Border Payment Management ("cross-border payments" tag).

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

Correspondent Banking Management BC-1340.40.10

Correspondent banking relationships and RMA management.

no catalog coverage

Cross-Border Payment Routing BC-1340.40.20

Routing of cross-border payments via SWIFT and alternative rails.

no catalog coverage

FX Conversion for Payments BC-1340.40.30

FX conversion, rate sourcing, and pricing for payments.

no catalog coverage

SWIFT GPI Tracking BC-1340.40.40

SWIFT GPI status tracking and customer transparency.

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 5 Complete, well-documented, and agent-ready

QontoInternational Transfers1 API77.0 WeavrCorrespondent Bank Transfers1 API77.0 RevolutInternational paymentInternational scheduled paymentInternational standing order3 APIs70.0 Narmiinternational wiresswift wire templates2 APIs67.9 LightsparkCross-Currency Transfers1 API66.9

Strong 3 Solid coverage with minor gaps

iBanFirstPayments1 API60.4 MastercardConversions1 API55.7 PrometeoCross-Border1 API54.6

Developing 18 Usable, with meaningful gaps to close

Thin 20 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 Cross-Border Payment 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 →