Onboard businesses

Open a crypto account for a business end client. If they’re new to your platform, onboard them first, then open their account. If they already have a customerId, skip straight to opening the account.

How it works

Check whether the client is new

Look up whether this business already has a customerId with Anchorage Digital. Existing clients can open additional accounts without repeating onboarding.

Onboard the client (new clients only)

Submit the business’s KYB information and documentation, and collect their agreement to your terms and conditions. Anchorage Digital performs due diligence and returns a customerId.

Open the account

Create an account (subaccount) for the client, specifying the account type and linking it to their customerId — either the one just created, or an existing one.

Confirm approval

Check the account’s status, or subscribe to the subaccount.opened webhook, to know when it’s active.

You don’t need to wait for a new client’s onboarding to be fully approved before opening their account — you can submit the account application right after receiving their customerId. Client onboarding and account opening are approved together.

This flow supports opening a business taxable account (e.g., LLC, C Corp, Trust, etc.) for business end clients. Before onboarding your first client, decide how you’ll deliver terms and conditions and whether you’re using a KYC reliance model — see Terms and conditions.

Integration steps

If this client already has a customerId, skip ahead to Step 6: Create the account.

Step 1: Onboard the client

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

Sandbox: applications must use mock data and reviews are expedited. Production: actual client information is required and a more thorough review process applies — no mock data is permitted in production.

General entries:

Tag	Description	Required	Type	Value restrictions
legalEntityName	legal entity name	Yes	String
hasDbaName	does the organization have a registered DBA name?	Yes	Boolean	`true` or `false`
dbaNames	DBA name	Yes, if `hasDbaName` is `true`	String
businessRegistrationNumber	business registration number	Yes (this or `taxId` required)	String
taxId	EIN	Yes (this or `businessRegistrationNumber` required)	Number	9-digit number
proofOfAddressContext	explanation when `hasProofOfAddress` is `false`	No	String
legalStructure	legal structure of the business	No	Enum	`C_CORP`; `LLC`; `LLP`; `LP`; `S_CORP`; `SOLE_PROP`; `TRUST`; `NON_PROFIT`; `OTHER`
legalStructureOther	legal structure when `legalStructure` is `OTHER`	No	String
physicalCountry	country	Yes	String	ISO 3166-1 alpha-2 country code
physicalStreetAddress	street address	Yes	String
physicalCity	city name	Yes	String
physicalStateUS	US state	Yes, for US country	String	2-character USPS state code
physicalStateOther	non-US state or province	Yes, for non-US countries	String
physicalPostalCode	zip code or postal code	Yes	String
hasProofOfAddress	can you provide a proof of address?	Yes	Boolean	`true` or `false`
hasProofOfAddressContext	additional context if unable to provide proof of address	No	String

Additional entries for IRS reporting requirements (US and non-US entities):

Tag	Description	Required	Type	Value restrictions
US entity
taxClassificationUs	tax classification (entity type)	Yes if `taxId` is provided	Enum	See tax classification values below
taxExemptionPayeeCode	exempt payee code	No	Enum	`TAX_EXEMPT_PAYEE_CODE_1` through `TAX_EXEMPT_PAYEE_CODE_13`. Values
fatcaExemptionReportingCode	exemption from FATCA reporting code	No	Enum	See FATCA values below
certifiedW9	customer has signed W-9 certification	Yes if `taxId` is provided	Boolean	`true` or `false`
Non-US entity
taxClassificationNonUs	tax classification (entity type)	Yes if `businessRegistrationNumber` is provided	Enum	See tax classification values below
disregardedEntityName	disregarded entity name	Yes if `taxClassificationNonUs` is `DISREGARDED_ENTITY`	String
fatcaEntityType	FATCA entity type	Yes if `taxClassificationNonUs` is `DISREGARDED_ENTITY`	Enum	See FATCA values below
fatcaStatusFfi	FATCA status	Yes if `fatcaEntityType` is `FFI`	Enum	See FATCA values below
fatcaStatusNffe	FATCA status	Yes if `fatcaEntityType` is `NFFE`	Enum	See FATCA values below
fatcaStatusExemptBO	FATCA status	Yes if `fatcaEntityType` is `EXEMPTBO`	Enum	See FATCA values below
giin	GIIN	Yes if `fatcaStatusFfi` is `REPORTING_MODEL_1`, `REPORTING_MODEL_2`, or `REGISTERED_DEEMED_COMPLIANT_OTHER_THAN_MODEL_1`	String	See GIIN composition
beneficialOwnersRequired	any individuals directly or indirectly owning ≥25% of the entity?	Yes if `fatcaStatusNffe` is `PASSIVE`	Boolean
beneficiaryFirstName	beneficiary’s legal first name	Yes if `beneficialOwnersRequired` is `true`	String
beneficiaryLastName	beneficiary’s legal last name	Yes if `beneficialOwnersRequired` is `true`	String
beneficiaryTaxId	beneficiary’s US taxpayer ID number	Yes if `beneficialOwnersRequired` is `true`	String	9-digit number
beneficiaryAllocation	beneficiary’s percentage of ownership	Yes if `beneficialOwnersRequired` is `true`	String	1–100, no percentage sign or spaces (e.g., `35`)
beneficiaryCountry	beneficiary’s residential country	Yes if `beneficialOwnersRequired` is `true`	String	ISO 3166-1 alpha-2 country code
beneficiaryStreetAddress	beneficiary’s residential street address	Yes if `beneficialOwnersRequired` is `true`	String
beneficiaryCity	beneficiary’s residential city	Yes if `beneficialOwnersRequired` is `true`	String
beneficiaryStateUS	beneficiary’s residential state	Yes, for US country	String	2-character USPS state code
beneficiaryStateOther	beneficiary’s residential state/province	Yes, for non-US countries	String
beneficiaryPostalCode	beneficiary’s zip code or postal code	Yes if `beneficialOwnersRequired` is `true`	String
certifiedW8	customer has signed W-8 certification	Yes if `businessRegistrationNumber` is provided	Boolean	`true` or `false`

Tax classification and FATCA values

taxClassificationUs values

Code	Label
`C_CORP`	C Corporation
`LLC_C_CORP`	LLC - C Corporation
`LLC_PARTNERSHIP`	LLC - Partnership
`LLC_S_CORP`	LLC - S Corporation
`PARTNERSHIP`	Partnership
`S_CORP`	S Corporation
`TRUST_ESTATE`	Trust/Estate
`OTHER`	Other

taxClassificationNonUs values

Code	Label
`CENTRAL_BANK`	Central bank of issue
`COMPLEX_TRUST`	Complex trust
`CORP`	Corporation
`DISREGARDED_ENTITY`	Disregarded entity
`ESTATE`	Estate
`FOREIGN_GOVERNMENT_CONTROLLED_ENTITY`	Foreign government – controlled entity
`FOREIGN_GOVERNMENT_INTEGRAL_PART`	Foreign government – integral part
`GRANTOR_TRUST`	Grantor trust
`INTERNATIONAL_ORGANIZATION`	International organization
`PARTNERSHIP`	Partnership
`PRIVATE_FOUNDATION`	Private foundation
`SIMPLE_TRUST`	Simple trust
`TAX_EXEMPT_ORGANIZATION`	Tax-exempt organization

fatcaExemptionReportingCode values

Code	Description
`FATCA_EXEMPT_REPORTING_CODE_A`	An organization exempt from tax under section 501(a) or any individual retirement plan as defined in section 701(a)(37)
`FATCA_EXEMPT_REPORTING_CODE_B`	The United States or any of its agencies or instrumentalities
`FATCA_EXEMPT_REPORTING_CODE_C`	A state, the District of Columbia, a U.S. commonwealth or territory, or any of their political subdivisions or instrumentalities
`FATCA_EXEMPT_REPORTING_CODE_D`	A corporation the stock of which is regularly traded on one or more established securities markets, as described in Regulations section 1.1472-1(c)(1)(i)
`FATCA_EXEMPT_REPORTING_CODE_E`	A corporation that is a member of the same expanded affiliated group as a corporation described in Regulations section 1.1472-1(c)(1)(i)
`FATCA_EXEMPT_REPORTING_CODE_F`	A dealer in securities, commodities, or derivative financial instruments (including notional principal contracts, futures, forwards, and options) that is registered as such under the laws of the United States or any state
`FATCA_EXEMPT_REPORTING_CODE_G`	A real estate investment trust
`FATCA_EXEMPT_REPORTING_CODE_H`	A regulated investment company as defined in section 851 or an entity registered at all times during the tax year under the Investment Company Act of 1940
`FATCA_EXEMPT_REPORTING_CODE_I`	A common trust fund as defined in section 584(a)
`FATCA_EXEMPT_REPORTING_CODE_J`	A bank as defined in section 581
`FATCA_EXEMPT_REPORTING_CODE_K`	A broker
`FATCA_EXEMPT_REPORTING_CODE_L`	A trust exempt from tax under section 664 or described in section 4947(a)(1)
`FATCA_EXEMPT_REPORTING_CODE_M`	A tax-exempt trust under a section 403(b) plan or section 457(g) plan

