---
title: "Verify an External Account"
method: POST
path: "/customers/{customerID}/external_accounts/{externalAccountID}/verify"
tags: ["External Accounts"]
---

# Verify an External Account

`POST /customers/{customerID}/external_accounts/{externalAccountID}/verify`

Trigger a verification check for an external account. Verifies that the `account_owner_name` matches the actual account holder at the receiving bank.

Supported for `iban` (EUR) and `gb` (GBP) account types only. Does not require an Idempotency-Key header.

After triggering, poll the external account's `account_verification` field until `completed_at` is populated.

## Path parameters

- `customerID` string, required — A UUID that uniquely identifies a resource
- `externalAccountID` string, required — A UUID that uniquely identifies a resource

## Response `200`

Verification initiated successfully

- object
  - `account_type` 'iban' | 'gb' — The account type that was verified.
  - `account_verification` object — The current state of the verification.
    - `iban` object — Present when verifying an IBAN account.
      - `match_level` 'pending' | 'match' | 'close_match' | 'no_match' | 'error' — The result of the name match check.
      - `reason_code` string, nullable — Additional context from the receiving bank when the result is not a full match.
      - `validated_account_owner_name` string, nullable — The name on file at the receiving bank.
    - `gb` object — Present when verifying a GB account.
      - `match_level` 'pending' | 'match' | 'close_match' | 'no_match' | 'error' — The result of the name match check.
      - `reason_code` string, nullable — Additional context from the receiving bank when the result is not a full match.
      - `validated_account_owner_name` string, nullable — The name on file at the receiving bank.
    - `requested_at` string, date-time — When the verification was requested.
    - `completed_at` string, date-time, nullable — When the verification completed. Null while pending.

## Other responses

- `400` — Request containing missing or invalid parameters.
- `401` — Missing or invalid API key
- `404` — No resource found
- `409` — A verification is already in progress for this external account
- `500` — Unexpected error. User may try and send the request again.

---

[API](https://skmtc.net/bridge/apis/bridge-api.md) · [All operations](https://skmtc.net/bridge/apis/bridge-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/bridge/bridge-api/revisions/570998bde3b5/schema)