Documents (KYC) Intro

Intro to KYC documents and sub-documents

Base Documents

The Base Document is basic user information, such as: name, DOB, address, email, and phone.

Base Document Object

Body Params

name:
required
string

Name of the document owner

alias:
string

Alias of the document owner (this can be the name or in case of businesses it can be the DBA entry)

email:
required
string

Email associated with the document

phone_number:
required
string

Phone number associated with the document

ip:
required
string

IP of where the document is being submitted from

entity_type:
required
string

Entity type of the document owner, this can be gender in case of an individual or DBA in case of a business. See here

entity_scope:
required
string

Industry in which the document owner operates. In case of an individual it can be their field of profession, in case of a corp this can be their line of business. See here

day:
required
integer

In case of a person this is day of birth. In case of business entity, this is day of organization

month:
required
integer

In case of a person this is month of birth. In case of business entity, this is month of organization

year:
required
integer

In case of a person this is year of birth (must be over 18). In case of business entity, this is year of organization

address_street:
required
string

Address associated with the document owner, this can be home address of a person or business address of a corp. Please include apartment suite or unit numbers.

address_city:
required
string

Address associated with the document owner, this can be home address of a person or business address of a corp.

address_subdivision:
required
string

Address associated with the document owner, this can be home address of a person or business address of a corp. This value needs to be in ISO Alpha-2.

address_postal_code:
required
string

Address associated with the document owner, this can be home address of a person or business address of a corp.

address_country_code:
required
string

Address associated with the document owner, this can be home address of a person or business address of a corp. This value needs to be in ISO Alpha-2.

virtual_docs:
array of objects

See Sub-Document Object here

physical_docs:
array of objects

See Sub-Document Object here

social_docs:
array of objects

See Sub-Document Object here

Base Document 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.
  • We recommend using Google to auto-populate the correct address to reduce address verification issues, as we check for mailable addresses.

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 Specification 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 worst permission scope ends up being the permission associated with the user account (This ensures that the Specification Sheet KYC program is never invalidated, thus keeping you compliant).

Following are the 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 Specification 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 Specification 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

NOT_KNOWN

Do not wish to specify (acceptable in cases of individuals only)

CORP

Corporation

Estate

Estate

IRA

Individual Retirement Account

LLC

Limited Liability Company

PARTNERSHIP

Any type of partnership

SOLE-PROPRIETORSHIP

Sole Proprietorship

TRUST

Trust

Sub-Documents

Sub-Documents are supporting documents. They are classified as Physical, Virtual or Social documents.

Body Params

document_type:
required
string

Type of document (physical, virtual, social)

document_value:
required
string

Value of the document (in case of physical documents, submit the padded base64 value of the file you wish to upload)

Sub-Document Statuses

Along with the user permissions, you can also view the status of a user's sub-documents.
Same document status conversations are followed for all three sub document types (Physical, Social), & Virtual.

Following are different subdocument statues and what they mean:

Status
Comment

SUBMITTED

Document was submitted but not validated. Resubmission is not needed.

SUBMITTED|REVIEWING

Document was uploaded and is being reviewed. Documents are reviewed asynchronously and may take a minute.

SUBMITTED|MFA_PENDING

Document uploaded, waiting for the user to verify the MFA code. Only applicable for EMAIL_2FA and PHONE_NUMBER 2FA.

SUBMITTED|VALID

Document submitted was reviewed and validated

SUBMITTED|INVALID

Document was submitted and determined to be invalid (resubmission dependent upon platform Spec. Sheet and KYC)

SUBMITTED|INVALID|BLACKLIST

Document was submitted, determined to be invalid and has been blacklisted due to fraudulent activity.

Physical Documents

These are images of physical documents uploaded to Synapse for verification (ex: Driver’s License, Proof of Address, Proof of Income, etc.). Physical docs must be converted to base64. Following is the complete list of physical documents that we are capable of verifying:

document_type
Allowed File Types
Comments

GOVT_ID

.png / .jpg / .jpeg

Front of user's government-issued photo ID (Driver's License, State ID, or Passport)

GOVT_ID_BACK

.png / .jpg / .jpeg

Back of user's government-issued photo ID (Driver's License, State ID, or Passport)

GOVT_ID_INT

.png / .jpg / .jpeg

User's government-issued photo ID (Driver's License, State ID, or Passport) that is not in English

GOVT_ID_INT_BACK

.png / .jpg / .jpeg

Back of user's government-issued photo ID (Driver's License, State ID, or Passport) that is not in English

VIDEO_AUTHORIZATION

.mov / .mp4 / .webm

5 second authorization video of the user. Read more here

SELFIE

.png / .jpg / .jpeg

Picture of user's face. We are deprecating SELFIE for VIDEO_AUTHORIZATION

PROOF_OF_ADDRESS

.png / .jpg / .jpeg / .pdf

User's proof of address (i.e. utility bill)

PROOF_OF_INCOME

.png / .jpg / .jpeg / .pdf

User's proof of income (i.e. pay stub)

PROOF_OF_ACCOUNT

.png / .jpg / .jpeg / .pdf

User's proof of account ownership (i.e. bank statement)

AUTHORIZATION

.png / .jpg / .jpeg

ACH authorization signed by the user

BG_CHECK

.png / .jpg / .jpeg /.pdf

Background check of the user

SSN_CARD

.png / .jpg / .jpeg / .pdf

SSN card of the user

EIN_DOC

.png / .jpg / .jpeg / .pdf

Form 147C issued to the business

W9_DOC

.png / .jpg / .jpeg / .pdf

W-9 with EIN number

W2_DOC

.png / .jpg / .jpeg / .pdf

W-2 document

W8_DOC

.png / .jpg / .jpeg / .pdf

W-8 document

