---
title: "VOP / CoP Providers"
url: "https://dev.ionova.ai/solutions/vop-cop"
image: "https://dev.ionova.ai/_og/d/c_Ocean.takumi,title_~Vk9QIC8gQ29QIFByb3ZpZGVycw,props_eyJ0aGVtZSI6eyJtb2RlIjoibGlnaHQiLCJjb2xvcnMiOnsicHJpbWFyeSI6IiMyRTUwOTAifX19,p_Ii9zb2x1dGlvbnMvdm9wLWNvcCI,s_lr1McDEpGCke3FoK.png"
---

[Docs](https://dev.ionova.ai/) › [Solutions](https://dev.ionova.ai/solutions) › VOP / CoP Providers

Provider & rails

# Add an address-quality verdict to every _payee check_.

A name + account match tells your customer the payee is real. It says nothing about whether the address will clear the network on 15 Nov 2026. That gap is a verdict you can return — one field, one endpoint.

**The hinge —** the _false green light_: a payee passes your check, the payment is built on that confidence, and it bounces on an address your product never inspected. ARS turns a presence commodity into a payment-success predictor.

Where you call _ARS_The narrowest integration in the catalogue.

|                |                                                                       |
| :------------- | :-------------------------------------------------------------------- |
| Placement      | At-Source                                                             |
| Scope          | Party Address only (Data) — 7 of 27 endpoints, zero messages to build |
| Channel preset | cop-verify                                                            |
| Pattern        | Fail-open ride-along inside your existing CoP / VOP response          |
| Verdict        | COMPLIANT / HYBRID / NON_COMPLIANT + a cited reason code              |

Your channel _preset_Address-level structural checks only — pre-check by nature.

```json
{
  "channelName": "cop-verify",
  "channelSelection": {
    "channel": "api", "direction": "INBOUND", "pspCountry": "GB", "timezone": "Europe/London"
  },
  "preferences": { "quality": "standard", "targetFormat": "auto" }
}
```

Endpoints you'll _use_Two looking operations plus a light normalise.

| Endpoint                     | Does                                                                   |
| :--------------------------- | :--------------------------------------------------------------------- |
| EP-03 Check Party Address    | Return an address-quality verdict alongside your name / account match. |
| EP-06 Classify Party Address | Detect the format (structured / hybrid / unstructured).                |
| EP-01 Process Party Address  | Normalise a single address ahead of the match.                         |
| EP-05 Render Party Address   | Down-render for a legacy screening engine.                             |

Recommended _use cases_Three address-level checks, all At-Source.

verified\_userVerify a payee address inside a CoP check

Validate

Data At-Source

Run structural address validation as part of a Confirmation of Payee response.

EP-03 Check Party Address Single

edit\_documentValidate an address on a form, in real time

Validate

Data At-Source

Check one address structurally as it is typed, sub-100ms, before the match.

EP-03 Check Party Address Single

categoryClassify and normalise a payee address

Classify to Correct

Data At-Source

Detect format and normalise a single address ahead of a name or account match.

EP-06 / EP-01 Classify and Process Party Address Single

**Watch out for —** you never own a `pain` or `pacs` message — this is Data-scope only. The check is **fail-open**: if ARS is unavailable, your existing name / account verdict returns exactly as today. The verdict rides inside your current response shape, so there's no integration change on your customer's side.

Where next

[Compliance](https://dev.ionova.ai/solutions/compliance)[Core concepts](https://dev.ionova.ai/concepts)[API reference](https://dev.ionova.ai/apis)