To clear a PIN challenge listed in a OTT.
Notes:
- User is required to create pin before the verification can be successful.
- Rate limit may be applied if there are 5 continuous unsuccessful attempts and OTT creation will be blocked for 15 minutes.
Security
UserToken
Optional UUID for correlating requests across systems. If provided, Wise echoes it back in the response. Maximum 36 characters. Learn more.
Example:f47ac10b-58cc-4372-a567-0e02b2c3d479
- Production Environmenthttps://api.wise.com/v1/one-time-token/pin/verify
- Sandbox Environmenthttps://api.wise-sandbox.com/v1/one-time-token/pin/verify
curl -i -X POST \
https://api.wise-sandbox.com/v1/one-time-token/pin/verify \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Accept: application/jose+json' \
-H 'Accept-Encoding: identity' \
-H 'Content-Type: application/jose+json' \
-H 'Content-Encoding: identity' \
-H 'X-TW-JOSE-Method: jwe' \
-H 'One-Time-Token: <one time token>' \
-d 'eyJlbmMiOiJBMjU2R0NNIiwi...'Encrypted one time token status.
Headers
Echoed back when X-External-Correlation-Id was included in the request. Learn more.
Example:"f47ac10b-58cc-4372-a567-0e02b2c3d479"
string
JWE-encrypted string. Please refer to our JOSE guide on how to decrypt this.
When decrypted, the response contains oneTimeTokenProperties with the one time token details.
Response
"eyJlbmMiOiJBMjU2R0NNIiwi..."