You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As far as I can see this breaks many methods in this library when SCA is required. A basic solution might be to support passing the correct headers to the methods to support manually handling this signatures and retires. It would be great if the library was able to automatically handle retries and signing.
The text was updated successfully, but these errors were encountered:
I have been looking at implementing this feature but I failed to replicate the 403 error that gives the one-time token either with my sandbox account or my live account. So I don't really know how to test the feature once implemented. If you've managed to reproduce the OTT demand I'll be interested to know how you did it.
Recent changes implement new strong customer authentication rules which sometimes require attaching signatures to requests.
https://api-docs.transferwise.com/#payouts-guide-strong-customer-authentication
As far as I can see this breaks many methods in this library when SCA is required. A basic solution might be to support passing the correct headers to the methods to support manually handling this signatures and retires. It would be great if the library was able to automatically handle retries and signing.
The text was updated successfully, but these errors were encountered: