---
title: "validate"
method: POST
path: "/v1/validate"
tags: ["Login"]
---

# validate

`POST /v1/validate`

The second part of login involves validating using an MFA device

An access token with PRE\_AUTH authorities is required

## Headers

- `Authorization` string

## Request body

- AccessTokenValidationRequest
  - `otp` string, required — an OTP either sent via sms or generated by a registered MFA device

## Response `200`

User request has been validated

- AccessTokenResponse
  - `access_token` string — Bearer token used in headers to access secure endpoints
  - `token_type` string — the type of the token
  - `refresh_token` string — can be used to obtain a new access token
  - `expires_in` integer — The lifetime in seconds of the access token
  - `scope` string — the scope of the access token
  - `user_info` UserInfo
    - `user_id` string, uuid — the id of the user
    - `userType` 'BACKOFFICE' | 'PAYOR' | 'PAYEE'
    - `mfa_details` MFADetails
      - `mfa_type` 'SMS' | 'YUBIKEY' | 'TOTP', nullable — The type of the MFA device
      - `verified` boolean — true if the user has used the MFA device for login
  - `entityIds` string[] — If the user is a payee then the payeeId<P> If the user is a payor then the payorId

## Other responses

- `401` — Invalid access token. May be expired or invalid
- `403` — The authentication does not have permissions to access the resource This usually occurs when there is a valid authentication instance (client or user) but they do not have the required permissions

---

[API](https://skmtc.net/velopaymentsapi/apis/velo-payments-apis.md) · [All operations](https://skmtc.net/velopaymentsapi/apis/velo-payments-apis/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/velopaymentsapi/velo-payments-apis/revisions/05c3f09fc50a/schema)