fatcaEntityType values

Code	Label	Description
`EXEMPTBO`	Exempt beneficial owners	Entities generally exempt from FATCA, including foreign governments, central banks, and certain retirement funds or international organizations
`FFI`	Foreign Financial Institutions (FFIs)	Non-US entities that hold financial accounts or act as financial intermediaries, such as banks, investment funds, or custodians
`NFFE`	Non-Financial Foreign Entities (NFFEs)	Non-US entities that are not financial institutions, typically operating businesses engaged in trade, manufacturing, or services
`OTHER`	Other statuses	Accounts not considered financial accounts for FATCA purposes, which do not fall into the FFI, NFFE, or exempt categories

fatcaStatusFfi values

Code	Label
`CERTIFIED_DEEMED_COMPLIANT_INVESTMENT_ADVISERS_MANAGERS`	Certified deemed-compliant investment advisers/managers
`CERTIFIED_DEEMED_COMPLIANT_LIMITED_LIFE_DEBT_INVESTMENT_ENTITY`	Certified deemed-compliant limited-life debt investment entity
`CERTIFIED_DEEMED_COMPLIANT_LOCAL_BANK`	Certified deemed-compliant local bank
`CERTIFIED_DEEMED_COMPLIANT_LOW_VALUE_ACCOUNTS`	Certified deemed-compliant low-value accounts
`CERTIFIED_DEEMED_COMPLIANT_SPONSORED_CLOSELY_HELD_INVESTMENT_VEHICLE`	Certified deemed-compliant sponsored, closely held investment vehicle
`EXCEPTED_INTER_AFFILIATE`	Excepted inter-affiliate
`NONPARTICIPATING`	Nonparticipating
`NONREPORTING_IGA`	Nonreporting IGA
`OWNER_DOCUMENTED`	Owner-documented
`PARTICIPATING`	Participating
`REGISTERED_DEEMED_COMPLIANT_OTHER_THAN_MODEL_1`	Registered deemed-compliant (other than model 1)
`REPORTING_MODEL_1`	Reporting model 1
`REPORTING_MODEL_2`	Reporting model 2
`RESTRICTED_DISTRIBUTOR`	Restricted distributor
`SPONSORED_WITHOUT_GIIN`	Sponsored (without GIIN)
`TERRITORY_FINANCIAL_INSTITUTION`	Territory financial institution

fatcaStatusNffe values

Code	Label
`501C_ORGANIZATION`	501(c) organization
`ACTIVE`	Active
`DIRECT_REPORTING`	Direct reporting
`EXCEPTED_NONFINANCIAL_ENTITY_IN_LIQUIDATION_OR_BANKRUPTCY`	Excepted nonfinancial entity in liquidation or bankruptcy
`EXCEPTED_NONFINANCIAL_GROUP_ENTITY`	Excepted nonfinancial group entity
`EXCEPTED_NONFINANCIAL_STARTUP_COMPANY`	Excepted nonfinancial start-up company
`EXCEPTED_TERRITORY`	Excepted territory
`NONPROFIT_ORGANIZATION`	Nonprofit organization
`PASSIVE`	Passive
`PUBLICLY_TRADED_OR_AFFILIATE_OF_A_PUBLICLY_TRADED_CORPORATION`	Publicly traded or affiliate of a publicly traded corporation
`SPONSORED_DIRECT_REPORTING`	Sponsored direct reporting

fatcaStatusExemptBO values

Code	Label
`ENTITY_WHOLLY_OWNED_BY_EXEMPT_BENEFICIAL_OWNERS`	Entity wholly owned by exempt beneficial owners
`EXEMPT_RETIREMENT_PLAN`	Exempt retirement plan
`FOREIGN_GOVERNMENT_US_POSSESSION_CENTRAL_BANK_OF_ISSUE`	Foreign government / US possession / central bank of issue
`INTERNATIONAL_ORGANIZATION`	International organization

A unique customerId is returned, which is used in all future calls to identify this end client.

