The Base Document contains basic user information (e.g. name, date-of-birth, address, email, and phone number). See Base Documents for more information.

Considerations

Users should submit their full legal name. Initials of names or non-legal names will result in failures.
Users below 18 years of age will be auto-rejected unless sharing a joint account with a parent or legal guardian
As we check for mailable addresses, we encourage you to use Google Maps or the USPS ZIP Code Lookup Tool or similar tools to autocomplete addresses to avoid typos and other address verification issues. Please confirm that provided address is valid via our Verify Address API call before adding or updating.

Permission Scope

Permission scope helps determine if the user is allowed to send funds, receive funds and up to what amount (i.e. daily, weekly or monthly).

Each base document object is given a permission_scope based on the KYC program set on the platform’s Spec Sheet. This helps decide the overall user permission associated with the account.

Additionally, if multiple base document objects are submitted for one user, the document with the lowest permission scope ends up being the permission associated with the user account (This ensures that the Spec Sheet KYC program is never invalidated, thus keeping you compliant).

Below are examples of different kinds of permission scopes:

Permission Scope	Comment
SEND\|RECEIVE	The user can send and receive funds
SEND\|RECEIVE\|TIER\|1	The user can send and receive funds up to the limits governed by the tier on the Spec Sheet
RECEIVE	The user can only receive funds
RECEIVE\|TIER\|1	The user can receive funds up to the limits governed by the tier on the Spec Sheet

Entity Scopes


- Not Known - Aerospace/Defense - Airport - Arts & Entertainment - Automobiles and Parts - Automotive - Bank & Financial Services - Bank/Financial Institution - Bar - Biotechnology - Book Store - Business Services - Cause - Chemicals - Club - Community Organization - Community/Government - Company - Computers/Technology - Concert Venue - Consulting/Business Services - Doctor - Education - Elementary School - Energy/Utility - Engineering/Construction - Event Planning/Event Services - Farming/Agriculture	- Food/Beverages - Food/Grocery - Government Organization - Health/Beauty - Health/Medical/Pharmaceuticals - Health/Medical/Pharmacy - Home Improvement - Hospital/Clinic - Hotel - Industrials - Insurance Company - Internet/Software - Landmark - Lawyer - Legal/Law - Library - Licensed Financial Representative - Local Business - Media/News/Publishing - Middle School - Mining/Materials - Movie Theater - Museum/Art Gallery - Non-Governmental Organization (NGO) - Non-Profit Organization	- Organization - Outdoor Gear/Sporting Goods - Pet Services - Political Organization - Political Party - Preschool - Professional Services - Public Places - Real Estate - Religious Organization - Restaurant/Cafe - Retail and Consumer Merchandise - School - Shopping/Retail - Small Business - Spas/Beauty/Personal Care - Sports Venue - Sports/Recreation/Activities - Telecommunication - Tours/Sightseeing - Train Station - Transport/Freight - Transportation - Travel/Leisure - University

Entity Types

Entity Types	Comment
M	Male
F	Female
O	Other
MINOR	Individual under 18 years of age (minors may only open an account that is co-owned by their parent/legal guardian. This must be part of your software agreement)
NOT_KNOWN	Do not wish to specify (acceptable in cases of individuals only)
ASSOCIATION	Association
CORP	Corporation
ESTATE	Estate
IRA	Individual Retirement Account
LLC	Limited Liability Company
PARTNERSHIP	Any type of partnership
SOLE-PROPRIETORSHIP	Sole Proprietorship
TRUST	Trust
VENDOR	Vendor Business entity type for cases where a common vendor relationship may be used in different contexts by multiple different business users on the same Platform. When creating a document owner with this entity type, please keep in mind that `is_business` needs to be set to `false`. This solution was provided in part to avoid vendor users associated with multiple business docs triggering duplicate user checks (i.e. duplicate user checks will be skipped for any document owners assigned this entity type).