---
title: "Verify a Merchant"
method: POST
path: "/merchants/{merchant_id}/verifications"
tags: ["Merchants"]
---

# Verify a Merchant

`POST /merchants/{merchant_id}/verifications`

Create a `Verification` on a Merchant to get them Approved. This request will create a new `PENDING` Verification. Listen to updates and re-fetch the Verification when it is `SUCCEEDED` or `FAILED`.

For handling `FAILED` Verifications, see [Fetch a Verification](/api/verifications/getverification). See also [Onboarding Process](/guides/platform-payments/onboarding-sellers/seller-onboarding-process) for Seller Merchants and [Verification Requirements for Payouts](/guides/payouts/recipient-verification-process) for Recipient Merchants.

## Headers

- `Finix-Version` string
- `Content-Type` string

## Request body

- object

## Response `201`

A Merchant Verification

- MerchantVerification
  - `id` string — The ID of the resource.
  - `created_at` string, date-time — Timestamp of when the object was created.
  - `updated_at` string, date-time — Timestamp of when the object was last updated.
  - `application` string — ID of the `Application` the resource was created under.
  - `identity` string, nullable — The ID of the `Identity` used to create the `Merchant`.
  - `merchant` string — The ID of the `Merchant` sent for verification.
  - `merchant_identity` string — The `Identity` ID associated with the `Merchant`.
  - `messages` string[] — A codified list of reasons the verification request failed.
  - `outcome_summary` string — A message providing additional context about why the verification request failed, available for `SELLER` merchants only.
  - `outcomes` object[] — A codified list of reasons the verification request failed, available for `SELLER` merchants only.
  - `payment_instrument` string — This field is not applicable to merchant verification.
  - `payment_instrument_verification_details` object — This object is not applicable to merchant verification.
    - `pull_from_card_cross_border` string, nullable — This object is not applicable to merchant verification.
    - `pull_from_card_domestic` string, nullable — This object is not applicable to merchant verification.
    - `push_to_card_domestic` string, nullable — This object is not applicable to merchant verification.
    - `push_to_card_cross_border` string, nullable — This object is not applicable to merchant verification.
    - `card_type` string, nullable — This object is not applicable to merchant verification.
    - `billing_currency` string, nullable — This object is not applicable to merchant verification.
    - `issuer_country` string, nullable — This object is not applicable to merchant verification.
  - `processor` 'FINIX_V1' | 'DUMMY_V1' — Name of the verification processor.
  - `raw` union — Raw response from the processor. For `SELLER` Merchants, please use the newer `outcomes` and `outcome_summary` fields.
    - object, nullable
    - string, nullable
  - `state` 'PENDING' | 'FAILED' | 'SUCCEEDED' — The state of the verification request.
  - `tags` Tags, nullable — Include up to 50 `key: value` pairs to annotate requests with custom metadata. - Maximum character length for individual `keys` is 40. - Maximum character length for individual `values` is 500. (For example, `order_number: 25`, `item_type: produce`, `department: sales`)
  - `trace_id` string — An ID used for tracking the verification request.
  - `type` 'MERCHANT' — Details the type of resource getting verified.
  - `sub_type` 'CYBERSOURCE', nullable — Specifies the [Gateway Integration](/api/gateway-integrations) linked to the [Merchant](/api/merchants). If the merchant is not linked to a `Gateway Integration`, this field will be `null`. At this time, `CYBERSOURCE` is the only supported `Gateway Integration`.
  - `_links` object — For your convenience, every response includes several URLs which link to resources relevant to the request. You can use these `_links` to make your follow-up requests and quickly access relevant IDs.
    - `self` object — Link to the `Verification`.
      - `href` string
    - `merchant` object — Link to the `Merchant` sent in the verification request.
      - `href` string
    - `application` object — Link to the `Application` associated with this resource.
      - `href` string

## Other responses

- `400` — Bad Request. The server cannot process the request due to malformed syntax or invalid data.
- `401` — Unauthorized. Authentication is required and has failed or has not been provided.
- `403` — Forbidden. The client is authenticated but does not have permission to access the resource.
- `406` — Not Acceptable. The server could accept the submitted request. Confirm how the request was formatted and submitted.

---

[API](https://skmtc.net/finix/apis/finix-api-reference.md) · [All operations](https://skmtc.net/finix/apis/finix-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/finix/finix-api-reference/versions/67e4dc871bfc/schema)