{
  "applicationType": "RIA_PC_INSTITUTION",
  "entries": [
    { "key": "legalEntityName", "value": "Encom LLC" },
    { "key": "hasDbaName", "value": true },
    { "key": "dbaNames", "value": "Encom Video Games" },
    { "key": "taxId", "value": "123456789" },
    { "key": "physicalCountry", "value": "US" },
    { "key": "physicalStreetAddress", "value": "123 Lightcycle Way" },
    { "key": "physicalCity", "value": "San Francisco" },
    { "key": "physicalStateUS", "value": "CA" },
    { "key": "physicalPostalCode", "value": "94104" },
    { "key": "hasProofOfAddress", "value": true },
    { "key": "taxClassificationUs", "value": "C_CORP" },
    { "key": "taxExemptionPayeeCode", "value": "TAX_EXEMPT_PAYEE_CODE_5" },
    { "key": "fatcaExemptionReportingCode", "value": "FATCA_EXEMPT_REPORTING_CODE_D" },
    { "key": "certifiedW9", "value": true }
  ]
}

{
  "applicationType": "RIA_PC_INSTITUTION",
  "entries": [
    { "key": "legalEntityName", "value": "Encom LLC" },
    { "key": "hasDbaName", "value": true },
    { "key": "dbaNames", "value": "Encom Video Games" },
    { "key": "businessRegistrationNumber", "value": "123456789" },
    { "key": "physicalCountry", "value": "GB" },
    { "key": "physicalStreetAddress", "value": "123 Lightcycle Way" },
    { "key": "physicalCity", "value": "London" },
    { "key": "physicalStateOther", "value": "London" },
    { "key": "physicalPostalCode", "value": "94104" },
    { "key": "hasProofOfAddress", "value": true },
    { "key": "taxClassificationNonUs", "value": "CORP" },
    { "key": "fatcaEntityType", "value": "NFFE" },
    { "key": "fatcaStatusNffe", "value": "PASSIVE" },
    { "key": "beneficialOwnersRequired", "value": true },
    {
      "key": "beneficiaryGroup",
      "value": [
        {
          "beneficiaryFirstName": "John",
          "beneficiaryLastName": "Smith",
          "beneficiaryTaxId": "123456789",
          "beneficiaryAllocation": "60",
          "beneficiaryCountry": "GB",
          "beneficiaryStreetAddress": "10 Downing Street",
          "beneficiaryCity": "London",
          "beneficiaryStateOther": "England",
          "beneficiaryPostalCode": "SW1A 1AA"
        },
        {
          "beneficiaryFirstName": "Jane",
          "beneficiaryLastName": "Doe",
          "beneficiaryTaxId": "987654321",
          "beneficiaryAllocation": "40",
          "beneficiaryCountry": "GB",
          "beneficiaryStreetAddress": "221B Baker Street",
          "beneficiaryCity": "London",
          "beneficiaryStateOther": "England",
          "beneficiaryPostalCode": "NW1 6XE"
        }
      ]
    },
    { "key": "certifiedW8", "value": true }
  ]
}

{
  "data": {
    "customerId": "d6f81b1563687f326ac9e3d4a00f9a0949e4ca81158cc47674846d27094b2503",
    "status": "IN_PROGRESS"
  }
}

Step 2: Upload required documents

POST /v2/onboarding/customers/{{customerId}}/document

Tag	Description	Required	Type	Value restrictions
constitutionDocument	constitutional document	Yes	Upload	GIF, JPEG, PNG, or PDF — max 25 MB
proofOfAddress	proof of address	Yes, if `hasProofOfAddress` is `true`	Upload	GIF, JPEG, PNG, or PDF — max 25 MB

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.

{
  "documentType": "constitutionDocument"
}

{
  "data": {
    "url": "https://storage.googleapis.com/anchorage/pii/v1/{{customerId}}/CONSTITUTION_DOCUMENT/{{documentId}}?X-Goog-Algorithm=GOOG4-RSA-SHA256&X-Goog-Expires=899&X-Goog-Signature={{signature}}"
  }
}

Upload the image to the returned URL:

curl -X PUT -H 'Content-Type: application/octet-stream' --data-binary @image.png {{step4url.response.body.data.url}}

Step 3: Check onboarding status

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

Response

