Wise

Wise integration connects your Wise multi-currency account to Sure using a personal API token. Sure syncs your currency balances, Jars (savings pots), transfers, and Wise Assets activity directly from the Wise API — no OAuth flow required.

​

How it works

1. You create a personal API token in Wise and paste it into Sure
2. Sure fetches the profiles (personal and/or business) available to that token
3. You choose which profile(s) to connect — each becomes its own connection in Sure
4. Sure discovers every currency balance and Jar under the connected profile(s)
5. You link each discovered balance to a new or existing Sure account
6. Syncs then run automatically, pulling balances, transfers, and Jar activity

​

Setting up Wise

1. Sign in to your Wise business account at wise.com (personal API tokens are issued from business account settings, even if you’re only connecting a personal profile)
2. Go to Your Account → Connect and manage apps → API tokens (requires two-factor authentication on the account)
3. Create a new personal API token and choose an access level: read only lets Sure read balances, transfers, and Jar activity; full additionally allows the token to authorize recipients and transfers, so prefer read-only unless you need that capability elsewhere
4. In Sure, go to Settings > Providers, find the Wise panel, and paste the token
5. If the token has access to more than one profile (for example, a personal and a business profile), select which ones to connect — Sure creates a separate connection for each
6. Open Set Up Accounts on the new connection and link each currency balance to a Sure account
7. To enable full transaction history including incoming payments, complete the SCA setup below

​

Features

​

Multi-currency balances

• Standard balances: one balance per currency held in your Wise account, refreshed (including reserved amount) on every sync
• Jars (savings pots): synced alongside standard balances and mapped to a savings-type account in Sure
• New balances discovered on a sync are shown as “needs setup” until linked to a Sure account

​

Transaction syncing

• The first sync imports history from the date you configure (or 365 days by default); later syncs use a 7-day lookback from the last successful sync
• Transactions are fetched from the Wise balance-statement endpoint, which covers both incoming and outgoing payments. The statement endpoint requires SCA — without it, Sure falls back to the outgoing-only transfers endpoint, so incoming payments will be missing until SCA is configured
• Transfers are matched to their linked balance by Wise balance ID, so Jars that share the same currency are still tracked as separate accounts
• Cross-currency incoming transfers use the amount actually received, not the amount sent
• When a same-currency transfer includes a fee, the fee is imported as a separate “Wise fee” transaction

​

Jar activity

• Deposits and withdrawals to a Jar are imported as “Transfer to Jar” / “Transfer from Jar” transactions
• Interest and Wise Assets fees are imported automatically
• Transfers between a standard balance and a Jar are automatically linked as Sure Transfers, so the same movement is never double-counted as separate income and expense

​

Multiple profiles

If your Wise account has both personal and business profiles, you can connect several profiles from the same token at once. Each profile is a separate connection that can be synced, updated, or disconnected independently.

​

Strong Customer Authentication (SCA)

Wise requires Strong Customer Authentication on the balance-statement endpoint. SCA uses an RSA keypair: Sure signs a one-time challenge with the private key, and Wise verifies it against the public key you register in your Wise account. Without SCA, the statement endpoint returns 403 and Sure falls back to the outgoing-only transfers endpoint, so incoming payments will not appear.

​

Enabling SCA

1. In Sure, go to Settings > Providers and open the Wise panel for the connection
2. Click Generate SCA keypair — Sure creates a 2048-bit RSA keypair and stores the private key encrypted at rest
3. Copy the public key that appears in the panel
4. In Wise, go to Your Account → Connect and manage apps → API tokens → Public keys and paste the public key
5. Run a sync — the statement endpoint should now succeed and incoming payments will be imported

​

Troubleshooting SCA

Incoming payments are missing: SCA is not yet configured or the public key has not been registered with Wise. Follow the steps above. Statement fetch fails after configuring SCA: confirm the public key in Wise matches the one shown in the Sure Wise panel. If the key was regenerated, the old public key must be removed from Wise and the new one registered.

​

Limitations

• Uses a Wise personal API token rather than OAuth; the token carries whatever account access you grant it in Wise
• Wise Assets (investment) balances are not tracked as accounts — only fees charged against them are imported
• Each discovered currency balance must be linked to a Sure account manually after the first sync; balances aren’t created automatically
• Incoming payments only sync after SCA is configured

​

Troubleshooting

Invalid token / connection requires update: your API token was revoked, is invalid, or lacks permissions (Wise personal API tokens don’t expire on their own). Create a new personal token in Wise and update it in the Wise provider panel. No profiles found: the token doesn’t have access to any Wise profile. Check the token’s permissions in Wise and try again. A currency balance is missing: run a sync, then check Set Up Accounts on the connection — new balances only become Sure accounts once you link them. Incoming payments are missing: the balance-statement endpoint requires SCA. Follow the SCA setup steps to generate a keypair and register the public key with Wise.