VOIDED_CHECK

.png / .jpg / .jpeg

Voided check of the Individual/business

AOI

.png / .jpg / .jpeg / .pdf

Articles of Incorporation

BYLAWS_DOC

.png / .jpg / .jpeg / .pdf

Bylaw document

LOE

.png / .jpg / .jpeg / .pdf

Letter of engagement

CIP_DOC

.png / .jpg / .jpeg / .pdf

CIP & business description document

SUBSCRIPTION_AGREEMENT

.png / .jpg / .jpeg / .pdf

Subscription agreement

PROMISSORY_NOTE

.png / .jpg / .jpeg / .pdf

Promissory note

LEGAL_AGREEMENT

.png / .jpg / .jpeg / .pdf

Any other legal agreement

REG_GG

.png / .jpg / .jpeg / .pdf

Reg GG form

DBA_DOC

.png / .jpg / .jpeg / .pdf

DBA or Fictitious Name Documentation

DEPOSIT_AGREEMENT

.png / .jpg / .jpeg / .pdf

Deposit agreement

OTHER

.png / .jpg / .jpeg / .pdf

If you don't need us to validate a physical document but still want to submit for the record, you can use OTHER as the type as well

Physical Document Format:

The base64 you send via this API call should be padded. See example below:

"data:text/csv;base64,<actual_file_data>

Testing Physical Document in Sandbox

To be able to generate a sample base64, you can go to Base64 Image. They make it easy to generate a padded base64 for any image. You can then use that base64 to test with our APIs.

document_value
Result

data:image/invalid;base64,SUQs==

Validation fails (i.e. identity related information is a complete fail)

Any Other

Validation is successful

Photo ID Requirements

Users do not need to mail in their government ID. They will upload a photo of their ID.
Following is a list of suggestions to improve accuracy for Photo ID uploads:

  • Steady image
  • ID occupies most of image
  • ID and text are aligned properly
  • Plain background
  • Four visible edges of the ID
  • Min resolution ~1200 pixels, minor axis
  • Good natural lighting (average pixel intensity ~150)
  • No flash
  • Name, address & DOB matches those supplied to us in base doc
  • Should be in full color (no black and white images accepted)
  • We recommend maximum file size of 2 MB (most high-quality JPG are around 1 MB)
    *Make sure to check your Spec Sheet to confirm if users need an American government-issued ID or if they can use an international government-issued ID

Following is an example of a high-quality Photo ID submission:

Video Auth Requirements

Following is a list of suggestions to improve accuracy for Video auth uploads:

  • Camera is positioned straight, in front of face, and not too far away
  • User is looking directly into camera while speaking
  • User is taking a steady video recording
  • No other people are present in video recording
  • Good natural lighting (average pixel intensity ~150)
  • Should be in full color (no black and white videos accepted)
  • We recommend a It maximum file size of 10 MB (most high quality JPG are around 5 MB)

Following is an example of a high-quality Video Auth submission:

Social Documents

Social documents are verified through tokens or validation pins (i.e. Facebook, LinkedIn, etc).
Following is the complete list of social documents that we are capable of verifying:

document_type
Comments

ADDRESS

User's address

DATE

User's birthdate

EMAIL_2FA

Using two-factor authentication to verify email

FACEBOOK

Facebook user access token. Please include email, user_friends, user_photos, and user_posts permissions for your user's Facebook token

LINKEDIN

OTHER

If you don't need us to validate the social document but still want to submit for the record, you can use OTHER as the type as well

PHONE_NUMBER_2FA

Using two-factor authentication to verify phone number

TWITTER

Twitter URL of the user's profile

Address Validation

We validate addresses to ensure an address is mailable. We encourage you to use a tool like Google to autocomplete addresses. This reduces the risk of submitting improperly formatted addresses.

Social Document Sandbox Test Values
Following are test values for Social Document verification in sandbox:

Document Type
document_value
Result

ADDRESS

Validation Fails (i.e. supplied address is invalid / unable to verify address(

ADDRESS

Any other address

Validation succeeds

EMAIL (supplied via base doc)

Validation Fails (i.e. identity related information is a complete fail)

EMAIL_2FA and PHONE_NUMBER_2FA

123456

Validation Succeeds during SUBMITTED|MFA_PENDING

FACEBOOK

Validation Fails (i.e. identity related information is a complete fail)

IP (supplied via base doc)

255.255.255.0

Validation Fails (i.e. identity related information is a complete fail)

LINKEDIN

Validation Fails (i.e. identity related information is a complete fail)

PHONE_NUMBER (supplied via base doc)

541-754-3010

Validation Fails (i.e. identity related information is a complete fail)

TWITTER

Validation Fails (i.e. identity related information is a complete fail)

`EMAIL_2FA` and `PHONE_NUMBER_2FA`

Two-factor authentication will not be sent in sandbox.

Virtual Documents

These documents are uploaded in meta data form (i.e. SSN, TIN, etc.). Following is the complete list of virtual documents that we are capable of verifying:

document_type
Comments

SSN

SSN number of the user

PASSPORT

Passport number of the user

DRIVERS_LICENSE

Driver's License number of the user

PERSONAL_IDENTIFICATION

Personal identification number of the user

TIN

TIN/EIN number of the business

DUNS

DUNS number of the business

OTHER

If you don't need us to validate the virtual document but still want to submit it for the record, you can use OTHER as the type as well

Virtual Document Sandbox Test Values
Following are test values for Virtual Document verification in sandbox. The last 4 digits of your virtual document must be one of the following values (ex: SSN = 777772222).

Real Identities

Note that you cannot verify real identities and document information in sandbox.

document_value
Result

1111 or any other value

Validation fails (i.e. identity related information is a complete fail)

2222

Validation succeeds