# CMP-056 — An ISV registering for a customer must supply the customer's details

> Where an ISV or platform registers on behalf of a customer, the campaign must carry the customer's website and brand information, not the platform's.

- **Rule ID:** CMP-056
- **Layer:** Campaign (`CAMPAIGN`)
- **Checks:** `campaign fields + brand.website`
- **Severity:** BLOCKING — Breaking this rule gets the submission rejected outright.
- **When it bites:** Gates approval — get this wrong and registration is refused
- **How it is detected:** AI judgement over the submitted form
- **Fix type:** Fix the field — a better value in the form clears it
- **Required by:** AWS
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/campaign/cmp-056/

## Why this rule exists

This is the campaign-side twin of registering the wrong brand. The platform's own site is real and substantial, which makes it a tempting field value — and it means the entity being vetted is not the business whose messages will be sent, so the vetting proves nothing about the sender.

## How to fix it

Populate every campaign field from the end customer: their website, their brand name, their opt-in surface. Your platform belongs on the CSP record only. Done when nothing in the campaign identifies the platform.

## Example of a compliant value

```text
Website: acmecoffee.com (the customer) — not northstarplatform.io (the ISV).
```

## Notes

Catalog CMP-056 is conditional on the registration being on behalf of a third party. We hold no "registered by an ISV" fact, so the condition lives in the judgement criteria instead of the applicability tag — the rule only fires a finding when the content itself shows a platform.