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

20 February 2023

· One min read

New features

✅ We added a new account activation tab to the Web Banking. This makes it easy for our no-code customers to finalize the account holder verification process. Just follow the steps.

✉️ Non-verified users can now use reset passcode by email.

💰 On March 1st 2023, we will start charging banking fees directly on your customers' Swan accounts. This is the first phase of our billing project. Ultimately, this will enable you to choose which fees you want to charge your customers through Swan, and lead to additional revenue.

Improvements

📃 You can now use the accountStatement query to return an account statement from its id.

Breaking changes

💥 As mentioned in past release notes, the new rejection reasons for CardOut transactions are as follows: RetryWithChipAndPin, PinRequiredForFurtherTransaction, InvalidSecurityNumber, and InvalidExpirationDate. These have been added to the Graph. Please take them into account to avoid breaking changes on your side.