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.

New features​

📖 Documentation has always been a priority at Swan. Today, we introduce the next era of our docs, with a stronger information hierarchy, dedicated product, Developers, and Partnership sections, and a powerful search that unites everything—including API Reference. There's more content, and everything was created with accessibility in mind. Discover the new docs.swan.io!

🛡️ We added new user roles to the Dashboard! Open your Team Management section to edit access for your team. This improves data privacy & security.

Improvements​

💳 To avoid unwanted notifications for Suspended physical cards (amongst other things), 3DS Strong Customer Authentication for card transactions on eCommerce websites won't be triggered for a card that doesn't have the status Enabled, or a physicalCard that doesn't have the status Activated. Authorization received for cards that aren't Enabled or Activated will still appear as Rejected.

Breaking changes​

⚠️ Queries using pagination are now limited to 100 elements to load per request.

New features​

✅ Before initiating a credit transfer to a Dutch IBAN from another financial institution, you can now check the account holder's name and account status using the new beneficiaryVerification query.

Improvements​

💳 Order cards in the language of your account. When ordering cards for an account member not already bound to a user, the card language will be the account language and not English by default.

Breaking changes​

⚠️ To prevent capital deposit failures caused by validation rejections related to shareholder onboarding, we are including the same validation checks as those used for onboarding, and we now answer with a ValidationRejection. This provides more specific and restrictive rejection criteria.

New features​

🇳🇱 Dutch accounts can now initiate outgoing Instant SEPA Credit Transfers.

Improvements​

📈 Performance for your Dashboard > Developers> Webhooks page is improved and now supports all volume and search types.

💳 We've improved your Dashboard > Data > Cards page with new sorting options. Sort by creation date and last update. Also, we added the addressLine2 in the shipping details.

Breaking changes​

⚠️ As announced in December 2023, all webhooks created before January 2024 are no longer available on your Dashboard following a technical migration.

Upcoming breaking changes​

💥 For naming consistency, we deprecated the enum value Recurring in InternalPaymentMandateSequence and InternalDirectDebitSequence. Instead, use the new value Recurrent. The deprecated value will be removed in 4 weeks.

✅ We're preparing for changes to the Capital Deposit API, coming in 2 weeks. Therefore, the API reference for the createCapitalDepositCase mutation has been updated to include regex examples. We're also implementing the same validation checks used for onboarding to provide more specific and strict rejection criteria.

New features​

🇳🇱 Dutch accounts can now receive incoming Instant SEPA Credit Transfers. Outgoing instant transfers will be available soon.

💸 As part of the European Payment Accounts Directive, we included an annual fees statement in this month's account statement. This is available on the last page of the PDF automatically generated for January 2024.

Improvements​

🛡️ For security reasons, we added a new screen on the desktop-to-mobile flow when a user signs up. They need to confirm their own mobile phone number.

New features​

🏦 Swan is now available for Open Banking aggregators. They can connect to our API to access the account and transactions. If you are interested in this, contact us!

Improvements​

📄 Validate a capital deposit case and change the status of capital deposit documents with the Event Simulator or the Testing API.

Upcoming breaking changes​

⚠️ In 4 weeks, queries using pagination will be limited to 100 elements to load per request.

💥 For API consistency, we deprecated the value Recurring for InternalDirectDebitSequence and DirectDebitSequence. Please use Recurrent instead in the mutations addInternalDirectDebitPaymentMandate and addSepaDirectDebitPaymentMandate.

New features​

🌍 In February, Swan IBANs will be able to receive incoming SWIFT transfers. To help you prepare for this new feature, you can test the reception of an incoming International Credit Transfer using our Testing API simulateIncomingInternationalCreditTransferReception or Event Simulator.

Improvements​

💳 Card option and spending limit values are displayed in the consent screen language instead of English by default.

🆔 To simulate different stages of the identification process for Sandbox users, you can now use the Event Simulator or the Testing API with the createSandboxIdentification and updateSandboxIdentification mutations. Additionally, we deprecated the identificationStatus and identificationLevels fields when creating and updating Sandbox users from the Dashboard.

New features​

🇪🇸 Swan's new Physical Card Issuing Hub in Spain is now live. Physical card shipment to Spanish end-customers now takes less time! Please contact your account manager if you're interested.

Improvements​

📄 We've added accountHolder and onboarding in the supportingDocumentCollection query to allow you to stop collecting documents via e-mail. It's more integrated and efficient, making follow-up easier. You also get better visibility on document collection throughout the onboarding process (status, content …).

Breaking changes​

⚠️ We've added new values to the SupportingDocumentPurpose enum: LegalRepresentativeProofOfIdentity, UltimateBeneficialOwnerProofOfIdentity, NIFAccreditationCard, PresidentDecisionOfAppointment, AdministratorDecisionOfAppointment, and FinancialStatements. We're also deprecating ProofOfIdentity.

New features​

🇫🇮 Our end-user interfaces are now available in Finnish.

Improvements​

🤳🏾 To improve the user experience for some payment control use cases, the card spending limits are no longer displayed on the consent screen for the mutations addCardsWithGroupDelivery, addCards, and updateCard (exception: single-use virtual cards).

⚡ Instant transfers are activated by default when initiating SEPA Credit Transfers with Swan's Web Banking interface. They fallback to regular transfers when instant isn't available.

🚓 To fight efficiently against money laundering, we implemented a new card ATM withdrawal spending limit. These limits are enforced at the account holder level and can only be modified by Swan. Review the limits

💼 We added the object relatedCapitalDepositCase to the shareholder query in order to provide details about the capital deposit case for any shareholder.

🪝 We added a new webhook, CapitalDepositDocument.Created, for when a new a document for a case or a shareholder is created. List of webhooks

‼️ Reminder: the date for addSepaDirectDebitPaymentMandate must match the format YYYY-MM-DD. Otherwise, we'll return a ValidationRejection.

Upcoming breaking changes​

⚠️ On February 5th, we're doing a database migration of our webhooks. Only logs from January 1st on will be migrated, meaning all data from 2023 and before will be lost. From February 5th on, webhook history will only be kept for 100 days. This change won't impact the subscriptions.