Skip to main content
This flow supports opening the following account types for institutional end clients:
  • INDIVIDUAL_TAXABLE
  • INSTITUTIONAL_TAXABLE
  • IRA — may contain an optional CONVERSION or ROLLOVER sub-type
  • ROTH — may contain an optional CONVERSION or ROLLOVER sub-type
  • JOINT
  • CUSTODIAL
Key differences from the existing institution onboarding flow:
  • physicalStateUS must be the 2-letter USPS state code when physicalCountry is US.
  • physicalStateOther must contain alphabetical characters when physicalCountry is not US.
  • New hasDbaName boolean field.
  • New dbaNames field — required when hasDbaName is true.
  • New upload field constitutionDocument — required.
  • New upload field proofOfAddress — required when hasProofOfAddress is true.
  • Removed fields: legalStructure, customerType, countryOfIncorporation, legalRegistAddrDifPrincPlace and all related legal address fields, initialFundingWalletGroup, sourceOfWealth.

Integration steps

1

Create an institution application

POST /v2/onboarding/customers
  • applicationType: RIA_PC_INSTITUTION
  • externalId: unique identifier used by the wealth platform to identify this end client
  • entries: see tables below
If the given externalId has already been tied to another end client, an external_id already in use error will be returned.
General entries:Additional entries for IRS reporting requirements (US and non-US entities):A unique customerId is returned, which will be used in all future calls to identify this end client at Anchorage Digital.Sample — US entity:
Sample — non-US entity:
Response:
2

Upload required document images

POST /v2/onboarding/customers/{{customerId}}/document
Upload a single image file (GIF, JPEG, PNG, or PDF). If a second file is uploaded, the latest replaces the first. Multi-file archives are rejected. A signed upload URL is returned and accepts the document via a PUT request. The URL is valid for 15 minutes — if it expires, request a new one by calling this endpoint again.
Sample request:
Sample response:
Upload the image:
3

Check the status of the application

GET /v2/onboarding/customers/{{customerId}}Any errors or missing documents are listed in the errors section of the response.Sample response:
4

Submit the application

POST /v2/onboarding/customers/{{customerId}}/submitOnce successfully submitted, you may submit another end client application or a linked subaccount application.
You do not need to wait for approval before submitting linked subaccount applications.
5

Check the approval status

GET /v2/onboarding/customers/{{customerId}}Upon successful submission, status changes from IN_PROGRESS to IN_REVIEW. Once fully approved, status changes to COMPLETE.To receive asynchronous notification when approval is complete, register for webhooks. See Configure webhooks.Sample response:

Reliance only: edit customer information

RIAs with full or partial KYC reliance have access to a flow in which program customers are auto-approved. For these RIAs, select fields remain editable even after application status is COMPLETE.

Changelog