Can anyone confirm that the Wise integration is working or if any additional setup required from Wise itself?
I’ve followed the Wise node documentation | n8n Docs and also created a private key (included in n8n credentials) with it’s public key included in my Wise account API keys.
Triggers don’t work at all, any test returns “Wise Trigger: Forbidden”. I understand I do not need to define the URL as a webhook in Wise account, but even so tried but does not validate there either.
On the Actions i can do some actions… rate exchange, account balance, etc but “statements” returns:
Error signing SCA request, check your private key
ERR_OSSL_UNSUPPORTED
Which sounds with a n issue with the double verification process which likely requires me to do a request to Wise, but my main issue now is the triggers.
I was hoping to keep a google sheet auto updated statement.
Based on what I can see from the n8n documentation, Wise Triggers are available and supported, but they depend on the same Wise credentials used for actions, including the Strong Customer Authentication (SCA) component.
Why Forbidden (403): the endpoint requires SCA and n8n couldn’t authenticate correctly. This explains why simple actions like balance or exchange rate work, while triggers and “statements” fail.
Why Error signing SCA request / ERR_OSSL_UNSUPPORTED: This points to a problem with the private key used to sign the SCA request. According to the documentation, the only officially supported format is:RSA 2048 key pair / Generated via openssl / Plain PEM, without a passphrase / public.pem registered in Wise / private.pem pasted in full into the n8n credentials
Any variation from this (different algorithm, password-protected key, altered PEM, or OpenSSL incompatibility in the Docker image) can cause exactly this error.
If you regenerate the keys exactly as described in the docs and the error continues, then it’s worth raising this as a possible incompatibility between version 1.122.5 and OpenSSL in Docker.
Hi @luison Welcome!
Just regenerate and import a valid RSA 2048 plain PEM key pair for your Wise credentials to fix it. As wise demands a fix schema so just revoke your existing credentials
I uploaded the public key to wise and private copied (with comment) to n8n, situation remained.
The original API key was “read only” as I only want to keep a track of the account, but for some reason I am guessing it has to be made as “Full Access”. Switching that seems to have made the triggers now available (still testing/building) alltough the same (ERR_OSSL_UNSUPPORTED) remains on the statements action. Other (I guess non SCA actions) work. Wise indicates when enabling Full Access:
Due to PSD2 compliance, funding transfers is restricted with API Tokens. If you need to fund via the API, please reach out to us.
I don’t see why this should affect “statements” but it might. I also don’t get why triggers require Full Access key either, but I did try setting up standard webhooks and I never managed for Wise to validate the n8n endpoints.
It’s a shame they (Wise) don’t allow a more personalized access to API key permissions. In my case I would be much more comfortable having a Read Only key just to maintain my DB or sheet updated.