---
title: "Verify member"
method: POST
path: "/members/{member_guid}/verify"
tags: ["verification"]
---

# Verify member

`POST /members/{member_guid}/verify`

This endpoint gathers information about account and routing numbers. Partners may optionally choose to transaction data in this request, potentially avoiding a separate aggregate member request.    The verification workflow is similar to standard aggregation. Start the verification, poll the member, answer MFA if necessary by using the list member MFA challenges endpoint and the update member endpoint, poll the status again, then read the member's `account_numbers`.    Before making a request to this endpoint, partners must make sure verification is enabled for the member's `institution`. Specifically, the institution's `supports_account_verification` field must be true.   If the `institution` does not support verification, a `400 Bad Request` error will be returned with the message, `Member's institution does not support instant account verification`.    If a request to this endpoint fails with a status of `403 Forbidden` but the member's `institution` nevertheless shows that verification is enabled, please contact support.

## Path parameters

- `member_guid` string, required

## Response `200`

OK

---

[API](https://skmtc.net/mx/apis/consent-management-v4-api.md) · [All operations](https://skmtc.net/mx/apis/consent-management-v4-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/mx/consent-management-v4-api/revisions/bf6bb86ee0c8/schema)