# Get verification of payee by ID

Retrieve details of a specific verification of payee by its unique identifier

Endpoint: GET /v1/verifications_of_payee/{id}
Version: 1.0

## Path parameters:

  - `id` (string, required)
    The unique identifier of the verification of payee
    Example: "123e4567-e89b-12d3-a456-426614174000"

## Response 200 fields (application/json):

  - `id` (string, required)
    Solaris UID for the verification of payee
    Example: "123e4567e89b12d3a456426614174000veop"

  - `payee` (object, required)
    The payee information that was verified

  - `payee.iban` (string, required)
    The IBAN of the payee
    Example: "DE89370400440532013000"

  - `payee.name` (string, required)
    The name of the payee
    Example: "John Doe"

  - `result` (object, required)
    The result of the verification of payee

  - `result.status` (string, required)
    The status of the verification of payee
    Enum: "MATCH", "NO_MATCH", "CLOSE_MATCH", "VERIFICATION_NOT_POSSIBLE", "VERIFICATION_NOT_SUPPORTED"

  - `result.suggested_name` (string)
    Suggested correct name when there is a close match but not exact
    Example: "John M. Doe"

  - `created_at` (string, required)
    The timestamp when the verification was created
    Example: "2025-04-16T12:34:56Z"

  - `expires_at` (string, required)
    The timestamp when the verification expires
    Example: "2025-04-16T12:39:56Z"

  - `used_for` (object)
    The process the verification was used for. Will be present only if verification was already used for a process (e.g. SEPA_CREDIT_TRANSFER).

  - `used_for.type` (string)
    The type of process the verification was used for.
    Enum: "SCT", "SCT_INSTANT", "SCHEDULED_SCT", "SCHEDULED_SCT_INSTANT", "BATCH_SCT", "BATCH_SCT_INSTANT"

  - `used_for.id` (string)
    The unique identifier of the process (e.g. transaction identifier)
    Example: "f874b3102718a4d757a6b6e4d5996078sctx"

  - `used_for.timestamp` (string)
    The timestamp when the verification was used
    Example: "2025-04-16T12:36:30Z"

## Response 404 fields (application/json):

  - `errors` (array, required)
    Example: [{"id":"b805c37f-75e9-4445-974c-12d28e7584ee","status":404,"code":"model_not_found","title":"Model Not Found","detail":"Couldn't find 'Account' for id '??????????acc'."}]

  - `errors.id` (string)
    A unique identifier for this error message.
    Example: "b805c37f-75e9-4445-974c-12d28e7584ee"

  - `errors.status` (integer)
    The HTTP status code of the response (typically in the range 4xx–5xx).
    Example: 400

  - `errors.code` (string)
    A machine-readable representation of the error type.
    Example: "invalid_json"

  - `errors.title` (string)
    The human-readable name of the error type.
    Example: "Invalid JSON"

  - `errors.detail` (string)
    A human-readable description of the error.
    Example: "The provided JSON was not properly formatted."

## Response 500 fields (application/json):

  - `errors` (array, required)
    Example: [{"id":"b805c37f-75e9-4445-974c-12d28e7584ee","status":500,"code":"generic_error","title":"Generic Error","detail":"There was an error."}]

  - `errors.id` (string)
    A unique identifier for this error message.
    Example: "b805c37f-75e9-4445-974c-12d28e7584ee"

  - `errors.status` (integer)
    The HTTP status code of the response (typically in the range 4xx–5xx).
    Example: 400

  - `errors.code` (string)
    A machine-readable representation of the error type.
    Example: "invalid_json"

  - `errors.title` (string)
    The human-readable name of the error type.
    Example: "Invalid JSON"

  - `errors.detail` (string)
    A human-readable description of the error.
    Example: "The provided JSON was not properly formatted."