Personal User Intent Field Requirements by KYC Type
Last updated: September 25, 2026
Overview
Onboarding a personal user to Astra's Platform begins with UserIntent creation, which submits their information for a high-resolution identity assessment.
Not every program submits the same fields. The ssn and date_of_birth as well as phone, address1, address2, and ip_address requirements depend on a combination of the following factors: the kyc_type assigned to your Users, whether your program has been approved for KYC delegation, and the payment flows your program is utilizing.
Standard Fields
For programs leveraging Astra's KYC services, the following fields are required on every POST /v1/user_intent request:
email · phone · first_name · last_name · address1 · city · state · postal_code · ip_address
Requirements for submitting phone, address1, and ip_address can vary for receive-only programs. If you would like to not submit these fields, please contact your Astra representative.
These fields are optional for all programs:
address2 · preferred_first_name · preferred_last_name · preferred_pronouns · kyc_type · metadata
kyc_type will default to verified if not specified.
ssn and date_of_birth requirements vary by configuration. See the section below.
SSN and Date of Birth Requirements
Find the row that matches your program's configuration on the table below. KYC delegation is approved by Astra's Compliance Team on a per-program basis. If you are unsure whether your program is approved, contact your Astra representative.
Your program |
|
|
|---|---|---|
| Required (last four digits) | Required |
| Optional | Optional |
| Optional | Required |
| Required | Optional |
| Optional | Optional |
If your program is KYC Delegated and is using AFTs via Astra Card-to-Card, or Card-to-Account solution, DOB is required as part of Astra's process for disputing Chargebacks on your program's behalf.