๐ On May 21, 2026, public onboarding URLs will switch to Onboarding v2 for all new onboardings, and the v1 public onboarding interface will be retired. The new experience delivers a cleaner onboarding flow with improved data collection for risk assessment and compliance. If you use public onboarding URLs without any prefilling, no action is needed. If you prefill onboarding fields via the API before redirecting users, refer to the migration guide or reach out to your Partner Integration Manager to plan your migration.
โ๏ธ Custom details for the Other purpose: when a supporting document with the purpose Other is requested, a new purposeDetails field on the SupportingDocumentPurpose object specifies what document is needed (for example, "Company structure chart"). Query purposeDetails under requiredSupportingDocumentPurposes and display the description to your account holders to guide their upload. See the supporting documents guide for details.
โฑ๏ธ Starting May 20, 2026, Swan is reducing the Consent Notification endpoint timeout from 3 seconds to 2 seconds. This change applies to consent flows (sensitive operations), not OAuth2 flows such as login or authentication. The shorter timeout gives Swan enough time to fall back to text message within the 3.5-second 3-D Secure (3DS) window. If your integration uses in-app consent notifications, make sure your endpoint responds within 2 seconds, ideally with some margin (around 1.5 to 1.8 seconds). If your response is slower, Swan falls back to text message. No action is required if you don't use in-app consent notifications.
โ ๏ธ Starting September 30, 2026, Onboarding API v1 will be shut down and all v1 endpoints will no longer be available. Onboarding API v2 has been generally available since March 2026, delivering improved data validation, expanded country coverage, and better support for risk assessment and compliance. If you're still using v1, migrate before this date. Refer to the migration guide or reach out to your Partner Integration Manager to plan your transition.
]]>๐ Physical cards that haven't been activated after their estimated delivery date now trigger automatic reminder emails to cardholders. Reminders are sent at configurable intervals until the card is activated. Configure this from your Dashboard > Settings > Notifications.
๐งโ๐คโ๐ง Changing account administrator is now easier to handle for your customers. The dedicated request form determines which supporting documents are required based on company type and reason for change, so requesters upload the right documents on the first attempt. Share the guided form directly with your customers.
๐ซ Swan now requires email address verification when creating a new project in Sandbox. This limits impersonation risk and reinforces security across all projects.
๐ก๏ธ The Web Banking sign-up flow has been updated to strengthen protections against social engineering and fraud. Users now complete sign-up on desktop by entering a 6-digit SMS verification code and their personal information. They then switch to mobile to complete identification via a link sent to their device.
๐ On April 30, the deprecated InternalCreditTransfer value will be removed from the PaymentProduct enum. Remove any references to this value from your transaction queries and filtering before this date.
๐
You can now configure card spending limits with calendar-based periods, in addition to rolling periods. Calendar-based limits reset on a fixed schedule instead of a rolling window. This makes it easier for finance teams to align card budgets with their accounting periods. Configure calendar limits using the new mode field in SpendingLimitInput with options for daily, weekly, or monthly recurrence.
๐ผ๏ธ A new no-code onboarding interface is now in beta and available from your Dashboard. It delivers a cleaner and more consistent onboarding experience, improves data collection for better risk assessment and regulatory compliance, and removes the need to build and maintain the interface yourself. For a visual overview of the new onboarding flow, browse the Figma prototype.
๐งญ The data in your Dashboard Insights tab is updated for Overview, Credit Transfers, All Transactions, and Cards.
Starting April 2, churned account holder data in the Overview tab will also reflect the new account closure reasons.
๐ Starting April 2, Swan provides more granular closure reason codes to help you understand why an account was closed. The new reasons are visible via the API and on your Dashboard.
CloseAccountReasonType values will be replaced with more granular codes: PartnerReason, Inactivity, and CapitalDepositReason. These were previously used for account opening refusals, capital deposit cancellations, and account closures.๐ Starting April 2, CapitalDepositCaseCanceledStatusInfo gains a cancellation reason code when the case status is Canceled. You can also subscribe to the CapitalDepositCaseEvent.Canceled webhook to receive notifications when a capital deposit case is canceled.
Capital deposit cases canceled before April 2 have a null cancellation reason at the capital deposit level. For those cases, refer to the account-level deprecated closure reason CapitalDepositReason.
๐งญ The new Onboarding API is now live in beta. It improves data collection for better risk assessment and regulatory compliance, and delivers a cleaner developer experience with structured inputs, typed responses, and updated mutations and queries. Documentation is updated to reflect all new validations.
๐ CapitalDepositDocumentRefusedStatusInfo now includes an optional reason string field with a free-text explanation of why a document was refused. You can view the exact explanation on your Dashboard, alongside the existing reasonCode value.
๐ Account holders can now be filtered by their Know Your Customer (KYC) verification requirements, both in the Dashboard and through the API. Supported filters include FirstTransferRequired, SupportingDocumentsRequired, UboDetailsRequired, LegalRepresentativeDetailsRequired, OrganizationDetailsRequired, TaxIdRequired, and Other.
๐ Starting April 2, CapitalDepositCaseCanceledStatusInfo gains a cancellation reason code when the case status is Canceled. You can also subscribe to the CapitalDepositCaseEvent.Canceled webhook to receive notifications when a capital deposit case is canceled.
Capital deposit cases canceled before April 2 have a null cancellation reason at the capital deposit level; for those cases, refer to the account-level deprecated closure reason CapitalDepositReason.
โ ๏ธ Starting April 2, three CloseAccountReasonType values are replaced with more granular codes. The deprecated values are PartnerReason, Inactivity, and CapitalDepositReason, previously used for account opening refusals, capital deposit cancellations, and account closures.
Accounts closed before April 2 keep their original reason codes. Refer to the deprecated reason codes for the full mapping.
๐ฉ Our new white-labelled email notifications are now live in Production Live. If you have automations in place, check your KYC operations now in Production Sandbox. Affected notifications:
๐๏ธ In April, weโre rolling out a new whiteโlabelled portal for periodic KYC reviews (โreโKYCโ). It lets account admins confirm or update customer details in a multilingual interface, with pre-filled information and automated email reminders.
๐ป A new desktop sign-up flow for Web Banking is coming soon. Authentication and personal information will be completed on desktop: users receive a 6-digit verification code by SMS, enter the code, create a passcode, then enter personal information before switching to mobile to complete identification. This keeps authentication on a single device, reducing exposure to phishing and social engineering attacks. No changes are required on your side.
]]>๐ฉ Following the December 18 postponement, the new white-labelled email notifications will be activated in Production Live starting March 12. They're now available for testing in Production Sandbox, so you can assess the impact on your KYC operations if you have automations in place.
Our new white-labelled email notifications:
๐ The sign-in flow for Web Banking on desktop was updated on February 18. Users now receive a 6-digit verification code by SMS, and enter both the code and their passcode on desktop, instead of clicking a link and entering their passcode on mobile. This update improves security by making it harder for unauthorized users to access accounts.
๐ We've added idempotency to several mutations, so you can more safely accept payments and fund accounts without risking duplicates:
initiateMerchantPaymentCollection for Internal Direct Debit.initiateSepaDirectDebitMerchantPayment for incoming SEPA Direct Debit.initiateFundingRequest for account funding.โ ๏ธ Starting April 2, the following CloseAccountReasonType values will be deprecated to provide more granular reason codes for account opening refusals, capital deposit cancellations, and account closures:
PartnerReason: use RequestedByHolder instead.Inactivity: use DormantAccount instead.CapitalDepositReason: use any of the new specific reason codes instead.๐ On March 31, accountId becomes mandatory in internationalBeneficiaryDynamicForms and internationalCreditTransferTransactionDetailsDynamicForm. It's available now as optional; update your integration before this date.
๐ On April 1, the following fields will be removed from accountStatement, Account.statements, and generateAccountStatement:
fees: replaced by feeCredits and feeDebits.status: replaced by statusInfo.url in type: moved to statusInfo.๐ Starting February 26, B2B received direct debit mandates will return to ConsentInitiationPending status instead of Canceled when consent is refused or expires. This will allow end users to retry activating the mandate using the enableReceivedDirectDebitMandate mutation.
๐ Swan is regenerating all bank details PDFs created before November 4, 2025, to reflect Swan SAS's new address. Bank details generated after this date already contain the new address.
This applies to both main and virtual IBANs. Subscribe to the Account.Updated webhook to synchronize your system. This webhook is triggered only when main IBAN bank details are regenerated. Query your virtual IBANs separately to synchronize them as well.
The process happens in two stages:
๐งญ SEPA Credit Transfers received without a customer-provided reference now display as empty strings in Web Banking and the API, instead of showing NotProvided.
๐ Identify which user initiated a credit transfer by querying the payment before consent is granted, or by storing user details at the time of initiation.
๐ง The reference field for standing orders has been updated to align with SEPA scheme requirements: the underscore character (_) is no longer accepted. New regex pattern: ^[A-Za-z0-9-?.+\/:,'() ]{1,35}$.
๐ฎ Starting February 5, new rejections apply to the openAccount mutation to prevent fraud patterns involving successive opening and closing of multiple accounts to bypass the account creation limit:
Opened, Suspended, Closing, or Closed). Previously, only Opened accounts counted. This change affects the existing AccountHolderAccountsCreationLimitRejection.Suspended, Swan rejects opening multiple accounts with AccountHolderAccountsSuspendedStatusNotEligibleRejection.๐ซ Starting February 26, the following rules apply to limited accounts:
This change mainly affects the first incoming transfer made while the account holder is still completing verification. During verification, the account remains limited, and any transfer exceeding these limits is automatically rejected.
Capital deposit accounts are unaffected, except that all transfers sent on SWIFT are now rejected for these accounts as well.
]]>๐ You can now subscribe to email notifications directly from the Changelog. Subscribe to receive regular updates about new features, API improvements, and upcoming breaking changes.
๐ The generateTransactionStatement mutation now works for incoming and outgoing Booked International Credit Transfers. Use it to prove a transaction was executed by Swan.
๐ Starting January 19, a new accountId field is available as an optional parameter in internationalBeneficiaryDynamicForms and internationalCreditTransferTransactionDetailsDynamicForm. This field becomes mandatory on March 31, 2026. Update your integration before this date to ensure continued support for international credit transfer queries.
๐ On April 1, the following fields will be removed from the accountStatement and Account.statements queries and from the generateAccountStatement mutation response:
fees will be replaced by feeCredits and feeDebits.status will be replaced by the statusInfo object.url, previously in the type object, will only be available in statusInfo.๐งญ We're releasing a preview of the documentation for our new onboarding API. Built to strengthen risk assessment and regulatory compliance through improved data collection, it also delivers a better developer experience with cleaner mutations and queries, structured inputs, and typed responses. Full launch is planned for Q1 2026.
๐ The Insights tab on your Dashboard now includes new visualizations:
๐ฉ Following an incident during activation of the new white-labelled email notifications announced on December 4, we rolled back to the previous account opening notifications within an hour. The December 18 breaking change for account membership invitations is also postponed.
We plan to activate all new white-labelled notifications in January 2026 with two weeks' notice. You'll be able to test them in Production Sandbox beforehand.
Affected notifications:
๐ค Swan's new MCP (Model Context Protocol) servers give AI assistants direct access to Swan's GraphQL schema and documentation. Use them with Claude Desktop, Claude Code, or Cursor to generate accurate queries and get answers about the API.
๐ Your users can now upload merchant profile supporting documents directly in Web Banking. Retrieve the upload link from supportingDocumentCollectionUrl in the SupportingDocumentCollection object and share it with them.
๐ฉ Account opening email notifications have been rebranded to support your project's branding (logo, accent colors):
Your current configuration has been applied automatically to avoid disruptions. Swan can configure some of these notifications on your behalf; submit a request if you're interested.
๐ The Insights tab on your Dashboard now includes new visualizations:
Coming soon: Support operations graphs.
๐ก๏ธ Starting December 18, we're introducing stricter input validation for several mutations to improve security and error handling. The following fields now enforce specific formats, returning a ValidationRejection for invalid values:
| Mutation | Field | Required format |
|---|---|---|
addVirtualIbanEntry | accountId | Valid UUID |
disableAccountMembership | accountMembershipId | Valid UUID |
resumeAccountMembership | accountMembershipId | Valid UUID |
resumeAccountMembership | consentRedirectUrl | Valid URL |
๐ฉ Starting December 18, the account membership invitation notification will be rebranded with your project's branding (logo, accent colors). If you use a forked version of Web Banking, fetch and deploy the latest version from Swan's repository to continue receiving Swan-sent invitation emails.
]]>