Individuals
Onboarding Requirements
Stables requires the following information for standard individual onboarding:
- First and last name
- Date of birth (YYYY-MM-DD)
- Nationality (country code)
- Street address
- City
- Postal code
- Province / State
- Country
- At least one ID document (e.g. passport) for identity verification
- Selfie photo
- Account purpose (
account_purpose), with a description (account_purpose_other) when the purpose isOTHER. See References for the values - Expected monthly volume (
expected_monthly_volume). See References for the values - Occupation (
occupation), as a standardised occupation code. See Occupation Codes for the codes - Annual income (
annual_income). See References for the values
Older customers
For older individual customers, Stables may ask for two extra items before individual_base verification can complete:
| Requirement | What the customer provides | How to submit |
|---|---|---|
proof_of_address | A recent proof of residential address | Through the verification flow |
age_risk_acknowledgement | Confirmation that they understand the age-related risks of transacting in crypto, plus their intended use of the service | PATCH /api/v1/customer/{customerId} |
The Stables compliance team can also request these as an RFI. Each appears as a kyc_capability requirement and clears once the customer holds that capability.
Submitting the age-risk acknowledgement
The acknowledgement is a declaration, not a document. Send both fields in one request:
PATCH /api/v1/customer/{customerId}{
"age_risk_acknowledged": true,
"reason_for_use": "Sending money to family overseas"
}reason_for_use is free text in the customer's own words. Stables compliance reviews both answers, and the customer gains the age_risk_acknowledgement and reason_for_use capabilities once they are approved.
Only set age_risk_acknowledged to true after the customer has seen and accepted the acknowledgement in your product. Do not set it on their behalf.
The hosted age_risk verification action still works but is deprecated. Use the PATCH above for new integrations. See Update Customer.