Wise website screenshot

Wise

Wise (formerly TransferWise) provides cross-border payments and multi-currency accounts for personal and business customers. The Wise Platform API exposes profiles, balances, transfers, recipients, quotes, multi-currency accounts, cards, statements, and webhooks.

Wise publishes 47 APIs on the APIs.io network, including 3ds API, activity API, address API, and 44 more. Tagged areas include Payments, FX, Cross-Border, Banking, and Multi-Currency.

The Wise catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

Wise’s developer surface includes authentication, sandbox, changelog, documentation, and 14 more developer resources.

46.4/100 developing ▼ -5.3 Agent 54/100 agent ready Full breakdown ↓
scored 2026-07-28 · rubric v0.6
AccessPaidSelf serve
47 APIs
PaymentsFXCross-BorderBankingMulti-Currency

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-28 · rubric v0.6
Composite quality — 46.4/100 · developing
Contract Quality 17.9 / 25
Developer Ergonomics 5.2 / 20
Commercial Clarity 9.5 / 20
Operational Transparency 6.8 / 13
Governance 5.0 / 12
Discoverability 5.0 / 10
Agent readiness — 54/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 10 / 10
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 9 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 7 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 6 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/wise: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 47

Individual APIs this provider publishes, each with its own machine-readable definition.

Wise 3ds API

To manage certain aspects of the 3D Secure (3DS) authentication, you will need to integrate with the following APIs.

Wise activity API

Activity represents a snapshot of a performed action for a profile.

Wise address API

Manage physical addresses associated with user profiles. Address requirements vary by country — use the address requirements endpoints to dynamically discover which fields are n...

Wise balance API

Create and manage balance accounts within a multi-currency account. Each profile can hold multiple balance accounts in different currencies. A `STANDARD` balance is limited to o...

Wise balance-statement API

Balance statements contain transactional activities on a Wise Multi-Currency Account, including deposits, withdrawals, conversions, card transactions, and fees. Statements can b...

Wise bank-account-details API

Bank account details allow users to receive money into their Wise Multi-Currency Account. Each currency balance can have local bank details (for domestic payments) and internati...

Wise batch-group API

A batch group is a named collection of up to 1000 transfers that can be managed as a single unit. Batch groups are primarily used for funding multiple transfers with a single pa...

Wise bulk-settlement API

Bulk settlement allows partners to settle multiple transfers in a single bank transfer at the end of a settlement period. This model splits transfer creation/funding from final ...

Wise card API

Manage your customers' cards programmatically. These APIs allow you to list cards, retrieve card details, control card status, and manage spending permissions. **Key capabilitie...

Wise card-kiosk-collection API

These APIs are designed to allow you to print and encrypt your card directly from a kiosk machine. The card information will be sent to our card manufacturer to configure and pr...

Wise card-order API

With this set of APIs, you will be able to create cards for your customers. You can also retrieve and view the status of your current card orders, as well as the list of availab...

Wise card-sensitive-details API

Wise is a PCI DSS compliant provider and stores all card data securely. The scope for PCI compliance depends on your use case and will impact how you integrate. For all sensitiv...

Wise card-transaction API

Retrieve information on transactions made on your users' cards. Transaction types {% #card-transaction-type .title-3 .m-t-5 %} The possible `type` values are: - `ACCOUNT_CREDIT`...

Wise case API

Partner Cases are part of the Partner Support API, allowing partners to open, retrieve and respond to support and operations queries. The endpoints described here allow partners...

Wise claim-account API

