New features​

📖 Learn about the new Verification of Payee regulation, its impact on your users, and how you can update your Swan integration to improve your payment experience.

Improvements​

👥 Get more balance information for booked transactions using BookedTransactionStatusInfo.balanceAfter. This object provides:

• amount - replaces the existing BookedBalanceAfter.amount (see upcoming breaking changes).
• sequenceNumber - new account-level transaction counter for new transactions (historical transactions show null).

🧭 Customize column width on all Dashboard pages to make the data easier to read.

🪝 Two new webhooks are now available to update you on rolling reserve changes. TransactionRollingReserve.Updated is triggered when the release date is changed, and TransactionRollingReserve.Released will indicate that the reserved funds are now available.

API updates​

Upcoming breaking changes​

📄 Starting August 28th, we'll start using these new, already available enum variables: USPersonStatusDeclaration and ProofOfBusinessActivity for SupportingDocumentPurpose, and W9, W8, and CertificateOfLossOfNationality for SupportingDocumentType.

👥 Starting December 31st, the bookedBalanceAfter field will be removed from the transaction query. Please use the balanceAfter.amount on BookedTransactionStatusInfo.

Coming up​

Passcode reset improvements, card insurance, and more! Check out Swan's public roadmap to see what's in the works. 🚀

New features​

🔗 Send a SEPA Direct Debit B2B mandate registration link to users with the canInitiatePayments permission. Get the link from your Dashboard > Data > Accounts page.

Improvements​

💳 One-off single use virtual cards now default to expiring 30 days after creation. This applies when SpendingLimitPeriod is set to Always in the addSingleUseVirtualCard and addSingleUseVirtualCards mutations. You can change this by setting a custom cardContractExpiryDate.

🧭 Transaction confirmation documents now follow a new, more readable naming convention that includes the document language. The new format is: TransactionConfirmation_[transactionId]_[documentLanguage].

Updates​

🪪 Starting August 7th, we'll recommend QES as the identification method for German accounts, replacing the current Expert level. If you use Auto, no action is needed. This change will apply automatically.

API updates​

Upcoming breaking changes​

🛑 Starting August 18th, the initiateCheckMerchantPayment mutation will return a new rejection: MerchantPaymentAlreadyExistsRejection. This occurs when you try to create a merchant payment, but the CMC7 value is already used by an existing payment that hasn't been Rejected or Canceled. If the existing payment with the same CMC7 was Rejected or Canceled, your mutation will still succeed.

💳 Starting August 21st, refund transactions will be linked to the paymentId of their original debit authorization when referenced by merchants. This change affects you only if you expect debit clearing transactions on a debit authorization.

API updates​

Upcoming breaking changes​

🔐 Starting July 10th, failed consent attempts will trigger the Consent.Failed webhook. Previously, failed consents triggered Consent.Granted, due to a bug. The new webhook is already available in your Dashboard.

✉️ Starting July 21st, the shippingProvider field in PhysicalCardToActivateStatusInfo and PhysicalCardRenewedStatusInfo will be migrated from a String to an ENUM. On the same day, the shipping provider values La Poste and CORREOS will be removed.

Improvements​

🧭 Account statement documents now follow a new, more readable naming convention that includes the document language. The new format is: AccountStatement_[ProjectName]_[AccountNumber]_[period]_[documentLanguage].

👫 Account member invitations with a ConsentPending status will now expire if the inviter doesn't provide consent before the consent period ends. This automatically changes the account membership status to Disabled, allowing you to inform the user to send a new invitation.

• If you're subscribed to the AccountMembership.Updated webhook, you'll receive a notification when the membership is Disabled.
• When querying AccountMembershipDisabledStatusInfo, you'll see the reason InvitationExpired.

✍️ You can now use CheckMerchantPayment to track the statuses and balances of French check payments.

API updates​

Upcoming breaking changes​

⚠️ Starting July 1st, the shippingProvider field in PhysicalCardToActivateStatusInfo and PhysicalCardRenewedStatusInfo will be migrated from a String to an ENUM. Please note that the shipping providers La Poste and CORREOS will soon be deprecated.

💶 On August 1st, we're removing the merchantPayment field in the InitiateCheckMerchantPaymentSuccessPayload, use checkMerchantPayment instead. We're also deprecating merchantPayment.

New features​

💳 You can now disable users from updating their card settings in Swan's Web Banking from your Dashboard > Web banking settings tab. When disabled, users with the CanUpdateCards permission can only update card limits through your product, not Web Banking.

Improvements​

🧭 We've made several improvements to your Dashboard:

• The Dashboard search now returns more accurate results. Results automatically narrow as you type and add more details. This update is available on the Account Holders, Onboarding, Account, Account Memberships, and Capital Deposits pages.
• Filters have a new look across all Dashboard pages to help you find data more efficiently. We added quick filters for all verification statuses on the Account Holders page based on user feedback. We removed the Verifications page because the new filters provide the same information in a more accessible way.

