Supporting documents

Learn how Swan collects, reviews, and tracks the status of the supporting documents required to verify account holders and transactions.

Swan is sometimes required to collect documents to verify account holders and transaction details.

Each document is uploaded individually into a collection. After all required documents are uploaded, Swan reviews the collection.

Supporting document collections are empty when created. Swan can upload some documents, and you can add documents to these collections as requested. For each required document, you'll create a document within the collection.

Options for collecting documents

There are two primary options to collect required supporting documents:

Option	Explanation
Use the API (Recommended)	No emails are exchanged. You'll know every time a document is needed with webhook notifications. You communicate with your end users to gather the required documents. Choose the API or the Dashboard for most actions, including uploading documents.
Email communication	Swan communicates directly with you or your end users. You or your end user receives an email. When Swan emails your end users directly, you can be copied (CCd) on the email. Let a member of the Swan team know to save this preference.

Required documents

Documents might be required to support account holder verification, verification renewal (Re-KYC), or to prove the validity of a transaction. The documents required vary significantly depending on why Swan needs to collect the documents, where your users are located, whether they're onboarding as individuals or companies, and more.

Refer to the API Reference for the list of possible supporting document purposes.

Onboarding tip

For a better user experience, always include a list of required documents in your onboarding flows.

In this section

1

Statuses

Collection, document, and refused-reason statuses.

2

Purposes and types

Document purpose vs. type.