CoP Verification Results

The result of a CoP verification is returned on the payment instrument's details.verification object. This guide covers the verification statuses, the shape of the verification object, and how to interpret each possible outcome.

This guide covers:

1. Verification Status: Tracking the state of a verification
2. Verification Object: The shape and fields of the verification result
3. Match Results: How to interpret match, close_match, and no_match
4. Verification Errors: What to do when verification cannot be completed

Verification StatusCopy URL

The details.verification.status field reflects the current state of the verification process:

Verification ObjectCopy URL

When verification has been initiated, the details.verification object is present on the payment instrument resource:

{
  "verification": {
    "status": "completed",
    "result": "match",
    "registered_account_name": "Jane Smith",
    "verified_at": "2025-12-02T16:35:01.987654Z",
    "method": "cop"
  }
}

Match ResultsCopy URL

When status is completed, the registered_account_name field contains the closest matching name returned by the financial institution. This may be an individual name, trading name, or AKA. For joint accounts where names do not equally match, it returns as "{name} and others". Some financial institutions may omit this field for privacy reasons.

MatchCopy URL

Meaning: The name provided very closely matches the name registered on the account. The match threshold allows for minor variations (a transposed letter or hyphenation difference, for example), so names like "Johnathan Smith" (provided) and "Jonathan Smith" (registered), or "Sarah-Jane Lee" and "Sarah Jane Lee", may still return match.

What you receive:

{
  "verification": {
    "status": "completed",
    "result": "match",
    "registered_account_name": "Jane Smith",
    "verified_at": "2025-12-02T16:35:01.987654Z",
    "method": "cop"
  }
}

Recommended action: Proceed with the payout. The account details are confirmed.

Close MatchCopy URL

Meaning: The name is similar but not identical. Common causes include spelling errors, shortened names, missing middle names, and formatting differences. For example, "Jane Smith" (provided) and "Jane A Smith" (registered), or "J P Richards" and "John-Paul Richards".

What you receive:

{
  "verification": {
    "status": "completed",
    "result": "close_match",
    "registered_account_name": "Jane A Smith",
    "verified_at": "2025-12-02T16:35:05.123456Z",
    "method": "cop"
  }
}

Recommended action: Review the registered_account_name (if returned) for discrepancies and confirm the account details with the intended recipient before proceeding.

No MatchCopy URL

Meaning: The names do not meaningfully align. The name provided bears no sufficient resemblance to the name registered against this account.

What you receive:

{
  "verification": {
    "status": "completed",
    "result": "no_match",
    "verified_at": "2025-12-02T16:35:08.654321Z",
    "method": "cop"
  }
}

Recommended action: Do not proceed with the payout without investigating further. A no_match result typically means one of:

• The BSB and/or account number belong to a different person than intended
• The account owner name provided is incorrect
• The recipient supplied incorrect account details

Contact the intended recipient to confirm their details before retrying. If the details have changed, create a new payment instrument with the corrected information and run verification again.

Verification ErrorsCopy URL

When status is failed, the verification process itself could not complete — it does not mean the account details are incorrect. This is distinct from no_match, where the check completed but the names did not align.

What you receive:

{
  "verification": {
    "status": "failed",
    "method": "cop",
    "latest_error": {
      "code": "ACCOUNT_VERIFICATION_SERVICE_UNAVAILABLE",
      "message": "Account verification service unavailable"
    }
  }
}

Recommended action: Check latest_error.code and act accordingly:

If the issue persists, contact support@banked.com.

Next StepsCopy URL

• CoP Webhooks - Full webhook payload reference for all CoP outcomes
• Getting Started with CoP - Step-by-step implementation guide