{
  "data": {
    "customerId": "26c014539bd34e8e441e34381d9d5dad9434bb3645dbbf27d8267304e7ad0584",
    "entries": [
      { "key": "legalEntityName", "value": "ACME Corp - 2025-04-11T11:08:11.771Z" },
      { "key": "dbaNames", "value": "Encom Video Games" },
      { "key": "taxId", "value": "123456789" },
      { "key": "hasProofOfAddress", "value": "Yes" },
      { "key": "physicalCity", "value": "San Francisco" },
      { "key": "physicalCountry", "value": "United States" },
      { "key": "physicalStateUS", "value": "California" },
      { "key": "physicalStreetAddress", "value": "123 Lightcycle Way" },
      { "key": "physicalPostalCode", "value": "94104" },
      { "key": "hasDbaName", "value": "Yes" }
    ],
    "errors": [
      { "key": "constitutionDocument", "status": "MISSING", "value": "expected 1 answer for non-void triggered question, instead got 0" },
      { "key": "proofOfAddress", "status": "MISSING", "value": "expected 1 answer for non-void triggered question, instead got 0" }
    ],
    "status": "IN_PROGRESS"
  }
}

Step 4: Submit the client application

POST /v2/onboarding/customers/{{customerId}}/submit Once submitted, you can move on to opening the account — you don’t need to wait for approval first (see the note above).

Step 5: Check client 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 completes, register for webhooks — see Configure webhooks.

Step 6: Create the account

POST /v2/onboarding/subaccounts Supported business account type:

Account type	Subtype	End client(s)
`INSTITUTIONAL_TAXABLE`	—	1

Expected program signers:

Account type	Expected program signers
`INSTITUTIONAL_TAXABLE`	Initial set of named program signers

Key fields:

Field	Description	Required	Type	Restrictions
`legalEntityName`	Legal entity name	Yes	String
`accountType`	Account type	Yes	Enum	`INSTITUTIONAL_TAXABLE`
`programSignerGroup`	List of program signers	Yes	Array
`programSignerGroup/programSignerFirstName`	First name	Yes	String
`programSignerGroup/programSignerLastName`	Last name	Yes	String
`programSignerGroup/programSignerEmail`	Email	Yes	String	Valid email
`documentPreferenceAddressDefaultEmail`	Statement delivery email(s)	Yes	String	Comma-separated valid emails
`termsAgreementID`	Terms agreement ID	If T&Cs enabled	String	ID from `/v2/onboarding/agreements/terms` — see Terms and conditions
`beneficiaryGroup`	Beneficiaries	No	Array
`beneficiaryGroup/beneficiaryType`	Type	Yes	Enum	`SPOUSE`, `FAMILY_OR_FRIEND`, `CHARITY`, `TRUST`, `ESTATE`
`beneficiaryGroup/beneficiaryName`	Name	Yes	String
`beneficiaryGroup/beneficiaryAllocation`	Allocation %	Yes, must sum to 100	Number	1–100
`contingencyBeneficiaryGroup`	Contingency beneficiaries	No	Array	Same structure as `beneficiaryGroup`
`fees`	Fee configuration	No	Array	See fee types
`isSegregated`	Wallet structure (omnibus or segregated wallets)	No, defaults to `false` (omnibus wallets)	Boolean	Org must opt into feature
`programCustomers`	Linked end clients	Yes	Array
`programCustomers/programCustomerId`	End client ID	Yes	String	The `customerId` from Step 1 — or an existing client’s `customerId` if you skipped onboarding
`programCustomers/programCustomerRole`	Role	Yes	Enum	`PRIMARY` or `SECONDARY`
`submit`	Submit immediately	No, defaults to `false`	Boolean

Each account requires a signer who can represent the client. The initial set of named program signers acts on the business’s behalf.

Example request

{
  "name": "{{name}}",
  "externalId": "{{externalId}}",
  "submit": true,
  "entries": [
    { "key": "legalEntityName", "value": "SubAccount INSTITUTIONAL_TAXABLE" },
    { "key": "accountType", "value": "INSTITUTIONAL_TAXABLE" },
    { "key": "isSegregated", "value": true },
    { "key": "documentPreferenceAddressDefaultEmail", "value": "kevin.flynn_4@test.com" },
    { "key": "programSignerGroup", "value": [
        { "programSignerFirstName": "Kevin", "programSignerLastName": "Flynn_5", "programSignerEmail": "kevin.flynn_5@test.com" },
        { "programSignerFirstName": "Kevin", "programSignerLastName": "Flynn_6", "programSignerEmail": "kevin.flynn_6@test.com" }
      ]
    },
    { "key": "programCustomers", "value": [
        { "programCustomerId": "{{customerId1}}", "programCustomerRole": "PRIMARY" }
      ]
    },
    { "key": "fees", "value": [
        { "feeType": "ADVISORY", "feeRate": "0.1" },
        { "feeType": "MANAGEMENT", "feeRate": "0.25", "feeIsBillable": true }
      ]
    }
  ]
}

