> ## 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.

# Terms and conditions

> Configure terms and conditions delivery method and KYC reliance model for end client onboarding.

How you deliver terms and conditions, and whether your integration uses a KYC reliance model, are configured once during setup — before you onboard your first client.

## Terms configuration

Two methodologies are supported for providing terms and conditions to program customers.

**Docusign** — Share an Anchorage Digital branded Docusign link for the customer to review and sign. Agreements are attached to a subaccount onboarding application.

<Steps>
  <Step title="Create new terms and conditions for a signer">
    **`POST /v2/onboarding/agreements/{agreementType}`** with `agreementType` set to `terms`.

    | **Tag**              | **Description**                                            | **Required** | **Type** | **Value restrictions**                              |
    | :------------------- | :--------------------------------------------------------- | :----------- | :------- | :-------------------------------------------------- |
    | legalEntityName      | legal entity name                                          | Yes          | String   |                                                     |
    | signerFirstName      | signer's first name                                        | Yes          | String   |                                                     |
    | signerLastName       | signer's last name                                         | Yes          | String   |                                                     |
    | signerEmail          | signer's email address                                     | Yes          | String   | valid e-mail address                                |
    | termsAgreementFormat | agreement format                                           | Yes          | String   | `docusign` (`anchorage` format has been deprecated) |
    | returnUrl            | URL to redirect to once terms and conditions are accepted  | No           | String   |                                                     |
    | frameAncestor        | URL where the terms and conditions link should be embedded | No           | String   |                                                     |

    A unique `termsAgreementId` is returned, which will be used in an end client onboarding application. A Docusign signed and timed `url` is also returned. A new signed URL is returned on each GET call as long as the terms are still `IN_PROGRESS`.

    <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. All agreements must reflect a status of `COMPLETE` before submitting the full onboarding application. See [Docusign embedded signing documentation](https://developers.docusign.com/docs/esign-rest-api/esign101/concepts/embedding/embedded-signing/) for details.
    </Note>
  </Step>

  <Step title="Check the status or generate a new signed URL">
    **`GET /v2/onboarding/agreements/{agreementType}/{agreementId}`** with `agreementType` set to `terms` and `agreementId` set to the `termsAgreementId`.

    Returns details of the agreement, including `status`. If still `IN_PROGRESS`, a new Docusign signed URL is returned.
  </Step>
</Steps>

**Hosted terms** — The preferred approach for partners, though it requires legal sign-off. Customers agree implicitly through onboarding, without a Docusign signature: provide the version of terms presented to the customer and the date they implicitly agreed. Contact your Anchorage Digital account representative to discuss enabling this flow.

## Reliance model configuration

This configuration supports partnerships that use full or partial reliance models. No reliance is the assumed default. Setting up an RIA for a reliance model requires explicit legal sign-off.

| Model            | Behavior                                                                                                                                                          |
| :--------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Full reliance    | Document uploads are not required and KYC checks are skipped, moving directly to approval. Anchorage Digital relies on the partner to perform KYC.                |
| Partial reliance | Document uploads are not required at onboarding. KYB and individual profiles are submitted to Alloy; if Alloy returns approval, the application is auto-approved. |
| No reliance      | The standard KYC process applies.                                                                                                                                 |


## Related topics

- [Onboarding examples](/knowledge-base/platform/developers/wealth/wealth-management-onboarding-examples.md)
- [Onboard individuals](/knowledge-base/platform/developers/wealth/wealth-management-onboarding-individuals.md)
- [Onboard businesses](/knowledge-base/platform/developers/wealth/wealth-management-onboarding-institutions.md)
- [Configure sandbox](/knowledge-base/platform/developers/wealth/wealth-management-api-config.md)
- [Web3 access](/knowledge-base/platform/users/web3-access.md)