Capabilities

Before You Start

Read the following guides before proceeding:

Overview

A capability is a product the corporation may use — a SEPA account, virtual cards, a PIX payout
corridor. Every capability carries a status, and the status is what the API enforces: a card issuance
call with VisaVirtualCard in any status other than Active is refused with 400 and
Capability is not active.

Read capabilities from GET /api/v1/corporations. Check the capability before the call, not after the
rejection — the rejection carries no indication of which precondition failed.

Capability Status

status_reason carries the specific cause and is the field to log:

Evaluation Order

Capabilities are evaluated on every read of GET /api/v1/corporations, in this order:

1. Country availability      →  Active, or NotAvailable ("Country is not supported")
2. Per-corporation overrides →  forced Active or NotAvailable
3. Verification levels       →  NotFulfilled if a required level is not Approved
4. Prerequisites             →  NotFulfilled / NotAvailable if a prerequisite is not Active
5. Activation validators     →  Active / ActivationNotStarted / InProgress / NotAvailable

Capabilities with no prerequisites are evaluated first, so a prerequisite's status is final before
anything depending on it is judged. Each stage stops the chain: a capability that fails verification is
never checked for activation, so status_reason names the first unmet condition, not every unmet
condition.

A corporation with no registration address gets an empty capability list. Evaluation starts from
the country on corporation_registration_address; with no address there is no country, and the list
comes back empty rather than as a list of NotAvailable entries. Every capability check then fails.
The address arrives with KYB — see Verification (KYB).

Capability Reference

Cards

Bank Accounts

The four *Account capabilities run the account activation validator: ActivationNotStarted when no
details of that type exist, InProgress while details are Pending, Active once any are Active,
and NotAvailable when details exist but none is Active or Pending. All four also require the
corporation profile to be Active.

FasterPaymentsIn1stParty, FasterPaymentsIn3rdParty and FasterPaymentsOut1stParty declare no
prerequisite on FasterPaymentsAccount, unlike their SEPA, ACH and SPEI counterparts. They can read
Active before any Faster Payments account exists. Check FasterPaymentsAccount itself before
attempting a Faster Payments flow.

Payout Corridors

Corridors route through an external provider profile, and the profile is the prerequisite.

CpnExternalProfile and TripleAExternalProfile are provisioned by Wirex. There is no partner-callable
activation for either — a corridor stuck on NotFulfilled with
Prerequisite capability is not active yet needs the provider profile, which is an onboarding
conversation, not an API call.

See Corridor Transfers for the transfer flow.

Exchange

Country Matrix

GET /api/v1/global/capabilities

Anonymous — no Authorization header. Returns the capability dictionary for every supported country,
before any corporation-specific evaluation.

Response:

{
  "capabilities": {
    "GB": [
      {
        "type": "VisaVirtualCard",
        "status": "Active",
        "status_reason": "",
        "prerequisites": [],
        "verification_requirements": [{ "type": "SDD", "order": 1 }]
      }
    ],
    "US": [
      {
        "type": "SepaAccount",
        "status": "NotAvailable",
        "status_reason": "Country is not supported",
        "prerequisites": [],
        "verification_requirements": []
      }
    ]
  }
}

Every entry reads Active unless the capability is unavailable in that country. This endpoint answers
"is this product offered where the corporation is registered" — it never reflects a corporation's own
verification, activation or card counts. Use it during pre-sales and country selection; use
GET /api/v1/corporations for anything operational.

A country absent from the map returns an empty list rather than an error.

Diagnosing a Blocked Capability

{
  "type": "SepaOut3rdParty",
  "status": "NotFulfilled",
  "status_reason": "Prerequisite capability is not active yet",
  "prerequisites": ["SepaAccount"],
  "verification_requirements": [{ "type": "SDD", "order": 1 }]
}

Work outward from status_reason:

1. Verification requirements not fulfilled → compare verification_requirements against
   verification_levels. Start the missing level with POST /api/v1/corporations/level-token.
2. Prerequisite capability is not active yet → find each entry of prerequisites in the same
   response and diagnose that one first.
3. Account should be activated... → call POST /api/v1/bank/accounts with the matching
   account_type.
4. Account activation is in progress → poll GET /api/v1/bank/accounts until the details are
   Active.
5. Country is not supported → the product is not offered where the corporation is registered. No API
   call changes this.
6. Corporation profile is not active → the corporation's status is not Active. Wirex advances it.
7. You have reached the maximum number of... → close a card before issuing another.