Skip to main content

Account holders

Individual (natural person) or legal entity (legal person) who owns and is responsible for the funds in a Swan account. Account holders must be located in a country where Swan offers accounts, as listed on the country coverage page.

Account holders can be individuals or companies (considered legal entities), and account holders can have as many Swan accounts as they need. In order for funds to be stored in a Swan account, they must be associated with an account holder.

As a result of the onboarding process, users become account holders.

Overview

As a Partner and project owner, you choose who can have Swan accounts within your project. However, regulations require Swan to verify all of your account holders, and to keep track of them for the lifetime of the account.

Therefore, Swan verifies each user before the account holder and account objects are created in your Swan project. This verification, often referred to as Know Your Customer (KYC) or Know Your Business (KYB), is mandatory.

Verification responsibility

One benefit of working with Swan is that Swan is responsible for this process. However, if it is vital that you perform KYC and KYB processes yourself, please send Swan a detailed explanation.

One account holder, multiple accounts

For individual accounts, you can open multiple accounts for the same account holder. They'll complete a shorter onboarding process for each new account because they don't need to complete account holder verification again. Follow the guide to add additional individual accounts for an existing account holder.

Companies can open multiple accounts linked to a single account holder and registration number. No new verification is needed when creating additional accounts. A new onboarding is required if you want to open an account with:

  • An IBAN from a different country.
  • A different company's registration number.
  • A different establishment (a branch of the same company at a new address).

Follow the guide to add additional company accounts for an existing account holder.

Account holder verification process

The verification process for a new account holder is thorough, and Swan provides a streamlined process through which each account holder proves they're who they claim to be.

Account holders can access their account immediately after creation. However, while account holder verification is in progress, there are limitations on the account. IBANs might be issued before limitations are removed from the account.

The account holder verification process can include the following elements:

  1. Onboarding: Process is finalized for either an individual or a company, which creates a user, an account holder, an account, and an account membership linking the user to the account.
  2. Identification: User that opened the individual or company account completes identification with an ID document and a picture or video.
  3. First transfer: Users may need to send a first transfer to their new Swan account.
  4. Document collection: Swan collects required documents.
  5. Clarification: Swan might contact the user to clarify details from onboarding, identification, or document collection.
  6. Review: Swan reviews all provided elements.

After Swan validates the review, the account holder is verified and their account receives its primary IBAN.

Statuses

Final status
Verified
Refused
Verification
requested
NotStarted
Pending
WaitingForInformation
Account holder verification statusExplanation
NotStartedVerification process hasn't started yet. The account holder's legal representative needs to complete identification before starting account holder verification.
PendingSwan is reviewing the account holder's information before activating or refusing the account.
WaitingForInformationSwan is waiting for information from the account holder, such as a first transfer, supporting documents, or something else.
VerifiedSwan verified the account holder and the process is complete
RefusedSwan won't onboard this account holder

Waiting for information status

If the account holder verification status is WaitingForInformation, the account holder must meet one or more of the following requirements. Call the API to learn which requirement they're missing.

RequirementExplanation
FirstTransfer
Required
Account holder needs to send a first transfer to their Swan account.
LegalRepresentative
DetailsRequired
More information is required about the account's legal representative, or about the account member acting as the legal representative with Power of Attorney.
Organization
DetailsRequired
More information is required about the organization.
SupportingDocuments
Required
Provide the requested supporting documents.
TaxId
Required
Provide the Tax ID for both the account holder and the organization.
UboDetails
Required
More information is required about the organization's ultimate beneficial owner or owners (UBO).
OtherSwan contacts your account holder directly about additional requirements.

First transfer

Prerequisites

Before a user can make their first transfer, the following conditions must be met:

  • Onboarding status: Finalized
    The user's onboarding is complete, and all required supporting documents have been uploaded.

  • Identification status: Valid
    The user's identification was successfully completed.

Sending a first transfer to a user's Swan account can be requested after the user completes identification but before the account holder verification status changes to Verified.

Not all users are required to send a first transfer to be Verified. Swan asks some users to send a first transfer as an additional verification measure. Additionally, if your users complete certain identification processes in certain countries, a first transfer might be required by law. Review the guide to request a first transfer for communication options.

🇩🇪 Germany

A first transfer is always required for self-employed and individual accounts for which the account country is Germany, regardless of registration or residency.

Users must send first transfers from an account in their name. Not all third-party payment platforms or online banks are accepted for first transfers. Share this Support Center article with your users. It explains why a first transfer may be requested, and the possible outcomes.

Users can send any amount in the first transfer. While there is technically no deadline for sending the transfer, the user's account is Limited until the transfer is validated.

First transfer and account holder verification status

A first transfer request is made when the account holder verification status is Pending. After Swan makes the request, the account holder verification status changes to WaitingForInformation.

After the user sends their transfer, the account holder verification status changes to Pending while Swan checks the transfer source. Note that if the account used to send the first transfer is located outside of the European Economic Area (EEA), it may be subject to additional review.

First transfer outcomes

OutcomeDescriptionAccount holder verification status update
Account holder is verifiedThe first transfer source was accepted, and we approved the account holder.Verified
Account holder is refusedThe first transfer source wasn't accepted, and we didn't approve the account holder.Refused
Additional transfer requestedThe first transfer came from an unaccepted source. We asked the user to send another transfer from a different account in their name.WaitingForInformation
Additional documents requestedWe received the first transfer and asked the user for supporting documents.WaitingForInformation
Additional transfer or documents

After the additional transfer or documents are received, the account holder verification status changes from WaitingForInformation to Pending while Swan reviews them. Depending on the outcome, the status changes to either Verified or Refused.

Sequence diagram

This diagram details a common flow of how Swan, the account holder, and you interact during verification. Note that the flow includes alternate scenarios (A or B) where the path is determined by your integration choices. Your final integration might flow differently.

SwanUserPartnerSwanUserPartnerIf a first transfer is required, the process splits into one of two scenarios:alt[SCENARIO A: Partner notifies user about first transfer][SCENARIO B: Swan requests first transfer from user]If supporting documents are required, the process splits into one of two scenarios:alt[SCENARIO A: Partner provides documents][SCENARIO B: Account holder provides documents]Creates onboarding link1Returns onboarding object2Sends onboarding link3Completes onboarding4Sends text message inviting the accountholder to complete identification5Provides identification providerwith required elements6Verifies identification7Sends email notifying about required first transfer8Requests first transfer9Sends first transfer10Sends email requesting first transfer11Sends first transfer12Swan reviews first transfer13Sends webhook about missing supporting documents14Requests documents15Provides documents16Uploads documents with the API17Sends email requesting supporting documents18Uploads documents to banking interface19Swan reviews identityverification and documents20

Guides