About profiles

Copy

In the Wise Platform API, a profile is the core resource representing a distinct legal and financial identity. Every transactional resource across the platform—including quotes, recipients, balance accounts, multi-currency account details, and transfers—is scoped to a specific profileId.

Understanding how profiles are structured, linked, and authenticated is essential for building an integration that satisfies global regulatory requirements, sanctions screening, and financial settlement flows.

The profile resource

A profile establishes legal ownership over financial activities within Wise Platform. It decouples the authenticated API caller from the legal entity originating or holding funds.

Wise uses the profileId to:

• Identify the originator of payments
• Enforce KYC/AML rules
• Ensure other resources (like recipients, card tokens, and currency balances) are private to the profile that created them
• Ensure thresholds, volume caps, and enhanced due diligence (EDD) triggers

Profile types

Wise Platform supports two distinct profile types: personal and business

• Personal profiles: Represent a natural person (individual).
  • Key attributes: Full legal name, date of birth, residential address, personal email, phone number, and occupation.
  • Verification scope: Identity document verification (passport, driver's licence, national ID) and proof of residential address.
• Business profiles: Represents a legal entity (Ltd, LLC, etc).
  • Key attributes: Registered company name, registration number, company type (for example, LIMITED_COMPANY, SOLE_TRADER, LLC), registered address, industry classification category codes, and website.
  • Authorised representative relationship: A business entity cannot act on its own behalf. Every business profile must reference an authorised representative (director, controlling person, or account administrator).
  • Verification Scope: Company registry verification, Ultimate Beneficial Owner (UBO) screening, and verification of the authorised representative.

Profiles and integration models

Creating and managing profiles differs depending on your integration model.

Data requirements

Some regions demand more profile data to be compliant with local regulations. Requirements are based on jurisdiction of operation and customer demographics of your bank or other financial institution. We are currently in the process of documenting region-specific profile data requirements. These will be published soon!

Profile verification

Wise is obliged to verify the identity of personal and business profiles as part of our Know Your Customer (KYC) policy. We must be satisfied that we know our customers well enough before conducting financial transactions with them.

For Correspondent and Enterprise partners, Wise verifies the business profile you create during account setup and informs you when the profile is verified and ready to use.

Embedded solutions partners, however, create unique profiles for each of their end users and each of these profiles is subject to KYC verification. How this occurs depends on your KYC approach, as defined in your partner contract. Partners licensed to perform their own KYC verify their customers using their own process. Partners not licensed to perform their own KYC use Wise's customer onboarding flow.

Checking verification status

You can check the verification status of a profile using two methods:

• Subscribe to the verification state change webhook to be notified when a profile status has changed.
• Send a request to the Check profile verification status endpoint.

Verification state change webhook

Create an application webhook subscription with the trigger_on value set to profiles#verification-state-change.

curl -i -X POST \
  'https://api.wise.com/2026Q3/applications/{clientKey}/subscriptions' \
  -H 'Authorization: Bearer <YOUR_JWT_HERE>' \
  -H 'Content-Type: application/json' \
  -H 'X-External-Correlation-Id: f47ac10b-58cc-4372-a567-0e02b2c3d479' \
  -d '{
    "name": "Profile verification check",
    "trigger_on": "profiles#verification-state-change",
    "delivery": {
      "version": "4.0.0",
      "url": "https://your.webhook.url/12345"
    }
  }'

Listen for the webhook payload:

{
  "schema_version": "4.0.0",
  "subscription_id": "01234567-89ab-cdef-0123-456789abcdef",
  "event_type": "profiles#verification-state-change",
  "sent_at": "2026-01-01T12:34:56.123Z",
  "data": {
    "resource": {
      "type": "profile",
      "id": 111
    },
    "current_state": "verified",
    "occurred_at": "2026-01-01T12:34:56.789Z"
  }
}

Check profile verification status

This request returns the verification status of a profile when funding with a bank transfer. It specifies the verification status for each route queried in the response (via the source_currencies query parameter).

Verification status is an indicator of the current level of verification that has been made for a profile to some particular level of confidence: a level that is likely to allow money transfers to occur without being delayed by verification-related issues.

curl -i -X POST \
  'https://api.wise.com/2026Q3/profiles/{profileId}/verification-status/bank-transfer?source_currencies=GBP%2CUSD%2CEUR' \
  -H 'Authorization: Bearer <YOUR_JWT_HERE>' \
  -H 'X-External-Correlation-Id: f47ac10b-58cc-4372-a567-0e02b2c3d479'

Understanding the response:

The current_status field:

• verified: The profile is sufficiently verified to start making payments.
• not_verified: The profile is currently awaiting verification or there are pending issues with the verification process.