New features​

🎨 We updated your Dashboard interface for capital deposit documents to improve readability and provide easier access to information.

💳 The transaction reason code enum InvalidSecurityNumber is back by popular demand. We previously deprecated it, but we reversed our decision following your feedback.

Upcoming breaking changes​

⛔ In 2 months, we're removing the user.idVerified field. Please start using the new field user.identificationsLevels.expert.

ℹ️ In 4 weeks, the cardDetails.Card field will no longer be mandatory.

New features​

📄 Generate transaction statements with the API to prove a transaction was executed by Swan. Today, the mutation works for incoming and outgoing Booked SEPA and Instant SEPA Credit Transfers. Up next, we'll make the feature available on your Dashboard and in Swan's Web Banking, as well as for other transaction types.

👥 Add trusted beneficiaries with the API and Web Banking to facilitate credit transfers. Account members can send credit transfers to beneficiaries according to their membership permissions. This provides an extra layer of security, reducing the risk of sending transfers to unintended recipients.

Breaking change​

ℹ️ As announced on August 29th, we implemented a webhook subscription limit. In order to avoid overconsumption, you're now restricted to 10 subscriptions per Sandbox event and 5 subscriptions per Live event.

New features​

📥 Provide transaction supporting documents with the API. Build your own communication flow between you and your users to request documents justifying a transaction ID, then submit the requested documents to Swan with the API. Also, you can subscribe to the SupportingDocumentCollection.Updated webhook to learn when a document is requested by Swan for a transaction ID. If you choose not to implement the API feature, you'll continue to use the current email process.

📨 Proactively share supporting documents when initiating an transaction with the API. To bypass potential requests for supporting documents, you can attach a supporting document to a transaction proactively when initiating the transaction with the API. In that case, if a document is required at a later stage, Swan won't need to contact the user to provide it.

Breaking change​

ℹ️ As announced on November 30th and July 19th, we removed the user > identificationStatus. Instead, use the identificationLevels booleans.

Upcoming breaking changes​

📃 In 4 weeks, we're adding a new value to the SupportingDocumentPurpose enum: CompanyFormationRegistration.

New features​

📥 You can now export the user and onboarding data available on the Dashboard in .csv format, either from your Dashboard or with the API by calling the exportUserData and exportOnboardingData mutations. More data will be available to export soon.

Improvements​

📈 The Insights tab on the Dashboard has been updated to include the Accounts funded step in the Onboarding funnel. You can now access a detailed conversion rate of account holders that have opened and funded their accounts.

📊 We’ve added two new graphs to the transactions data within your Dashboard's Insights tab. We now display the total volume of incoming and outgoing transactions by payment method.

🚌 Payment Control now allows you to filter transactions related to transportation expenses. Use the TransactionTransportType field, which mirrors the Transit Transaction Type Indicator shared from Mastercard.

Breaking changes​

ℹ️ As announced on July 19th, the onboardingUrl parameter of our onboarding object is now set to null when an onboarding is finalized.

Upcoming breaking changes​

⚠️ In the coming weeks, we'll introduce an additional permission to initiate a credit transfer to an unsaved beneficiary, meaning not previously added as a trusted beneficiary.

• From October 21st, account members must have both canInitiatePayment and canManageBeneficiary permissions to initiate a credit transfer to an unsaved beneficiary.
• Swan will grant existing account members with canInitiatePayment with the canManageBeneficiary on October 21st.

Please ensure that new account members, created after October 21st, have both permissions to initiate a credit transfer to an unsaved beneficiary.

Improvements​

👤 In order to reduce user binding errors when adding account memberships, we now consider the account member's birthLastName. If it matches their lastName, we won't raise a lastNameMatchError.

🧭 Enriched transaction information is now available for all card transactions, including those from the start of Swan. When available, detailed merchant and transaction data can be accessed through the API, Dashboard, and Web Banking.

📄 Get information about supporting documents related to onboarding and account holder verification from your Dashboard. We also revamped the document collection portal.

👯 Access and change the Sandbox user you're impersonating when using Web Banking in the Sandbox environment.

Breaking changes​

