Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.clear-box.io/llms.txt

Use this file to discover all available pages before exploring further.

KYB (Know Your Business) is the merchant-side counterpart to KYC. Before a merchant can accept settled transactions, ClearCheck verifies the legal entity, its beneficial owners, and screens against sanctions and adverse-media lists. KYB runs on Persona, the same identity infrastructure that powers consumer KYC.

​
What ClearCheck KYB covers

  • Entity verification — confirming the business exists and the submitted legal name and registration number match government records.
  • Beneficial-owner verification — running KYC on individuals with 25%+ ownership and on key controllers.
  • Sanctions and PEP screening — checking the entity and its owners against sanctions, PEP, and adverse-media lists.
  • Document review — articles of incorporation, EIN/Tax ID, proof of address.

​
Flow at a glance

1

Merchant created

The merchant exists in ClearBox with kyb_status: "pending_kyb" (see Onboarding overview).
2

Create a KYB inquiry

ClearBox creates a Persona business inquiry from your KYB template, tagged with the merchant_id as the reference ID.
3

Operator completes the flow

A representative of the merchant uploads documents and adds beneficial owners. Each owner completes individual KYC.
4

Receive the result

Persona transitions the inquiry to a terminal status and fires a webhook.
5

Activate the merchant

On approval, ClearBox flips kyb_status to active and the merchant can transact.

​
1. Create the KYB inquiry

POST https://api.withpersona.com/api/v1/inquiries
Authorization: Bearer <PERSONA_API_KEY>
Content-Type: application/json

{
  "data": {
    "attributes": {
      "inquiry-template-id": "itmpl_ClearCheckKYB",
      "reference-id": "mer_7d3a"
    }
  }
}
Persona returns the inquiry. Surface it to the merchant operator through your chosen integration (hosted, embedded, or mobile SDK). See Verify identity (ClearCheck) for the integration patterns — they’re identical to the consumer KYC flow, just configured for a business template.

​
2. Read the result

Subscribe to the inquiry.approved and inquiry.declined webhooks. When the KYB inquiry is approved, update the merchant. 
PATCH /v1/merchants/mer_7d3a

{
  "kyb_status": "active",
  "kyb_inquiry_id": "inq_kyb_4f2c"
}

​
Handling needs_review and declines

needs_review returns the inquiry to your compliance team for manual review. Hold the merchant in pending_kyb until your team resolves it. For declines, follow your program’s decline-handling process; the merchant cannot be activated.

​
Ongoing monitoring

ClearCheck re-screens active merchants on a configurable cadence and on any material change (new beneficial owner, address change). If a re-screen produces an adverse signal, ClearBox flips the merchant to suspended and pauses settlements until review.

Next: Locations & terminals

Once active, add the venues and the terminals at them.

​
Reference

itmpl_ClearCheckKYB is a placeholder business-template ID. Replace it with your program’s actual Persona KYB inquiry template ID.