Blockchain & Digital Assets › Stablecoin Payments

Stablecoin Payments

AE-240.70 Level 2 API Evangelist extension API Evangelist extension, CC BY-NC-SA 6 providers 10 API surfaces 4 rated strong or better

Moving money as fiat-backed tokens.

Stablecoin Payments (AE-240.70) is a level-2 business capability under Blockchain & Digital Assets in the API Evangelist extension model. The catalog holds 10 API surface(s) from 6 provider(s) that can perform some part of it, 4 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 the API Evangelist extension to the business-capability model, written by API Evangelist and licensed CC BY-NC-SA 4.0. API Evangelist capability extension — https://apievangelist.com Audience: b2bconsumer It extends, and never modifies, Turbo EA Capabilities by Vincent Verdet (CC BY 4.0). · Extension provenance and licence

Sub-capabilities

Stablecoin Issuance AE-240.70.10API Evangelist extension, CC BY-NC-SA

b2b

Minting and redeeming stablecoins.

no catalog coverage

Crypto Payment Acceptance AE-240.70.20API Evangelist extension, CC BY-NC-SA

b2b

Merchants accepting crypto and stablecoins.

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 1 Complete, well-documented, and agent-ready
Strong 3 Solid coverage with minor gaps
Developing 2 Usable, with meaningful gaps to close
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 Stablecoin Payments. 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 →