Step-up Requirements
Base verification (individual_base or business_base) covers most customers. Stables may ask some customers for more, based on their profile or activity. These extra items are step-up requirements.
A step-up requirement reaches you in one of two ways:
- During verification: the customer's base level stays pending until the requirement is met, and a
verificationRFI lists what is missing. - Later, as an RFI: Stables compliance or the risk engine asks for it on an existing customer or a held payment.
Either way, the requirement names a capability (required_capability) or a level (required_level). Once the customer holds the capability, the requirement is satisfied. You can check what a customer already holds with Get KYC Capabilities.
Stables compliance sets the rules that decide who is asked for what, and can change them. Build your integration around the requirements on the RFI, not around guesses about who will be asked.
Individuals
| Capability | What the customer provides | How to submit |
|---|---|---|
proof_of_address | A recent proof of residential address, such as a utility bill | proof_of_address_documents on Update Customer, or a verification link with verification_type: proof_of_address |
source_of_wealth | Documents showing how the customer built their overall wealth. See SOF & SOW | source_of_wealth_documents on Update Customer, or a verification link with verification_type: source_of_wealth |
liveness | A fresh liveness check, completed by the customer | A verification link with verification_type: liveness |
id_document:passport | A passport (or, where accepted, an Emirates ID) | A verification link with verification_type: passport |
edd_questionnaire | An enhanced due diligence questionnaire, completed by the customer | The verification link from the requirement's action |
age_risk_acknowledgement, reason_for_use | A declaration that the customer understands the risks of transacting in crypto, and their intended use of the service. Asked of some older customers | age_risk_acknowledged and reason_for_use on Update Customer. See Older customers |
Verification links are created with Create Verification Link and completed by the customer in a hosted flow. Documents sent through Update Customer are PDF, JPEG, PNG or HEIC, up to 5MB each, and are reviewed by Stables compliance before the capability is granted.
Businesses
Business enhanced due diligence (EDD) can be requested for a business customer that already has base verification. It covers:
| Capability | What the business provides |
|---|---|
business_edd_questionnaire | The due diligence questionnaire: what the business does, where its funds come from, expected volumes, and its compliance controls |
business_document:bank_statements | Recent company bank statements |
business_document:aml_bsa_policy | The company's written AML / BSA policy, when it conducts money services or has higher-risk activity |
all_ubos_have_identity | An identity document for every beneficial owner |
all_ubos_have_proof_of_address | Proof of residential address for every beneficial owner |
all_ubos_have_tax_id | A tax ID for every beneficial owner |
Submit it in one of two ways:
- Hosted: a verification link with
verification_type: business_edd, completed by the business. - API:
enhanced_due_diligence(answers and documents) andbeneficiaries(owner documents and tax IDs) on Update Customer. Answers are saved cumulatively, so you can send them in parts. Use a freshIdempotency-Keyfor each part.