🔍 We've added new filters to enhance searching for transaction information by amount and execution date in the API:

• Amount filters: we added isAboveAmount and isBelowAmount. We also updated the amount filter to return an exact match. These filters are now cumulative and will replace the current amount field in the transactions search filter (see upcoming breaking change).
• Execution date filters: we added isAfterExecutionDate and isBeforeExecutionDate.

✍️ The requestMerchantPaymentMethods mutation now validates your SEPA Creditor Identifier (SCI) when you request SEPA Direct Debit. If the SCI is invalid, the mutation will reject it, helping you avoid blocked transactions in the future.

📝 You can now retrieve all transactions initiated by a standing order using the standingOrder.transactions query.

API updates​

Upcoming breaking changes​

👥 Starting June 19th, the amount field will be removed from the transactions search filter. Please use the amount filters to refine your search.

💸 Starting June 19th, the beneficiaryId and isMyOwnIban input fields will be removed from the initiateCreditTransfers mutation. The isMyOwnIban field will become optional.

🛑 Starting June 19th, a new rejection type, ValidationRejection, will be used to validate an input in the initiateCreditTransfers mutation.

🚫 Starting June 19th, calls to scheduleStandingOrder with an invalid reference will be rejected. See the API reference for the regex pattern.

New features​

📥 You can now export account data in .csv format from your Dashboard or with the API by calling the exportAccountData mutation.

Improvements​

🪪 Auto identification is now smoother. To automatically skip the identification process for eligible users on projects configured to bypass it, add the accountMembershipId to the authorization URL when inviting account members.

🤏 To protect you and the merchant from fraud, merchant payments may now have a paymentAmountLimit that applies to each individual transaction. This limit may be applied during the review of the merchant payment method or later, based on risk factors. It's available in the merchantPaymentMethod type in the API, for Card, SEPA Direct Debit (Core and B2B), and French check payments. Setting a limit will trigger a MerchantPaymentMethod.Updated webhook.

New features​

💳 You can now set a preferred shipping provider for physical cards, when calling the addCards mutation. To do this, select shippingProvider in the physicalCardCustomOptions input.

📥 You can now export account membership data in .csv format from your Dashboard or with the API by calling the exportAccountMembershipData mutation.

Improvements​

🧭 We improved the executionDate field for card transactions. It now shows the precise timestamp from Mastercard, giving you additional visibility on the time when the transaction was received by the network.

🔎 We've released several updates to improve your Dashboard:

• You can now apply new filters to the following Dashboard pages:
  • Accounts: IBAN
  • Account memberships: email, firstName, and lastName
  • Account holders: firstName and lastName
  • Onboarding: email
  • Users: firstName and lastName
• We've increased the size of the search bar, making it easier to view and input text.
• The search bar now automatically removes unwanted spaces from your input, ensuring more accurate results.

Update​

🧾 Starting May 1st, invoices will be issued through our new billing provider, Lago. The format will change, but the content will remain the same.

New features​

📥 You can now export card data in .csv format from your Dashboard or with the API by calling the exportCardData mutation.

🔔 You can now activate two new text message notifications for rejected card payments due to an incorrect PIN or an invalid card expiration date. Activate them from your Dashboard > Settings > Notifications.

💌 A new white-labeled email notification for card expiration is now available! Activate it from your Dashboard > Settings > Notifications.

Update​

🔴 To provide more detailed feedback, errors in the addCards inputs, especially the physical card delivery address and spending limit, will now return a ValidationRejection instead of an error.

New feature​

🇮🇹 Italian IBANs are now are live! Generate onboarding links from your Dashboard > Settings > Onboarding.

Improvements​

🐓 French company onboardings are now smoother. In addition to previously auto-filling UBOs, the VAT number, and the address, we now automatically retrieve representative information and company type when you add the company’s registration number. You no longer need to ask users if they’re the legal representative; instead, compare their data to the retrieved information.

API updates​

Upcoming breaking change​

👥 Starting on April 10th, the type of AccountMembershipsFilterInput.accountId will change from String to ID, making it consistent with the other filters.

New feature​

📱 Users can now change the phone number associated with their Swan account securely and independently. Tap New phone number? Update it at the beginning of any login or consent flow and follow the prompts.

Update​

⭐️ Effective March 13, all new business debit cards are issued with a new Banking Identification Number (BIN). Card numbers with the new BIN start with 543946 instead of the current 547395. The BIN for existing cards will be updated automatically when the cards are renewed.

API updates​

Upcoming breaking change​

📓 Effective May 1st, providing gender for Ultimate Beneficial Owners (UBO) is mandatory due to Swan’s reporting obligations. This field includes more granular options than the title field, set to be deprecated on May 1st.