Rezva

Complaints

Approved businesses can report impersonation, unauthorized identifiers, payment-destination abuse, or trademark disputes.

API request

POST /v1/complaints
Authorization: Bearer <approved-provider-key>
Content-Type: application/json

{
  "target_type": "phone",
  "target_value": "+15551234567",
  "reason": "impersonation",
  "description": "This identifier is being used to impersonate our business.",
  "evidence": ["https://example.com/evidence"]
}

The API returns 201 with a complaint record. A complaint must identify an existing mapping and the description must contain enough detail for review.

Dashboard workflow

  1. Open Business → Complaints after business approval.
  2. Enter a target as type:value.
  3. Provide a concise reason, description, and relevant evidence.
  4. Track SUBMITTED, UNDER_REVIEW, RESOLVED, or REJECTED.

Complaints are stored durably in the registry and routed to the operator review queue. Reporter history is scoped to the authenticated dashboard user.

Open complaints