A unique subaccountId is returned for all future references to this account. Add termsAgreementId to a program signer’s entry only if terms and conditions delivery requires their explicit agreement.

Step 7: List account applications

GET /v2/onboarding/subaccounts Returns all account onboarding applications associated with this API key. Supports afterId and limit for cursor pagination.

Step 8: Check account status

GET /v2/onboarding/subaccounts/{subaccountId} Errors and missing documents are listed in the errors array of the response.

Step 9: Update the account application (if errors are present)

PUT /v2/onboarding/subaccounts/{subaccountId} Uses the same entries array shape as Step 6. Only include the entries you want to change — omitted fields keep their existing value.

Example request

{
  "entries": [
    { "key": "documentPreferenceAddressDefaultEmail", "value": "kevin.flynn_4-updated@test.com" }
  ]
}

Any change to a client’s data, or a request to terminate their account, is authenticated by Anchorage Digital Bank with the end client via DocuSign before processing.

Step 10: Submit the account application (if `submit: false`)

POST /v2/onboarding/subaccounts/{subaccountId}/submit

Step 11: Check account approval status

GET /v2/subaccounts/customers/accounts?subaccountIds={subaccountId} Status values: PENDING (received, awaiting approval) → OPEN (approved and active). Alternatively, subscribe to the subaccount.opened webhook event for asynchronous notification.

Reliance only: edit client 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.

Tag	Description	Required	Can edit	Type	Value restrictions
legalEntityName	legal entity name	Yes	No	String
hasDbaName	does the organization have a registered DBA name?	Yes	Yes	Boolean	`true` or `false`
dbaNames	DBA name	Yes, if `hasDbaName` is `true`	Yes	String
taxId	EIN	Yes (this or `businessRegistrationNumber` required)	No	Number	9-digit number
businessRegistrationNumber	business registration number	Yes (this or `taxId` required)	No	String
proofOfAddressContext	explanation when `hasProofOfAddress` is `false`	No	Yes	String
legalStructure	legal structure of the business	No	No	Enum	`C_CORP`; `LLC`; `LLP`; `LP`; `S_CORP`; `SOLE_PROP`; `TRUST`; `NON_PROFIT`; `OTHER`
legalStructureOther	legal structure when `legalStructure` is `OTHER`	No	Yes	String
physicalCountry	country	Yes	Yes	String	ISO 3166-1 alpha-2 country code
physicalStreetAddress	street address	Yes	Yes	String
physicalCity	city name	Yes	Yes	String
physicalStateUS	US state	Yes, for US country	Yes	String	2-character USPS state code
physicalStateOther	non-US state or province	Yes, for non-US countries	Yes	String
physicalPostalCode	zip code or postal code	Yes	Yes	String
hasProofOfAddress	can you provide a proof of address?	Yes	Yes	Boolean	`true` or `false`
hasProofOfAddressContext	additional context if unable to provide proof of address	No	Yes	String

Platform

Solutions

How it works

Integration steps

Step 1: Onboard the client

Tax classification and FATCA values

Step 2: Upload required documents

Step 3: Check onboarding status

Step 4: Submit the client application

Step 5: Check client approval status

Step 6: Create the account

Step 7: List account applications

Step 8: Check account status

Step 9: Update the account application (if errors are present)

Step 10: Submit the account application (if `submit: false`)

Step 11: Check account approval status

Reliance only: edit client information

​How it works

​Integration steps

​Step 1: Onboard the client

​Tax classification and FATCA values

​Step 2: Upload required documents

​Step 3: Check onboarding status

​Step 4: Submit the client application

​Step 5: Check client approval status

​Step 6: Create the account

​Step 7: List account applications

​Step 8: Check account status

​Step 9: Update the account application (if errors are present)

​Step 10: Submit the account application (if submit: false)

​Step 11: Check account approval status

​Reliance only: edit client information

How it works

Integration steps

Step 1: Onboard the client

Tax classification and FATCA values

Step 2: Upload required documents

Step 3: Check onboarding status

Step 4: Submit the client application

Step 5: Check client approval status

Step 6: Create the account

Step 7: List account applications

Step 8: Check account status

Step 9: Update the account application (if errors are present)

Step 10: Submit the account application (if `submit: false`)

Step 11: Check account approval status

Reliance only: edit client information