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

# Onboard end clients

> Steps to onboard end clients to your Anchorage Digital account via API.

Once your organization sandbox is set up, you can begin onboarding end clients.

## Onboarding steps

<Steps>
  <Step title="Collect end client KYC information and documentation" />

  <Step title="Sign terms and conditions">
    The end client signs the Anchorage Digital terms and conditions (see integration paths below — this step may be optional depending on your setup).
  </Step>

  <Step title="Submit the application">
    Once application data and documentation are ready, submit via API.
  </Step>

  <Step title="Anchorage Digital review">
    Anchorage Digital performs KYC due diligence. If documents are missing or questions arise, additional materials will be collected via secure file sharing.
  </Step>

  <Step title="Application approval">
    Once approved, application status becomes `COMPLETE`. Use webhooks to get notified when approval is complete.
  </Step>
</Steps>

Subaccount onboarding and creation can be requested while end clients are pending Anchorage Digital approval — both are approved together.

Any change in data or account termination requests is authenticated by Anchorage Digital Bank with end clients via DocuSign before processing.

<Note>
  **Sandbox:** Applications must use mock/dummy data and reviews are expedited. In production, actual client information is required and a more thorough review process applies. No dummy data is permitted in production.
</Note>

***

## Terms and conditions integration paths

### Option 1: With Anchorage Digital terms and conditions

Include Anchorage Digital T\&Cs for end clients to sign. These are hosted via DocuSign and can be embedded in your existing onboarding workflow.

<Note>
  Anchorage Digital supports DocuSign's Embedded Signing integration, which allows immediate signing within an app or website. Signed URLs are valid for **5 minutes** (a DocuSign limit that cannot be changed) and should be generated immediately before use. If a URL expires, request a new one with a subsequent GET call to the agreement endpoint. See [DocuSign embedded signing documentation](https://developers.docusign.com/docs/esign-rest-api/esign101/concepts/embedding/embedded-signing/) for details.
</Note>

### Option 2: Without Anchorage Digital terms and conditions

You are responsible for presenting the Anchorage Digital T\&Cs to end clients, collecting their acceptance, and maintaining proof of acceptance. Anchorage Digital's DocuSign process is not used in this path.

***

## Changelog

| Date          | Change                                            |
| :------------ | :------------------------------------------------ |
| June 10, 2025 | Updates for new onboarding API payloads and flows |
| May 1, 2025   | Initial version                                   |