Signing up

Users sign up for Swan the first time they go through an authentication link. This typically occurs when they're invited to become an account member or during the account onboarding process.

Sign-up steps

Core steps

Your user:

1. Opens their sign-up link.
2. Enters their phone number.
   • If you include their number when creating their sign-up link, they won't need to enter it again.
3. Confirms their phone number. Swan sends your user a text message with a verification code. The user enters this code on the device they used to open the sign-up link, whether that's a computer or a mobile device.
4. Enters their personal information: first name, last name, and birthdate. This information must match the information that appears on their identity document.
   • The user skips this step if you included this information when creating their sign-up link.
5. Sets a 6-digit passcode. Users must remember their passcode. Swan can request it anytime the user needs to consent to a sensitive operation.
6. Completes email verification if included in the OAuth URL.
   • This step only appears if email verification was configured in the sign-up link.

Identification steps

If a user isn't required to complete identification, they can access Swan after setting their passcode. If a user is required to complete identification, they continue with the following steps.

1. Enters their birth information: birth city, postal code, country, and nationality.
   • If you include this information when creating their sign-up link, they won't need to enter it again.
2. Enters their residency information. Swan only requests the information required for the relevant identification process (to be completed in step 4).
   • QES process: residency address, city, country, and postal code.
   • PVID or Expert process: residency country only.
   • If you include this information when creating their sign-up link, they won't need to enter it again.
3. Reviews and confirms all provided information: personal, birth, and residency. Users can modify their information before confirming.
4. Completes identification, where Swan verifies their identity. This step can be performed later, though it's recommended to complete it as soon as possible. When using the API, you must trigger this step.
5. (Optional) Sets up biometrics, if desired and available on their mobile device. Biometrics typically include face or fingerprint authentication.
6. Gets redirected to your redirect URL.

Identification rejection

If a user's identification fails, they receive a text message after completing sign-up with the reason for the failure. They must follow the link provided to retry.

Share the support article on Identification rejection reasons and solutions to help your users troubleshoot the identification process.

Sign-up diagram

The following diagram illustrates the steps to sign up for Swan.

End-user perspective of signing up

Accessing accounts

After signing up, your user can start using Swan. How they get to their account depends on your integration:

Integration	Access
No-code Web Banking	Swan redirects your user to the interface automatically.
Full API or Customized open source frontend	Your user is redirected to the redirectUrl you supplied when creating their sign-up link. Make sure to declare your redirectUrl on your Dashboard > Developers > Redirect URIs. Otherwise, the redirection fails.