💳 As announced on August 1st, we now use additional issued card rejection reason codes: CanceledByCardHolder, DigitalCardDeactivated, DigitalCardEnrollmentInvalid, DigitalCardRefusal, DigitalCardSuspended, DigitalCardTokenInvalid, InPersonTransactionsNotAuthorized, MagstripeNotSupported, MerchantNotFound, PeriodTransactionNumberLimitExceeded, PinRequired, and ThreeDsError.

Upcoming breaking changes​

🔢 In 4 weeks, we're introducing a webhook subscription limit. In order to avoid overconsumption caused by too many subscriptions to the same event, you'll be restricted to 10 subscriptions per Sandbox event and 5 subscriptions per Live event.

⚠️ In 4 weeks, we're adding a new value to the SupportingDocumentPurpose Enum: PepDeclaration.

⛔ In 8 weeks, if you call the API with a user access token attributed to a Blocked user, it will be rejected.

Improvements​

✖️ Partners can cancel a capital deposit case in the early stages of a case with the API mutation cancelCapitalDepositCase.

🛟 We updated the Swan Support Center to better serve your users and operational support teams. The redesign brings a sleek, user-friendly interface and clear architecture, simplifying navigation. New articles are available in eight languages, and we're working on delivering even more optimized content. The support request form has also been enhanced for quicker issue resolution.

Use the Swan Support Center either by sharing links directly or by using the content to inspire your own support articles.

Upcoming breaking changes​

💳 In 4 weeks, we'll start using some new, additional, issued card rejection reason codes: CanceledByCardHolder, DigitalCardDeactivated, DigitalCardEnrollmentInvalid, DigitalCardRefusal, DigitalCardSuspended, DigitalCardTokenInvalid, InPersonTransactionsNotAuthorized, MagstripeNotSupported, MerchantNotFound, PeriodTransactionNumberLimitExceeded, PinRequired, and ThreeDsError.

New feature​

↩️ You can now request a refund for outgoing SEPA Direct Debits. A new returnTransaction mutation allows your users to request a refund on SepaDirectDebitOut and InternalDirectDebitOut transactions with a Booked status following the SEPA rules. Refund through API will be available only for direct debits created after the 12 June 2024.

Breaking changes​

ℹ️ As announced on March 15th, the Ultimate Beneficial Owner's (UBO) residency country (individualUltimateBeneficialOwners > residencyAddress > country) is now mandatory in our onboarding API.

🌐 As announced on June 21st, only AccountLanguage enum values for language are accepted in the onboarding object.

Upcoming breaking changes​

📃 In 4 weeks, we're deprecating the SupportingDocumentStatus > downloadUrl field in the supporting document collection process.

🔍 In 4 weeks, we'll set the onboardingUrl parameter of our onboarding object to null when an onboarding is finalized.

🔍 We added a new value to the SupportingDocumentCollectMode enum: EndCustomerCcPartner. We'll start to use it in 4 weeks.

🪪 In 2 months, we're finally removing the user > identificationStatus field. We announced its deprecation on November 30th, and it's replaced with the identificationLevels booleans and identification collection.

New features​

💳 Our first cards are reaching expiration in 2024. Therefore, we deployed an automatic renewal process so virtual and physical cards renew automatically before they expire. Your cardholders can update their delivery address for the new physical card if needed.

Users can now choose their PIN when printing a physical card. To allow this for your cardholders, set the new choosePin boolean to true. Allowing cardholders to choose their PIN will reduce friction to use their physical card, therefore driving more transactions.

Improvements​

🔎 In 1 week, we're generating Bank Details documents for all accounts created before 16 November 2023, which weren't available automatically when we launched this feature. Subscribe to the Account.Updated webhook to synchronize your system if necessary.

🌐 Choose and update the account membership language, 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 isn't 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, the language won't change with this update.

Upcoming breaking changes​

⚠️ In 4 weeks, we're adding new values to the SupportingDocumentPurpose and SupportingDocumentType enums.

• SupportingDocumentPurpose enum: PersonalIncome, PersonalSavings, Investment, Donation, Inheritance, RealEstateIncome, GamblingPrizeWinnings, Trade, CompanyTreasury, and CompanyObligations
• SupportingDocumentType enum: WinningsCertificate and Invoice

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.