Creating an account

Copy

Getting started as a Correspondent or Enterprise partner

All Wise Platform partners must have an account with a business profile. How these accounts get created differs depending on your integration model.

• Correspondent
  Correspondent partner

  The term used to refer to Wise Platform partners who are regulated financial institutions using the Wise infrastructure to facilitate international transactions on behalf of their customers.
  and Enterprise
  Enterprise partner

  The term used to refer to enterprise-level businesses who use Wise Platform to manage their own funds in their Wise business account.
  partners start by creating an account and adding a business profile.
• For Embedded Solution
  Embedded finance

  The term used to refer to regulated financial institutions and fintech platforms who offer Wise services to their customers by embedding Wise features and capabilities directly into their applications. Sometimes called Embedded partners or Embedded integrations.
  partners, accounts are provisioned internally due to their unique configuration needs.

Methods

You can create your Wise account and related profiles either via API or via the Wise.com interface. Each method has a specific OAuth grant flow for obtaining user tokens.

• API method: Uses the registration code grant flow to obtain user tokens. This method is best for fully automated, headless integrations where you programmatically obtain credentials and tokens, providing the best level of security overall.
• Wise.com method: Uses the authorisation code grant flow to obtain user tokens. This method is best for partners who prefer to create their account interactively through the Wise web interface.

Your implementation team will help you decide which path best fits your business and integration needs.

Select your preferred method below for step-by-step instructions:

Requirements

• Client credentials are required for both account setup methods.
• A redirect URI, if using the authorisation code grant flow.
• Multiple pieces of data about the business and its representatives to create the profile.

Review this section thoroughly to ensure you have the necessary information before you begin.

Client credentials

Your client_id and client_secret are issued by your implementation team and are scoped to your specific integration. Visit the Developer Hub to access your client credentials at any time.

If you are currently testing with sandbox credentials, be sure to access the sandbox Developer Hub instead.

Redirect URI

The redirect URI is the registered callback URL for the authorisation code flow (not necessary if using the registration code flow).

For Correspondent partners, Wise issues a dummy redirect URI solely for the purpose of providing the authorisation code during the redirect step.

Business profile details

All partner integrations require, at minimum, the following data points to create a business profile:

Business representative (authorised signatory):

• Full legal name (first name, last name)
• Date of birth
• Residential address (state code required for US, CA, BR, and AU addresses)
• Contact email address
• Phone number (with international prefix)

The person your organization designates as the business representative should be someone considered an authorised signatory. This could be a director, executive officer, or other senior leader in your organization. Your implementation team can help you determine the appropriate individual.

The representative's details are submitted as part of the business profile creation request, rather than as a separate personal profile.

Business profile:

• Legal business name
• Business registration number
• Company type (from an enumerated list)
• Company role of the person creating the profile (OWNER, DIRECTOR, or OTHER)
• Registered business address
• Business industry categories (see Business categories)
• Operational address(es)
• Business webpage
• An actively monitored email address for handling Requests for Information (RFIs)

Business directors and ultimate beneficial owners (UBOs):

• Full name, date of birth, and country of residence (ISO3 code) for each director
• Full name, date of birth, country of residence (ISO3 code), address, and ownership percentage for each UBO

If you are uncertain about who to identify as business directors or UBOs, consult with your implementation team for assistance.

Environments

For each environment, sandbox and production, we offer an endpoint that requires mutual TLS (mTLS) and a separate endpoint for non-mTLS. For most situations we recommend using mTLS, which requires some additional setup.

During development, you’ll follow the setup steps in the sandbox environment with your sandbox credentials. Once ready to move into production, you’ll follow the same steps in the production environment.

The sandbox environment may be made available prior to an executed partnership agreement, and your onboarding team will issue sandbox-specific credentials to you.

Postman collection