Allow a customer to take ownership of an account [created on their behalf](/api-reference/user/usercreate). Generate a short-lived `claim_account_code` and use it when [redirect...

Wise comparison API

The comparison API can be used to request price and speed information about various money transfer providers. This includes not only Wise but other providers in the market. Pric...

Wise contact API

Find discoverable Wise profiles and add them to your recipient list using an identifier — such as a Wisetag, email, or phone number — without needing bank details. Creating a tr...

Wise currencies API

Retrieve the list of currencies supported for transfers, including currency codes and display names.

Wise delivery-estimate API

Get the estimated delivery time for a transfer, showing when funds are expected to arrive in the recipient's bank account.

Wise digital-wallet API

These APIs provide encrypted cardholder information needed to implement push provisioning (Apple Pay, Google Pay) in your own mobile app.

Wise direct-debit-account API

Register and retrieve external bank accounts used to fund batch transfers via ACH (USD) or EFT (CAD) direct debit.

Wise disputes API

Raise and manage card transaction disputes, including submission via Dynamic Flow or direct API, file uploads, and dispute lifecycle tracking. For implementation details, see: -...

Wise facetec API

Wise leverages [FaceTec's](https://www.facetec.com/) facial biometric technology for authentication. Use this endpoint to retrieve the public key needed for exporting 3D FaceMaps.

Wise jose API

Wise uses the [JOSE framework](https://jose.readthedocs.io/en/latest/) to accept and respond with signed and encrypted payloads. These endpoints allow you to manage keys and tes...

Wise kyc-review API

KYC Review API provides endpoints to view, update and submit information related to the KYC flow. There are two ways to collect KYC requirements from your customers: - **Hosted ...

Wise multi-currency-account API

The Wise multi-currency account (MCA) enables users to hold, convert, and fund transfers (single or batches) with balances in up to 56 currencies. Of the 50+ currency balances s...

Wise oauth-token API

Exchange client credentials or authorisation grants for OAuth 2.0 access tokens. All grant types use `POST /oauth/token` with basic authentication (your `client_id` and `client_...

Wise payin-deposit-detail API

The payin deposit details API allows you to get the bank details for the account that the customer should send funds to when paying for a Wise transfer via a bank transfer. Thes...

Wise payins API

The payin APIs allow you to fund the MCA or transfers with local payment rails, by retrieving or creating the relevant details to send to for funding a payment. These details wi...

Wise profile API

A profile represents an identity that can send and receive money through Wise — either a personal profile (an individual) or a business profile (a company). Most API endpoints r...

Wise quote API

The quote resource defines the basic information required for a Wise transfer - the currencies to send between, the amount to send and the profile who is sending the money. The ...

Wise rate API

Current and historical exchange rates by currency routes.

Wise recipient API

Recipient or beneficiary is the one who will receive the funds. Recipient account endpoints use a mixture of our v1 and v2 APIs. Please ensure you address the right version to g...

Wise sca-device-fingerprints API

Device fingerprints are possession-based SCA challenge factors. They allow you to verify that a user is accessing the API from a recognized device. A profile can have up to 3 de...

Wise sca-facemaps API

Facemaps are inherence-based (biometric) SCA challenge factors that use FaceTec's 3D face recognition technology. Facemaps should be exported from your FaceTec server using thei...

Wise sca-otp API

For phone-based OTP (one-time password) authentication — where an OTP is a single-use 6-digit code sent to verify the identity of a user — Wise supports multiple delivery method...

Wise sca-ott API

One-time tokens are temporary authentication sessions used to track SCA challenges. When an SCA-protected endpoint is called, a one-time token is returned containing the challen...

Wise sca-pin API

PIN (Personal Identification Number) is a knowledge-based SCA challenge factor. Users create a 4-digit PIN that can be used to verify their identity when accessing SCA-protected...

Wise sca-sessions API

SCA sessions allow you to manually trigger Strong Customer Authentication, returning a one-time token along with a list of associated challenges. These challenges can be cleared...

Wise simulation API

Use these endpoints to simulate key actions in the sandbox environment, including transfer state changes, balance top-ups, card transactions, KYC reviews, and incoming payments....

Wise spend-controls API

Control which card transactions are permitted by creating rules based on merchant category code (MCC) or transaction currency. An authorisation rule dictates whether transaction...

Wise spend-limits API

Manage spending limits applied to profiles and cards. Profile limits are shared across all cards under the same profile, while card limits apply to individual cards. For more de...

Wise transfer API

A transfer is a payment order to a [recipient account](/api-reference/recipient) based on a [quote](/api-reference/quote). Once created, a transfer usually needs to be funded wi...

Wise user API

A User serves as the primary entity and can possess multiple Profiles to represent different contexts or settings. A User can have one personal Profile and multiple business Pro...

Wise user-security API

{% admonition type="warning" %} These endpoints are deprecated. Please refer to [PIN](/api-reference/sca-pin), [Facemaps](/api-reference/sca-facemaps), and [Device Fingerprints]...

Wise verification API

In certain situations, additional evidence is required to verify customers and ensure we’re compliant with the KYC regulations. Additional Verification APIs support a list of ev...

Wise webhook API

Manage webhook subscriptions at both the application and profile level. Create, list, retrieve, and delete subscriptions, as well as test your webhook endpoints. For more inform...

Scroll for all 47

Open Collections 1

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Wise Platform API

OPEN COLLECTION

GraphQL 1

GraphQL schemas published by this provider.

Wise GraphQL Schema

This conceptual GraphQL schema models the Wise (formerly TransferWise) Platform API surface, covering cross-border money transfers, multi-currency accounts, balances, recipients...

GRAPHQL

Pricing Plans 1

Published pricing tiers and plan structures.

Wise Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Wise Rate Limits

3 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Wise Finops

FINOPS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Wise Platform Webhooks

AsyncAPI 2.6 description of the Wise Platform webhook surface. Wise pushes HTTP `POST` notifications to subscriber-defined HTTPS endpoints when events occur against profiles, tr...

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Wise API Rules

8 rules · 1 errors 7 warnings

SPECTRAL

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Wise Authentication

http · 2 schemes

SECURITY

Wise Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Wise Vulnerability Disclosure

Bugcrowd · security.txt · contact published

SECURITY

Wise Trust Center

SOC 1 Type 2, SOC 2 Type 2, PCI DSS, ISO 27001, GDPR

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Wise Agentic Access

238 operations · 147 acting · 6 human-in-the-loop

238 operations · 147 acting

AGENTIC

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 4

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: wise
url: https://raw.githubusercontent.com/api-evangelist/wise/refs/heads/main/apis.yml
name: Wise
kind: company
description: Wise (formerly TransferWise) provides cross-border payments and multi-currency accounts for personal and business
  customers. The Wise Platform API exposes profiles, balances, transfers, recipients, quotes, multi-currency accounts, cards,
  statements, and webhooks.
accessModel:
  pricing: paid
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Paid · Self-serve signup
  confidence: high
  source:
  - plans
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/wise.png
tags:
- Payments
- FX
- Cross-Border
- Banking
- Multi-Currency
created: '2026-05-08'
modified: '2026-05-30'
specificationVersion: '0.19'
apis:
- aid: wise:wise-3ds-api
  name: Wise 3ds API
  description: To manage certain aspects of the 3D Secure (3DS) authentication, you will need to integrate with the following
    APIs.
  humanURL: https://docs.wise.com/api-docs/api-reference/profile
  baseURL: https://api.wise.com/v2
  tags:
  - 3ds
  properties:
  - type: OpenAPI
    url: openapi/wise-3ds-api-openapi.yml
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/profile
  - type: Sandbox
    url: https://api.sandbox.transferwise.tech
  - type: GraphQL
    url: graphql/wise-graphql.md
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/recipient
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/quote
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/transfer
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/balance
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/multi-currency-account
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/balance-statement
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/card
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/subscription
  - type: AsyncAPI
    url: asyncapi/wise-webhooks-asyncapi.yml
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/simulation
- aid: wise:wise-activity-api
  name: Wise activity API
  description: Activity represents a snapshot of a performed action for a profile.
  humanURL: https://docs.wise.com/api-docs/api-reference/profile
  baseURL: https://api.wise.com/v2
  tags:
  - activity
  properties:
  - type: OpenAPI
    url: openapi/wise-activity-api-openapi.yml
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/profile
  - type: Sandbox
    url: https://api.sandbox.transferwise.tech
  - type: GraphQL
    url: graphql/wise-graphql.md
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/recipient
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/quote
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/transfer
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/balance
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/multi-currency-account
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/balance-statement
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/card
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/subscription
  - type: AsyncAPI
    url: asyncapi/wise-webhooks-asyncapi.yml
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/simulation
- aid: wise:wise-address-api
  name: Wise address API
  description: 'Manage physical addresses associated with user profiles.


    Address requirements vary by country — use the address requirements endpoints to dynamically discover which fields are
    needed before creating an address.'
  humanURL: https://docs.wise.com/api-docs/api-reference/profile
  baseURL: https://api.wise.com/v2
  tags:
  - address
  properties:
  - type: OpenAPI
    url: openapi/wise-address-api-openapi.yml
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/profile
  - type: Sandbox
    url: https://api.sandbox.transferwise.tech
  - type: GraphQL
    url: graphql/wise-graphql.md
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/recipient
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/quote
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/transfer
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/balance
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/multi-currency-account
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/balance-statement
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/card
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/subscription
  - type: AsyncAPI
    url: asyncapi/wise-webhooks-asyncapi.yml
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/simulation
- aid: wise:wise-balance-api
  name: Wise balance API
  description: 'Create and manage balance accounts within a multi-currency account.


    Each profile can hold multiple balance accounts in different currencies. A `STANDARD` balance is limited to one per currency,
    while `SAVINGS` balances (Jars) allow multiple in the same currency. Creating the first balance for a profile automatically
    creates the multi-currency account.


    Balances include an `investmentState` field. Only balances with `NOT_INVESTED` can be operated on via the API. Invested
    balances should be shown but not actionable.


    For a complete guide on multi-currency accounts, see [Multi-Currency Accounts](/guides/product/accounts).'
  humanURL: https://docs.wise.com/api-docs/api-reference/profile
  baseURL: https://api.wise.com/v2
  tags:
  - balance
  properties:
  - type: OpenAPI
    url: openapi/wise-balance-api-openapi.yml
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/profile
  - type: Sandbox
    url: https://api.sandbox.transferwise.tech
  - type: GraphQL
    url: graphql/wise-graphql.md
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/recipient
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/quote
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/transfer
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/balance
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/multi-currency-account
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/balance-statement
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/card
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/subscription
  - type: AsyncAPI
    url: asyncapi/wise-webhooks-asyncapi.yml
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/simulation
- aid: wise:wise-balance-statement-api
  name: Wise balance-statement API
  description: 'Balance statements contain transactional activities on a Wise Multi-Currency Account, including deposits,
    withdrawals, conversions, card transactions, and fees.


    Statements can be retrieved in multiple formats: JSON, CSV, PDF, XLSX, CAMT.053, MT940, or QIF.'
  humanURL: https://docs.wise.com/api-docs/api-reference/profile
  baseURL: https://api.wise.com/v2
  tags:
  - balance-statement
  properties:
  - type: OpenAPI
    url: openapi/wise-balance-statement-api-openapi.yml
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/profile
  - type: Sandbox
    url: https://api.sandbox.transferwise.tech
  - type: GraphQL
    url: graphql/wise-graphql.md
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/recipient
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/quote
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/transfer
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/balance
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/multi-currency-account
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/balance-statement
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/card
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/subscription
  - type: AsyncAPI
    url: asyncapi/wise-webhooks-asyncapi.yml
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/simulation
- aid: wise:wise-bank-account-details-api
  name: Wise bank-account-details API
  description: 'Bank account details allow users to receive money into their Wise Multi-Currency Account. Each currency balance
    can have local bank details (for domestic payments) and international bank details (for SWIFT payments) where available.


    Bank account details can be retrieved for existing balances, or new details can be ordered for currencies where they''re
    available but not yet issued.'
  humanURL: https://docs.wise.com/api-docs/api-reference/profile
  baseURL: https://api.wise.com/v2
  tags:
  - bank-account-details
  properties:
  - type: OpenAPI
    url: openapi/wise-bank-account-details-api-openapi.yml
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/profile
  - type: Sandbox
    url: https://api.sandbox.transferwise.tech
  - type: GraphQL
    url: graphql/wise-graphql.md
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/recipient
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/quote
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/transfer
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/balance
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/multi-currency-account
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/balance-statement
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/card
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/subscription
  - type: AsyncAPI
    url: asyncapi/wise-webhooks-asyncapi.yml
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/simulation
- aid: wise:wise-batch-group-api
  name: Wise batch-group API
  description: 'A batch group is a named collection of up to 1000 transfers that can be managed as a single unit. Batch groups
    are primarily used for funding multiple transfers with a single payment.


    **Workflow:**

    1. Create a batch group with a source currency

    2. Add transfers to the group (up to 1000)

    3. Complete the batch group to close it for modifications

    4. Fund the batch group from a balance or via direct debit


    Individual transfers in the group follow standard transfer lifecycle and can be tracked separately.'
  humanURL: https://docs.wise.com/api-docs/api-reference/profile
  baseURL: https://api.wise.com/v2
  tags:
  - batch-group
  properties:
  - type: OpenAPI
    url: openapi/wise-batch-group-api-openapi.yml
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/profile
  - type: Sandbox
    url: https://api.sandbox.transferwise.tech
  - type: GraphQL
    url: graphql/wise-graphql.md
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/recipient
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/quote
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/transfer
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/balance
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/multi-currency-account
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/balance-statement
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/card
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/subscription
  - type: AsyncAPI
    url: asyncapi/wise-webhooks-asyncapi.yml
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/simulation
- aid: wise:wise-bulk-settlement-api
  name: Wise bulk-settlement API
  description: 'Bulk settlement allows partners to settle multiple transfers in a single bank transfer at the end of a settlement
    period. This model splits transfer creation/funding from final settlement, allowing Wise to process transfers before receiving
    funds based on a partner''s guarantee.


    Use the settlement journal endpoint to submit a list of transfers to be settled, along with the settlement reference that
    matches your bank transfer payment.'
  humanURL: https://docs.wise.com/api-docs/api-reference/profile
  baseURL: https://api.wise.com/v2
  tags:
  - bulk-settlement
  properties:
  - type: OpenAPI
    url: openapi/wise-bulk-settlement-api-openapi.yml
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/profile
  - type: Sandbox
    url: https://api.sandbox.transferwise.tech
  - type: GraphQL
    url: graphql/wise-graphql.md
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/recipient
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/quote
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/transfer
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/balance
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/multi-currency-account
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/balance-statement
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/card
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/subscription
  - type: AsyncAPI
    url: asyncapi/wise-webhooks-asyncapi.yml
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/simulation
- aid: wise:wise-card-api
  name: Wise card API
  description: 'Manage your customers'' cards programmatically. These APIs allow you to list cards, retrieve card details,
    control card status, and manage spending permissions.


    **Key capabilities:**

    - List and retrieve card details for a profile

    - Update card status (active, frozen, blocked)

    - Control spending permissions (e-commerce, ATM, contactless, magnetic stripe, etc.)

    - Reset PIN attempt counter after incorrect PIN entries

    - Update card phone number for verification purposes


    {% admonition type="info" %}

    For accessing sensitive card data (PAN, CVV, PIN), see the [Sensitive Card Details API](/api-reference/card-sensitive-details).
    For ordering new cards, see the [Card Orders API](/api-reference/card-order). For transaction history, see the [Card Transactions
    API](/api-reference/card-transaction).

    {% /admonition %}'
  humanURL: https://docs.wise.com/api-docs/api-reference/profile
  baseURL: https://api.wise.com/v2
  tags:
  - card
  properties:
  - type: OpenAPI
    url: openapi/wise-card-api-openapi.yml
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/profile
  - type: Sandbox
    url: https://api.sandbox.transferwise.tech
  - type: GraphQL
    url: graphql/wise-graphql.md
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/recipient
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/quote
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/transfer
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/balance
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/multi-currency-account
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/balance-statement
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/card
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/subscription
  - type: AsyncAPI
    url: asyncapi/wise-webhooks-asyncapi.yml
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/simulation
- aid: wise:wise-card-kiosk-collection-api
  name: Wise card-kiosk-collection API
  description: 'These APIs are designed to allow you to print and encrypt your card directly from a kiosk machine. The card
    information will be sent to our card manufacturer to configure and print the card on-site on a kiosk machine.


    The card printing process will automatically begin once the request is received by our card manufacturer.


    During the printing process, you will be notified via webhook about any [card production status change](/guides/developer/webhooks/event-types#cards-card-production-status-change).


    Before using these APIs, make sure to read the guide on [kiosk collection](/guides/product/issue-cards/card-kiosk-collection#card-kiosk-collection).


    {% admonition type="warning" %}

    Please reach out to your Implementation Manager for more information on these APIs.

    {% /admonition %}


    **Testing**: In the sandbox environment, use the [card production simulation API](/api-reference/simulation/simulationcardproduction)
    to test your integration with various production statuses and error scenarios.


    Production status flow {% .title-2 .m-t-5 %}


    These statuses represent the lifecycle of a card production:


    - `READY` - Card is ready for production. The [produce card endpoint](/api-reference/card-kiosk-collection/cardkioskcollectionproduce)
    can be called.

    - `IN_PROGRESS` - Card is being produced at the kiosk machine (chip encryption and printing in progress).

    - `PRODUCED` - Card has been successfully produced and collected from the kiosk. This is a final state.

    - `PRODUCTION_ERROR` - Card production failed. Check the errorCode to identify the issue, resolve it, then retry using
    the [produce card endpoint](/api-reference/card-kiosk-collection/cardkioskcollectionproduce).


    A card with production status `PRODUCED` will trigger an asynchronous call to update the associated card order to `PRODUCED`
    status.


    ![Card production status flow](/images/diagrams/card-production-status-flow.png)'
  humanURL: https://docs.wise.com/api-docs/api-reference/profile
  baseURL: https://api.wise.com/v2
  tags:
  - card-kiosk-collection
  properties:
  - type: OpenAPI
    url: openapi/wise-card-kiosk-collection-api-openapi.yml
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/profile
  - type: Sandbox
    url: https://api.sandbox.transferwise.tech
  - type: GraphQL
    url: graphql/wise-graphql.md
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/recipient
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/quote
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/transfer
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/balance
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/multi-currency-account
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/balance-statement
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/card
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/subscription
  - type: AsyncAPI
    url: asyncapi/wise-webhooks-asyncapi.yml
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/simulation
- aid: wise:wise-card-order-api
  name: Wise card-order API
  description: 'With this set of APIs, you will be able to create cards for your customers. You can also retrieve and view
    the status of your current card orders, as well as the list of available card programs for the user.


    {% admonition type="info" %}

    On production, each personal profile can order at most 1 physical card and 3 virtual cards. On sandbox, we allow up to
    10 physical cards and 30 virtual cards for testing purpose. However, no more than 3 virtual cards can be ordered per day.
    This limit includes cards and card orders.

    {% /admonition %}


    Card order status flow {% #card-order-status-flow .title-3 .m-t-5 %}


    The card order response will contain the `status` field. The initial status is `PLACED` or `REQUIREMENTS_FULFILLED` depending
    on the requirement fulfillment state:


    - `PLACED` - The card order is created. The card will be generated once it has fulfilled all the requirements

    - `REQUIREMENTS_FULFILLED` - The card order has fulfilled all the requirements and the card should be generated in a short
    while

    - `CARD_DETAILS_CREATED` - The card has been generated

    - `PRODUCED` - The physical card has been produced and waiting to be picked up by delivery vendor (physical card only)

    - `COMPLETED` - The card has been activated and is ready to use. The card order is completed

    - `CANCELLED` - The card order has been cancelled. This can happen if you reach out to Wise Support to cancel a card order

    - `RETURNED` - Delivery failed, the physical card has been returned and will be blocked (physical card only)


    ![Card order status state machine](/images/diagrams/card-order-status-flow.png)'
  humanURL: https://docs.wise.com/api-docs/api-reference/profile
  baseURL: https://api.wise.com/v2
  tags:
  - card-order
  properties:
  - type: OpenAPI
    url: openapi/wise-card-order-api-openapi.yml
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/profile
  - type: Sandbox
    url: https://api.sandbox.transferwise.tech
  - type: GraphQL
    url: graphql/wise-graphql.md
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/recipient
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/quote
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/transfer
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/balance
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/multi-currency-account
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/balance-statement
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/card
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/subscription
  - type: AsyncAPI
    url: asyncapi/wise-webhooks-asyncapi.yml
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/simulation
- aid: wise:wise-card-sensitive-details-api
  name: Wise card-sensitive-details API
  description: 'Wise is a PCI DSS compliant provider and stores all card data securely. The scope for PCI compliance depends
    on your use case and will impact how you integrate. For all sensitive card details endpoints, follow the [detailed guide](/guides/product/issue-cards/sensitive-card-details).


    **Key capabilities:**

    - Access sensitive card data (PAN, CVV, PIN) via encrypted JWE payloads


    **Related operations:**

    - For card management (list, status, permissions), see the [Cards API](/api-reference/card)

    - For ordering new cards, see the [Card Orders API](/api-reference/card-order)

    - For transaction history, see the [Card Transaction API](/api-reference/card-transaction)'
  humanURL: https://docs.wise.com/api-docs/api-reference/profile
  baseURL: https://api.wise.com/v2
  tags:
  - card-sensitive-details
  properties:
  - type: OpenAPI
    url: openapi/wise-card-sensitive-details-api-openapi.yml
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/profile
  - type: Sandbox
    url: https://api.sandbox.transferwise.tech
  - type: GraphQL
    url: graphql/wise-graphql.md
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/recipient
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/quote
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/transfer
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/balance
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/multi-currency-account
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/balance-statement
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/card
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/subscription
  - type: AsyncAPI
    url: asyncapi/wise-webhooks-asyncapi.yml
  - type: Documentation
    url: https://docs.wise.com/api-docs/api-reference/simulation
- aid: wise:wise-card-transaction-api
  name: Wise card-transaction API
  description: "Retrieve information on transactions made on your users' cards.\n\nTransaction types {% #card-transaction-type\
    \ .title-3 .m-t-5 %}\n\nThe possible `type` values are:\n\n- `ACCOUNT_CREDIT` - Receiving money on the card, excluding\
    \ Visa OCT or Mastercard MoneySend\n- `ACCOUNT_FUNDING` - Sending money to another card or e-wallet\n- `CASH_ADVANCE`\
    \ - Cash disbursement\n- `CASH_WITHDRAWAL` - ATM withdrawal\n- `CHARGEBACK` - Currently unused. Reserved for future use\n\
    - `CREDIT_TRANSACTION` - Visa OCT and Mastercard MoneySend\n- `ECOM_PURCHASE` - Online purchase\n- `POS_PURCHASE` - Purchase\
    \ via a POS terminal\n- `REFUND` - Partial or full refund of an existing card transaction\n\nTransaction states {% #card-transaction-state\
    \ .title-3 .m-t-5 %}\n\nThe possible `state` values are:\n\n- `IN_PROGRESS` - The transaction has been authorized but\
    \ not captured\n- `COMPLETED` - The transaction has been captured and/or settled\n- `DECLINED` - The transaction has been\
    \ declined\n- `CANCELLED` - The transaction has been cancelled\n- `UNKNOWN` - Default fallback status if the state cannot\
    \ be confirmed\n\nThe transition from `CANCELLED` to `COMPLETED` is an edge case. Wise releases the customer funds after\
    \ 7 days (30 days for pre-authorization) if the merchant has not captured the transaction, and the state becomes `CANCELLED`.\
    \ However, the merchant can decide to capture the transaction at a later date, at which point the state will become `COMPLETED`.\n\
    \n![Transaction state flow](/images/diagrams/transaction-state-flow.png)\n\nDecline reasons {% #card-transaction-decline-reasons\
    \ .title-3 .m-t-5 %}\n\nThe decline reason field provides information about the specific issue that led to the transaction\
    \ being declined, helping the merchant and the customer troubleshoot the problem.\n\nWhile the decline reason field provides\
    \ valuable information, it may not cover all possible reasons for a decline, such as technical issues or unforeseen circumstances.\n\
    \n{% admonition type=\"warning\" %}\nNew decline reasons may be added in the future, and not all decline reasons are currently\
    \ documented. Review this documentation regularly to ensure accuracy.\n{% /admonition %}\n\n{% admonition type=\"warning\"\
    \ %}\nExercise caution when communicating decline reasons to your customers, as some may not be relevant or may cause\
    \ confusion.\n{% /admonition %}\n\n- `ACCOUNT_INACTIVE` - Balance related to the transaction is not active. Ensure that\
    \ all outstanding actions have been completed before using the card, as this may help avoid potential issues or declines\n\
    - `ACCOUNT_SUSPENDED` - The transaction has been declined pending further compliance checks. It may have been flagged\
    \ for potential sanctions issues\n- `ATM_PIN_CHANGE_NOT_ALLOWED` - PIN change via ATM terminal is not allowed\n- `BLOCKED_COUNTRY`\
    \ - Transactions were made in unsupported countries. Check this [link](https://wise.com/help/articles/2935771/where-can-i-use-my-wise-card)\
    \ to see if the country is included in the list of supported nations. It is possible for a merchant to be based in a supported\
    \ country and have an address registered in a blocked country, albeit infrequently\n- `BLOCKED_SUBSCRIPTION` - The system\
    \ cannot facilitate this transaction as the customer has opted out of recurring payments with this merchant\n- `CARD_EXPIRED`\
    \ - The card provided has reached its expiration date, making it invalid for this transaction\n- `CARD_FROZEN` - The customer\
    \ or the customer service team has put this card on a temporary hold. If the card has not been frozen by the customer,\
    \ it may be worth investigating further. To resume spending, advise the customer to unfreeze the card\n- `CARD_INACTIVE`\
    \ - The card is either not active or has not been received by the customer, so the transaction cannot proceed\n- `CARD_BLOCKED`\
    \ - The card has been blocked and cannot be used anymore\n- `CARD_PARTNER_SUSPENDED` - The internal team has deactivated\
    \ the account for compliance reasons related to AML, fraud, or EDD. Contact the team if this is believed to be an error\n\
    - `CHIP_PIN_ENTRY_TRIES_EXCEEDED` - The PIN is restricted on the chip of the card due to excessive incorrect entries.\
    \ The blocked PIN can be unlocked at an ATM using specific steps that vary depending on the machine and country, such\
    \ as PIN management or PIN operations followed by unblocking the PIN\n- `CONNECTION_ISSUE` - A connection problem occurred\
    \ during the transaction\n- `CONTACTLESS_PIN_ENTRY_REQUIRED` - Contactless payment systems sometimes require a PIN for\
    \ authentication purposes to protect users' accounts from potential fraud or tampering. In Europe, contactless payment\
    \ transactions that follow one after the other require PIN verification as an additional security measure\n- `CREDIT_TRANSACTIONS_NOT_SUPPORTED`\
    \ - Credit is not supported for this specific transaction. Review the [Acceptable Use Policy](https://wise.com/gb/legal/acceptable-use-policy-eea)\
    \ for further information\n- `CUMULATIVE_LIMIT_EXCEEDED` - In certain jurisdictions, there are restrictions on the amount\
    \ that can be spent. Refer to [spending limits](https://wise.com/help/articles/2899986/what-are-my-spending-limits) for\
    \ further details\n- `DECLINED_ADVICE` - There is a problem with the message from the processor, so it might not be accepted\
    \ because it could be incomplete or unsafe. This does not indicate a problem with the card. Advise the customer that there\
    \ was a technical issue with the payment and to try again later\n- `INCORRECT_CVV` - The customer entered the wrong security\
    \ code. Advise the customer to check their card details and try again. If the saved card details are correct, they should\
    \ remove their card details from the merchant's website and add them back again\n- `INCORRECT_EXPIRY_DATE` - The customer\
    \ entered the wrong expiration date for their card. If the saved card details are correct, they should remove their card\
    \ details from the merchant's website and add them back again\n- `INCORRECT_PIN` - The customer entered their PIN incorrectly.\
    \ Advise the customer to check their PIN and try again. If the PIN is correct and still fails, suggest resetting the PIN\n\
    - `INSUFFICIENT_FUNDS` - The customer does not have enough money in their account to make the payment. Advise the customer\
    \ to add money to their account and try again. In most cases, this will resolve the issue\n- `INVALID_3DS_UCAF` - The\
    \ 3D Secure checks failed during the transaction. The customer should try again and request authentication\n- `INCORRECT_ARQC`\
    \ - ARQC (Authorization Request Cryptogram) is a cryptogram generated by the card during a transaction, which is validated\
    \ on the server side. If incorrect, it could indicate a faulty card, a fraudulent attack, or an issue with the POS terminal\n\
    - `INCORRECT_ICVV` - ICVV (Integrated Circuit Card Verification Value) is a security feature used to validate the authenticity\
    \ of a card during chip-based transactions. There were problems reading the chip on the card, which may indicate an issue\
    \ with the card's chip, the terminal, or the transaction process. Wait and try again\n- `INVALID_MERCHANT` - Transaction\
    \ from a specific mercha

# --- truncated at 32 KB (112 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/wise/refs/heads/main/apis.yml