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.

Improvements​

✖️ Cancel Upcoming Instant SEPA Credit Transfers (SepaInstantCreditTransferOut) from your Dashboard.

🖊️ Check returns now have a specific returnReason. These reasons can be tested using the simulateIncomingCheckReturn mutation with the reasonCode field.

🙅🏾 Check why a capital deposit document was refused from your Dashboard > Data > Capital deposits.

🔎 Search accounts by account ID on your Dashboard > Data > Accounts. You will need to enter the full account ID.

💳 Issued card transaction types CardOutDebit, CardOutDebitReversal, CardOutCredit, and CardOutCreditReversal are now received and created 3 times per day (previously 1 time per day). This will improve user experience and positively impact performance.

📱 We added a second SMS/text message provider. Sending text messages will automatically switch between the two providers in case of an outage.

Upcoming breaking changes​

💥 Reminder: on July 15th, the Ultimate Beneficial Owner's (UBO) residency country (individualUltimateBeneficialOwners.residencyAddress.country) becomes mandatory in our onboarding API.

🌐 In 4 weeks, only AccountLanguage enum values for language will be accepted in the onboarding object. Previously, this field was a string and accepted other values. Please take this into account to avoid any breaking changes.

Improvements​

📱 Deactivate users who aren't using Swan anymore. This way, their phone number can be reused for a different user.

🌐 In about 2 weeks, you'll be able to choose and update the preferred language for account memberships, which is used for the invitation email and when ordering and using cards.

• By default, the new AccountMembership.language inherits the Account.language chosen during onboarding.
• The available languages are: Dutch nl, English en, French fr, German de, Italian it, Portuguese pt, and Spanish es.
• Finnish fi won't be supported for the account membership language yet.
• If you're subscribed to the AccountMembership.Updated webhook, you'll receive a webhook notification when AccountMembership.language is live.
• If you've already used the updateAccountMembership mutation to choose the language for an account membership, it won't change with this update.

New features​

🪝 You can now manage webhooks automatically with the API. Use the API to create webhooks dynamically, retry failed events automatically, and keep track of webhook delivery.

Improvements​

⏸️ When an account is suspended or reactivated, we now trigger an Account.Updated webhook notification.

📃 If a KBIS document for a newly-created company is refused at the end of a French capital deposit process, you can now upload a new one and we'll process it again.

Upcoming breaking changes​

🪪 In 4 weeks, we will deprecate the notStarted identification status and replace it with Started to streamline identification flows and reduce confusion.

💳 In 4 weeks, we will start using the new following issued card rejection reason codes: ThreeDsError, PeriodTransactionNumberLimitExceeded, MissingExpirationDate, MissingPin, DigitalWalletDeactivated, DigitalWalletEnrolmentInvalid, DigitalWalletTokenInvalid, DigitalWalletRefusal, DigitalWalletSuspended, InvalidAmount, and CardholderCancellation. The new rejection reasons are available in Sandbox using the Event Simulator.

Improvements​

💰 We're supporting additional fees to provide a more flexible billing solution for our partners. This will allow further customization of our standard fee list, facilitating extra revenue generation. You can check our public documentation for further details.

🔁 Access the returnReason when receiving a return transaction for returned SEPA Credit Transfers and reversed SEPA Direct Debits.

✅ Get better visibility about your account holders' ongoing verification processes by going to Dashboard > Data > Account holders.

Upcoming breaking changes​

💳 For naming consistency, we deprecated choosePINCode in the printPhysicalCard mutation and made it optional. In the coming weeks, choose PINs for your cardholders by using the new optional field choosePin.

⚠️ The list of documentReasonCode for a Refused capital deposit document has been expanded with nine new values. They'll take effect in 4 weeks.

New features​

💸 Offer bulk credit transfer capabilities to your end users. Your end users can now export a list of credit transfers from their accounting or payment tool into a CSV file, then upload the file into their Web Banking app. As a result, they'll initiate multiple credit transfers simultaneously (bulk payments).

🏦 Swan is now available for Open Banking payment initiators. They can connect to our API to initiate SEPA Credit Transfers and Instant SEPA Credit Transfers. Contact your Account Manager if you're interested in this feature.

Upcoming breaking changes​

🙅🏾 In 4 weeks, the status Canceled will be added to CapitalDepositCase, and the status CapitalDepositCanceled to Shareholder. Learn more about statuses for your capital deposit cases and shareholders.

Improvements​

📃 It's now possible to simulate a supporting document request in Sandbox.

📅 We've improved the account holder queries with verificationStatusInfo, allowing you to get the exact date when a verification status was updated.

🔚 Shareholder accounts are now set to Closing upon completion of the capital deposit case. First, we will use CloseAccountReasonType = ComplianceReason. In 4 weeks, we will use the new value CapitalDepositReason.

Breaking changes​

⚠️ The Ultimate Beneficial Owner's (UBO) residency country is now mandatory in our no-code onboarding form.

New features​

🌎 Account holders can now send International Credit Transfers to:

• Exchange euros for another currency and transfer it.
• Transfer euros outside of SEPA.
• Receive International Credit Transfers in euros sent from outside of SEPA.

Please contact your Account Manager if you're interested.

Improvements​

✅ Beneficiary verification between two Dutch accounts is now available on Swan's Web Banking.

Improvements​

📃 Use the newly introduced Dashboard > Data > Onboarding > Supporting documents page to manage the document collection during the account opening process. Learn more about the supporting document collection.

🧪 Simulate a supporting document status update.

⏸️ Suspending an account now triggers an Account.Updated webhook.

Upcoming breaking changes​

⚠️ In 2 weeks, we'll reject any input of the "_" character in the reference field, and sanitize it in the label field within the initiateCreditTransfers mutation, as it's not authorized in SEPA messages. For the reference field, ensure that the content:

• Doesn't start or end with a "/"
• Doesn't have "//"
• Follows this pattern: (regex [A-Za-z0-9 -?.+,/’])

💸 The beneficiaryId input field for the mutation initiateCreditTransfers has been deprecated, and will be removed in 4 weeks.

ℹ️ In the upcoming months, we'll remove the requirement of one unique phone number per user. While each phone number will remain linked to only one user at a time, it can later be reused by different users, like employees, at separate times.

New features​

✅ Before initiating a credit transfer to a Swan account from a Dutch financial institution, payers can now check the account holder's name and account status. This will remove current friction when receiving SEPA Credit Transfers from the Netherlands.

Upcoming breaking changes​

💥 In 4 weeks, the Ultimate Beneficial Owner's residency country becomes mandatory in our no-code onboarding form. In 4 months, our API will enforce this change as well.