This is the Digital Asset Accounts onboarding path, built on Circle’s shared
End User Onboarding API. Follow this quickstart for
the DAA flow; see the End User Onboarding docs for the full API reference and
advanced scenarios such as Requests for
Information and device-risk
signals.
Prerequisites
Before you begin, ensure that you’ve:- Requested and received Digital Asset Accounts sandbox access from your Circle representative. See Sandbox environment for details.
- Obtained an API key for Digital Asset Accounts from your Circle representative.
- (EEA end customers only) Confirmed with your Circle representative that your
agreement covers end customers in the European Economic Area (EEA), and that
EEA routing is enabled on your existing sandbox account. EEA end customers use
the same
api-sandbox.circle.comhost and API key. See End customers in the EEA. - (Recommended) Configured a webhook subscription for tracking asynchronous events.
Step 1: Create a business client
Create a new business client using the End User Onboarding API. Each client represents a business entity that goes through KYB verification.YOUR_API_KEY with your Bearer token. Use a unique clientName for
each new client, because the API rejects duplicate names.
Save the clientEntityId and applicationId from the response. You need both
values for the remaining steps.
Step 2: Complete business information
Fill out the required business information sections. Replace{applicationId}
with the value from step 1 in all of the following requests.
2.1. Basic business info
2.2. Business address
2.3. Business registration
The
businessName value must match the clientName you used in step 1.Step 3: Complete the remaining KYB sections
Six more sections need data before you can submit the application. The following calls use placeholder data that is valid for sandbox testing.3.1. Entity operations
3.2. Compliance details
3.3. Licensing
3.4. Beneficial owners
3.5. Intended use of account
3.6. Control person
Step 4: Upload documents
Upload six PDF documents required for KYB verification. For sandbox testing, create a minimal dummy PDF:documentId from each response because you need
them to link documents back to their sections.
4.1. Upload the control person’s government ID
The control person’s government ID requires arefId and documentType. First,
retrieve the refId:
refId value in data.data[0].refId, then upload the document:
4.2. Re-save sections with document references
After uploading, link the documents back to their sections by re-saving the section with thedocumentId values. For example, re-save
businessRegistrationDetails with the formation document:
documentId arrays:
physicalBusinessAddress: addphysicalAddressProofOfAddressintendedUseOfAccount: addbankBrokerageCryptoStatementandfinancialStatementsbeneficialOwnersDetails: addownershipChart
Step 5: Submit the application
Verify that all sections show acomplete status:
endUserAgreesToTermsOfService records that the end customer accepted the
application’s active certifications, which include Circle’s user agreement and
privacy policy. The submit request fails with a 400 error if it’s false or
missing. The certifications differ by region, so don’t hard-code the terms. To
show the end customer the exact text, list the application’s certifications and
display each one’s content before you record acceptance. See
Discover required certifications.
In sandbox, the application is auto-approved almost immediately. In production,
KYB verification takes time and may result in rejection.
Step 6: Retrieve your account
After the application is approved, retrieve the account using theclientEntityId from step 1:
accountId is now ready for deposits, withdrawals, and transfers. See
Wire deposits and withdrawals
to fund your account. To give the end customer more custodial accounts, see
Create a custodial account.
End customers in the EEA
End customers in the EEA follow the same steps, with the following differences. If your business isn’t in the flow of funds (Partner model), onboarding starts with a manual partner setup with Circle instead. Contact your Circle representative.- Booking: Circle books EEA end customers to Circle France SAS under its Markets in Crypto-Assets Regulation (MiCA) authorization. This happens automatically, whether you contract with Circle France SAS or Circle LLC. See Booking patterns.
- Terms: the application’s certifications include the Circle France SAS version of the user agreement. Show them and record the end customer’s acceptance before you submit the application in Step 5.
- Review in production: if your business is in the flow of funds (Wholesale model), Circle also runs a Compliance flow-of-funds review before it activates the account. Your Circle representative starts the review after you submit the application.
- Controls after activation: your platform authenticates with mTLS in addition to your API key, money movement and address book changes need Strong Customer Authentication (SCA) from the end customer (implement SCA), and each transfer destination must be registered in the platform address book with declared wallet ownership first. See EEA API behavior.