> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cadanapay.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Build multi-tenant integrations with Cadana's Platform API

The Platform API lets you manage multiple businesses from a single integration. You get one API token that can create businesses, onboard workers, run payroll, process payments, and [move funds between your own business accounts](/api-reference/workforce/platform/create-transfer) across all of them — each isolated by a unique tenant key.

This is purpose-built for HR platforms, payroll providers, talent marketplaces, staffing platforms, and international HR providers.

***

## Architecture

```mermaid theme={null}
flowchart TD
    APP["Your Platform"] -- "Platform Token + X-MultiTenantKey" --> CADANA

    subgraph CADANA["Cadana"]
        BIZ_A["Business A"]
        BIZ_B["Business B"]
        BIZ_C["Business C"]
    end
```

Each business has its own workforce, payroll, and payments — fully isolated by tenant key. Businesses can also manage multiple [legal entities](/workforce/entity-management) for global payroll operations across different jurisdictions.

Every API call that targets a specific business includes the `X-MultiTenantKey` header to identify which business you're operating on.

***

## Key Concepts

| Concept              | Description                                                                                                                     |
| :------------------- | :------------------------------------------------------------------------------------------------------------------------------ |
| **Platform Token**   | An API token with access across all businesses on your platform. Generated from the Dashboard after platform access is enabled. |
| **Tenant Key**       | A unique identifier for each business (e.g., `cad95193904`). Returned when you create a business.                               |
| **X-MultiTenantKey** | The HTTP header used to specify which business a request applies to. Required for all business-specific operations.             |

***

## Platform vs Org Tokens

| Aspect                | Org Token                   | Platform Token                       |
| :-------------------- | :-------------------------- | :----------------------------------- |
| **Scope**             | Single organization         | Multiple businesses                  |
| **Business creation** | Cannot create businesses    | Can create businesses via API        |
| **X-MultiTenantKey**  | Not required                | Required for business-specific calls |
| **Use case**          | Single-business integration | Multi-tenant platform                |

***

## Business Lifecycle

```mermaid theme={null}
flowchart LR
    A["Create Business"] --> B["Submit KYB"]
    B --> C["Review"]
    C -->|Approved| D["ACTIVE"]
    C -->|Needs info| E["Fix & Resubmit"]
    E --> C
```

| Status                 | Description                   | Can transact? |
| :--------------------- | :---------------------------- | :------------ |
| `pending_verification` | Created, KYB not yet approved | No            |
| `ACTIVE`               | Fully verified                | Yes           |
| `CLOSED`               | Business closed               | No            |

A business must complete [KYB verification](/platform/kyb-requirements) before it can process payments — the KYB submission itself moves through its own set of [statuses](/platform/kyb-requirements#kyb-statuses) while the business stays `pending_verification`.

***

## Getting Started

<CardGroup cols={2}>
  <Card title="Multi-Tenant Setup" icon="building" href="/platform/multi-tenant-setup">
    Step-by-step implementation guide
  </Card>

  <Card title="KYB Requirements" icon="shield-check" href="/platform/kyb-requirements">
    Business verification requirements
  </Card>

  <Card title="KYC Verification" icon="id-card" href="/platform/kyc-verification">
    User identity verification
  </Card>

  <Card title="Transaction Reconciliation" icon="file-invoice-dollar" href="/platform/transaction-reconciliation">
    Reconcile transactions across businesses
  </Card>
</CardGroup>