Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.

Skip to main content

27 June 2024

ยท One min read

Newโ€‹

๐Ÿค๐Ÿพ Visit the new Swan Trust Center to learn how Swan keeps you, your users, and Swan secure. Understand security measures in depth, review policies, and find answers to frequent security questions.

Improvementsโ€‹

๐Ÿ”Ž Search account holders by account holder ID on your Dashboard > Data > Account holders. You will need to enter the full account holder ID.

๐Ÿ”€ To ensure the best identification experience for your users, set the identificationLevel to Auto when constructing your authorization URL. This lets Swan choose the best flow for your user's situation. Using Auto is ideal if you include the onboardingId in the authorization URL, or if you're trying to reengage your user to complete identification.

Breaking changesโ€‹

โš ๏ธ As announced on May 24th, the notStarted identification status was removed. Instead, use Started to streamline identification flows and reduce confusion.
Nothing changed for account holder verification statuses.