---
title: "account name validation"
method: POST
path: "/cop/account/validate"
tags: ["CoP Account Validations"]
---

# account name validation

`POST /cop/account/validate`

Validates a given name matches a given account.

## Request body

- CopAccountValidationsRequest
  - `uid` string, required — Supplied unique identifier for CoP lookup, maximum 64 characters containing only unreserved characters as defined in RFC3986. This identifier ensures CoP lookup uniqueness between integrator systems and Zepto.
  - `account_identifier` object, required
    - `type` 'bban', required — The type of account identifier
    - `value` string, required — The branch code (BSB) and account number to validate, can be concatenated or separated with a hyphen.
  - `party_name` string, required — The party name to validate against the account
  - `requester` object, required
    - `id` string, required — Merchant provided customer ID for uniquely identifying end user of CoP. Maximum 64 characters containing only unreserved characters as defined in RFC3986.
  - `sandbox` object — SANDBOX ONLY: Parameter that allows you to simulate the confirmation of payee API responses for certain scenarios to aid integrators while testing their control flows. Defaults to `match` if not given.
    - `simulate` 'match' | 'close_match' | 'individual_no_match' | 'non_individual_no_match' | 'account_closed' | 'no_account_found' | 'bic_lookup_failed' | 'account_daily_no_match_limit_exceeded' | 'requester_daily_no_match_limit_exceeded' | 'account_daily_request_limit_exceeded' | 'requester_daily_request_limit_exceeded' | 'unable_to_confirm' | 'rate_limited', required

## Response `200`

OK

- CopAccountValidationsSuccess — Successful validation response
  - `data` object, required
    - `outcome` object, required — The Confirmation of Payee account validation outcome
      - `result` 'match' | 'close_match' | 'no_match' | 'account_closed', required — The matching result, 'match' indicates high confidence, 'close_match' indicates reasonable confidence but with potential variance, 'no_match' indicates the party name could not be confirmed, 'account_closed' indicates the bank account is closed.
      - `match_name` string — The name matched from the Data Holder. This field returns the closest matching name registered for the bank account. This may be an individual name, AKA name, trading name, or a formatted representation. For successful matches on joint accounts, returns in the format "{Name} and others" instead of revealing all account holders when names don't equally match. For privacy reasons, this field is included only for: - Individual accounts: With 'match' and 'close_match' results - Business accounts: With 'match', 'close_match', and 'no_match' results
      - `message` string — Human-readable message with the lookup result. For successful matches, returns in the format "The account is in the name of {match_name}". For privacy reasons, this field is included only for: - Individual accounts: With 'match' and 'close_match' results - Business accounts: With 'match', 'close_match', and 'no_match' results
    - `insights` object — Additional insights about the account and payment recommendations. For privacy reasons, insights is included only for: - Individual accounts: With 'match' and 'close_match' results - Business accounts: With 'match', 'close_match', and 'no_match' results
      - `risk_score` integer — **(Alpha)** Proprietary risk score from 0 to 100, where 100 indicates the highest risk. The score is calculated based on account age, and other factors. This field is only present for 'match' and 'close_match' results.
      - `is_joint` boolean — Indicates whether the account is held jointly by multiple parties.
      - `suggested_payment_channels` string[] — Recommended payment channels for this account based on its capabilities. 'npp.sct' indicates NPP support, 'de.dc' indicates Direct Entry support.
    - `uid` string — Supplied unique identifier for CoP lookup, maximum 64 characters containing only unreserved characters as defined in RFC3986. This identifier ensures CoP lookup uniqueness between integrator systems and Zepto.

## Other responses

- `401` — unauthorized
- `403` — forbidden
- `404` — Not Found
- `422` — Unprocessable Entity
- `429` — Too Many Requests

---

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