Statuses

Collections and documents have unique statuses.

Collection statuses

This lifecycle is described for onboarding-related collections; collections requested for transactions or verification renewal move through the same statuses.

Collection status	Explanation
WaitingForDocument	Onboarding is created and ready for documents, or documents were submitted but Swan is requesting additional documents. Next steps: Moves to PendingReview after onboarding is finalized.
PendingReview	Onboarding is finalized and a document review is needed. Next steps: Can move to Approved, Rejected, or Canceled depending on partner actions and Swan decisions (or, if documents are insufficient, back to WaitingForDocument).
Approved	Swan approved the supporting document collection.
Rejected	Swan rejected the supporting document collection.
Canceled	Swan canceled the supporting document collection (this could also be at the partner's request).

Document statuses

Document status	Explanation
WaitingForUpload	URL to upload the document has been generated. Next steps: If the document is uploaded → Uploaded If the collection switches to a final status before the document is uploaded → NotUploaded
Uploaded	Document is uploaded; if a review is completed on the uploaded document, the status moves to Validated or Refused depending on Partner actions and Swan decisions.
Validated	Swan approved the document.
Refused	Swan refused the document (refer to Refused document reason codes).
NotUploaded	URL was generated but collection was closed before a document was uploaded.

Deleting a document

An Uploaded document can be deleted by you or by Swan (for example, if the wrong file was shared). Deletion removes the document rather than assigning it a status. See Delete a document.

Refused document reason codes

When any type of supporting document is Refused, the reason is displayed on your Dashboard. Navigate to the supporting document area for the relevant onboarding, transaction, or account holder verification. You can also query the API.

Reason code	Explanation
CompanyNameMismatch	The company name in the document submitted doesn't match Swan's records.
ExpiredDocument	Documents must have been issued within the last three months.
InvalidAddress	The address in the document submitted doesn't match Swan's records.
InvalidDocument	The document submitted isn't valid or in an accepted format.
InvalidOrMissingData	The name in the document submitted is invalid, missing, or not clearly visible.
UnacceptableDocument	The document submitted doesn't match the requested document type.
ProviderColorIdDocumentRequired	The document must be submitted in color.
MissingSignature	The document submitted must be signed or dated.
BadDocumentQuality	The quality of the document submitted is too low. All document content must be clear and legible.
FullDocumentRequired	The entire document must be submitted, not just a portion of the document.
MissingDescription	More information is needed to understand the nature of this transaction.
InvalidTransaction	The information in the document submitted doesn't match this specific transaction.
TransactionNameMismatch	The issuer or beneficiary name in the document submitted doesn't match the transaction details.
TransactionDateMismatch	The date in the document submitted doesn't match the transaction details.
TransactionAmountMismatch	The transaction amount in the document submitted doesn't match the transaction details.
IbanMismatch	The beneficiary IBAN in the document submitted doesn't match the transaction details.
Other	Reason not covered by the other reason codes.

These reason codes come from the SupportingDocumentReasonCode enum. Capital deposit documents have their own set of refusal reason codes; refer to the capital deposit reference.