You can use these credentials to authenticate the following nodes:
  • Wise
  • Wise Trigger

​
Prerequisites

Create a Wise account.

​
Supported authentication methods

  • API token
Refer to Wise’s API documentation for more information about the service.

​
Using API token

To configure this credential, you’ll need:
  • An API Token: Go to your user menu > Settings > API tokens to generate an API token. Enter the generated API key in your credential. Refer to Getting started with the API for more information.
  • Your Environment: Select the environment that best matches your Wise account environment.
    • If you’re using a Wise test sandbox account, select Test.
    • Otherwise, select Live.
  • Private Key (Optional): For live endpoints requiring Strong Customer Authentication (SCA), generate a public and private key. Enter the private key here. Refer to Add a private key for more information.
    • If you’re using a Test environment, you’ll only need to enter a Private Key if you’ve enabled Strong Customer Authentication on the public keys management page.

​
Add a private key

Wise protects some live endpoints and operations with Strong Customer Authentication (SCA). Refer to Strong Customer Authentication & 2FA for details. If you make a request to an endpoint that requires SCA, Wise returns a 403 Forbidden HTTP status code. The error returned will look like this:
This request requires Strong Customer Authentication (SCA). Please add a key pair to your account and Stigg credentials. See https://api-docs.transferwise.com/#strong-customer-authentication-personal-token
To use endpoints requiring SCA, generate an RSA key pair and add the relevant key information to both Wise and Stigg:
  1. Generate an RSA key pair: 
    $ openssl genrsa -out private.pem 2048 
$ openssl rsa -pubout -in private.pem -out public.pem
  2. Add the content of the public key public.pem to your Wise user menu > Settings > API tokens > Manage public keys.
  3. Add the content of the private key private.pem in Stigg to the Private Key (Optional).
Refer to Personal Token SCA for more information.