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

# KYB workflow

> Follow the current business onboarding sequence alongside KYB review, EDD, timing, and rejection policy.

## KYB workflow

The KYB workflow combines current customer, related-party, capability, task, submission, and document resources with a policy review of the business and its ownership.

<Warning>
  KYB outcomes and timelines are policy estimates. They do not guarantee API
  transitions, approval, or availability.
</Warning>

## Current workflow sequence

### 1. Create the business customer

Create the business customer with [`POST /v3/customers`](/api-reference/customers/post-v3-customers). Read the current customer with [`GET /v3/customers/{customerId}`](/api-reference/customers/get-v3-customers-by-customer-id).

### 2. Maintain related parties

Use [`GET /v3/customers/{customerId}/related-parties`](/api-reference/customers/get-v3-customers-by-customer-id-related-parties) to review current parties, [`POST /v3/customers/{customerId}/related-parties`](/api-reference/customers/post-v3-customers-by-customer-id-related-parties) to create one, and [`PATCH /v3/customers/{customerId}/related-parties/{relatedPartyId}`](/api-reference/customers/patch-v3-customers-by-customer-id-related-parties-by-related-party-id) to update supplied facts.

Maintain the direct owners, parent entities, UBOs, control persons, directors, officers, and signers requested by current tasks. Their roles are distinct.

### 3. Discover and request an eligible capability

Read [`GET /v3/customers/{customerId}/capabilities/supported`](/api-reference/capabilities/get-v3-customers-by-customer-id-capabilities-supported). Request an available or beta capability only when the customer is eligible, using [`POST /v3/customers/{customerId}/capabilities/{capabilityId}`](/api-reference/capabilities/post-v3-customers-by-customer-id-capabilities-by-capability-id).

### 4. Read current tasks

List current work with [`GET /v3/customers/{customerId}/tasks`](/api-reference/tasks/list-customer-tasks). Fetch each actionable task through [`GET /v3/customers/{customerId}/tasks/{taskId}`](/api-reference/tasks/get-customer-task), then derive the next action from its current revision, requirements, and sessions.

### 5. Upload documents requested by the current task

Upload a requested file with [`POST /v3/customers/{customerId}/documents`](/api-reference/documents/post-v3-customers-by-customer-id-documents). The current task determines whether a document is required and can narrow its accepted type, count, or format.

### 6. Submit complete task answers

Submit one complete answer set for the current task revision with [`POST /v3/customers/{customerId}/tasks/{taskId}/submissions`](/api-reference/task-submissions/create-customer-task-submission). Use current requirement ids and reference uploaded document ids only where the task asks for them.

### 7. Monitor current resources

After every action or event, refetch the customer with [`GET /v3/customers/{customerId}`](/api-reference/customers/get-v3-customers-by-customer-id), the capability with [`GET /v3/customers/{customerId}/capabilities/{capabilityId}`](/api-reference/capabilities/get-v3-customers-by-customer-id-capabilities-by-capability-id), its applications with [`GET /v3/customers/{customerId}/capabilities/{capabilityId}/applications`](/api-reference/capabilities/get-v3-customers-by-customer-id-capabilities-by-capability-id-applications), and any current tasks.

For the complete mechanics, see [business onboarding](/integration/onboarding/customers#business-customers), [Capabilities and tasks](/integration/onboarding/capabilities-and-requirements#complete-current-tasks), and the [Integration Documents guide](/integration/onboarding/capabilities-and-requirements#upload-documents).

## Enhanced due diligence (EDD) triggers

EDD may be required for:

* High-risk jurisdictions
* High-risk verticals, including gaming, trading, and crypto exchanges
* Complex ownership structures
* Expected monthly volume exceeding applicable thresholds
* Operations involving sanctioned countries

## Policy review outcomes

**Outcome:** KYB approval, conditional approval with caps, or rejection.

These are policy review outcomes, not current API status values. A conditional policy decision can be reflected through current resources without creating a status named "conditional approval."

## Verification timeline

| Stage             | Typical duration   |
| ----------------- | ------------------ |
| Document upload   | Immediate          |
| Initial review    | 1-2 business days  |
| Standard KYB      | 2-5 business days  |
| EDD, if triggered | 5-10 business days |

These durations are typical policy estimates, not guaranteed API behavior.

## Common rejection reasons

| Reason                         | Resolution                                                  |
| ------------------------------ | ----------------------------------------------------------- |
| Missing documents              | Provide every document type requested by the current task   |
| Unclear or blurry documents    | Provide higher-quality scans or images                      |
| Mismatched information         | Make sure the entity name matches across submitted evidence |
| Incomplete ownership structure | Provide evidence that accounts for 100% of ownership        |
| Expired documents              | Provide current, valid documents                            |

## Policy terms and API states

Keep policy decisions separate from current resource vocabularies:

* **Capability status:** `pending`, `ready`, `restricted`, `rejected`, `canceled`
* **Application status:** `requested`, `in_review`, `action_required`, `ready`, `rejected`, `disabled`, `canceled`
* **Task status:** `action_required`, `in_review`, `satisfied`, `rejected`, `canceled`
* **Submission outcome:** `in_review`, `accepted`, `changes_requested`, `rejected`

Read the latest resource rather than translating a policy outcome into an API value.


## Related topics

- [Overview](/knowledge-base/compliance/overview.md)
- [Governance and Roles](/knowledge-base/compliance/governance-retention-and-privacy.md)
- [KYC status and workflow](/knowledge-base/individual-onboarding/status-and-workflow.md)
- [Individual onboarding API workflow](/knowledge-base/individual-onboarding/api-workflow.md)
- [Business onboarding overview](/knowledge-base/business-onboarding/overview.md)