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 evidences that can be found in the [Supported Evidences guide](/guides/product/kyc/partner-kyc/supported-evidences).If you use the [Customer Account with Partner KYC](/guides/product/kyc/partner-kyc) model and your customers are primarily based in the EU,refer to this [Onboarding EU customers](/guides/product/kyc/partner-kyc/additional-verification#onboarding-eu-customers) guidefor instructions on how to use these APIs.If you use the [Customer Account with Partner KYC](/guides/product/kyc/partner-kyc) model and you are onboarding high risk business customersbased primarily based in the US, refer tothis [Onboarding High Risk US Businesses](/guides/product/kyc/partner-kyc/additional-verification#onboarding-high-risk-us-businesses) guide for instructions on how to use these APIs.
Wise verification API is one of 47 APIs that Wise publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.
Tagged areas include verification. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an AsyncAPI specification.
This API exposes 4 operations across 4 paths. It is described by OpenAPI 3.1.0.
Requests are made against 2 base URLs: https://api.wise.com, https://api.wise-sandbox.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 4
Wise verification API declares
4 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (UserToken).
It accepts HTTP bearer tokens (JWT) (PersonalToken).
It accepts HTTP bearer tokens (JWT) (ClientCredentialsToken).
It accepts HTTP basic authentication (BasicAuth).
UserToken— User Access Token for making API calls on behalf of a Wise user. Can be obtained via two OAuth 2.0 flows: - registrationcode grant: For partners creating users…PersonalToken— Personal API Token for individual personal or small business users. Generated from Wise.com Settings Connect and manage apps API tokens. Has limited API access…ClientCredentialsToken— Application-level token for partner operations that don't require a specific user context, such as bulk settlement and card spend controls. Obtained via POST /…BasicAuth— Basic Authentication using your Client ID and Client Secret as the username and password. Client credentials are provided by Wise when your partnership begins.…
Paths & Operations 4
Across 4 paths, the API surfaces 4 operations — 1 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.
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 evid…
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Wise 12
Other APIs Wise publishes across the network.