New features​

📊 Looking for information about your product's performance? Check out the new Insights tab on your Dashboard, where you'll find data dashboards providing insights into transactions, onboardings, and more.

New features​

🇳🇱 Dutch IBANs starting with NL are live! You can test Dutch IBANs with the API or on your Dashboard > Settings > Onboarding.

💡 For each country, Swan must comply with different requirements depending on local laws. Learn more about requirements for individual and company accounts in the Netherlands.

Improvements​

ℹ️ We added a reason to the ReleasedTransactionStatusInfo query. You can now see why a card authorization was released. Possible values: Captured, Expired, AdviceReceived, MerchantReleased, ManuallyReleased, and Other.

📅 You can now schedule an Internal Direct Debit transaction. In the initiateMerchantPaymentCollection mutation, use the requestedExecutionAt field.

❌ The cancelTransaction mutation now supports canceling incoming Internal Direct Debit transactions with the status Upcoming.

Breaking changes​

💥 There are two key changes to the addInternalDirectDebitPaymentMandate mutation: (1) We removed the scheme and merchantProfileId fields. Use paymentMethodId instead. (2) The InternalDirectDebitPaymentMandateId is no longer returned in the success payload.

Upcoming breaking changes​

⚠️ The isInstant field for initiateCreditTransfers is deprecated and will be removed in 7 weeks. Please use mode instead to initiate a SEPA Instant Credit Transfer. By using mode=InstantWithFallback, your SEPA Instant Credit Transfers will "fallback" to a regular SEPA Credit Transfer if instant isn't available.

🔍 In the users query, search moved to the filters category and requires at least 3 characters. The old search will be deprecated in 4 weeks.

Improvements​

🔄 When providing consent, users can now request a new text message if the original text message wasn't received.

📃 We added the account object in accountStatement. Use it to link an account to its generated account statements.

🔍 The transactions query can now be filtered by transactionId.

Breaking changes​

⚠️ In 4 weeks, we're adding the new value GeneralAssemblyMinutes to the SupportingDocumentPurpose enum.

Improvements​

💳 We've added new fields to Payment Control messages:

• terminalId: The payment terminal that was used to initiate the transaction.
• mechantPostalCode: The postal code of the merchant that initiated the transaction (this field will start being populated in October 2023, note that not all merchants communicate this information).
• digitalCardWalletProvider: The digital token used for the transaction (when applicable), possible values are: ApplePay, GooglePay, Merchant.

🧪 The simulateIncomingInternalDirectDebitReturn mutation allows to simulate a return on an Internal Direct Debit transaction.

New features​

🤩 We redesigned the Data tab on the Dashboard to be more customer centric. View a list of unique users connected to your project with a 360 view of their accounts and cards. These improvements should help your operations and customer support teams.

Improvements​

💸 We redesigned the Web Banking transfer page following your feedback. It's ready to welcome the upcoming International Credit Transfer feature.

🪶 We added two new fields at the transaction level: reservedAmount and reservedAmountReleasedAt. Keep an eye on these fields to improve the user experience with account funding and accepting payments, and soon in Web Banking and Dashboard.

Upcoming breaking changes​

⚠️ The scheme and merchantProfileId inputs are deprecated and will be removed from the addInternalDirectDebitPaymentMandate API mutation in 6 weeks. These inputs were redundant with the paymentMethodId input.

⚠️ In the addInternalDirectDebitPaymentMandate mutation's AddInternalDirectDebitPaymentMandateSuccessPayload, the InternalDirectDebitPaymentMandateId field will no longer be returned starting 12 weeks from now. Please use the id available in the paymentMandate object instead.

New features​

🫰🏽 As part of our Accept Payments feature, merchants can add a logo to their merchant profile using the addMerchantProfile mutation. An existing merchant profile can be updated using the requestMerchantProfileUpdate mutation.

Improvements​

🍂 When a SEPA Credit Transfer is initiated using mode=InstantWithFallback and the transfer is rejected by the beneficiary bank, a fallback will always be triggered except when the recipient account is unknown, closed, or the account holder is deceased.

⛔ As part of our Accept Payments feature, we deleted a few API mutations and fields that were previously flagged as deprecated. Please note that the deprecated mutations and fields are no longer accessible or supported in any capacity following this release. Learn more about Accepting Payments

• MerchantPaymentProduct becomes MerchantPaymentMethod.
• requestMerchantPaymentProducts becomes requestMerchantPaymentMethods.
• requestMerchantPaymentProductsInput becomes requestMerchantPaymentMethodsInput.
• InternalDirectDebit is now divided into two different mutations: InternalDirectDebitStandard & InternalDirectDebitB2B. As a result, InternalDirectDebitStandardPaymentMethodInput & InternalDirectDebitB2BPaymentMethodInput are new input names to request such payment methods.
• CheckMerchantPaymentProduct becomes CheckMerchantPaymentMethod.
• CheckPaymentProductInput becomes CheckPaymentMethodInput.

🧾 Limited accounts can no longer initiate credit transfers.

🙅🏻‍♀️ We added a new enum value to accountHolder.verificationStatus: Refused.

Upcoming breaking changes​

🌍 As part of our future International Credit Transfers offer, new values will be added to the TransactionType enum: InternationalCreditTransferIn, InternationalCreditTransferOut, InternationalCreditTransferInReturn, and InternationalCreditTransferOutReturn.

🌍 As part of our future International Credit Transfers offer, a new value will be added to the PaymentProduct enum: InternationalCreditTransfer.

New features​

🤳🏻 To improve text message deliverability, receive text messages from AUTHLINK instead of AUTHMSG when consenting to sensitive operations.

Improvements​

📱 Consent or log in with a QR code if there's an issue receiving the text message.

😃 Run consents and user queries with a project access token.

🔄 On your Dashboard > Data tab, check out the Transactions page to view all transactions for your project.

⚠️ We are starting to use the new enum values for FeesType that were added to the API three weeks ago.

New features​

🇪🇸 Instant SEPA Credit Transfers for Spanish account are live. Learn more about requirements for individual and company Spanish accounts.

🦢 Swan's design system, Swan Lake, is public! A natural complement to Swan's open source frontend, Lake gives you a head start with a collection of building blocks for an accessible banking UX/UI.

Improvements​

🛒 Manage your merchant profiles from the Dashboard > Data > Accounts page.

📃 Generate a PDF version of SEPA Direct Debit payment mandates. Merchant customers might need to send this PDF to their banks.

📄 Generate custom account statements with your designated 3-month date range directly from the Web Banking > History page.

📈 To increase the identity verification conversion rate, when the identification fails, we now include a re-engagement link in the text message sent to the user.

👀 We added an unmasked IBAN field for both the debtor and creditor when querying SEPACreditTransferTransaction and SEPADirectDebitTransaction. You can choose how much information to expose when using these queries.

😃 Call the transaction query with a user access token; a project access token is no longer required.

Upcoming breaking changes​

⚠️ In three weeks, we'll start using new enum values for FeesType that have been added to the API. To avoid breaking changes on your side, please take these into account.

New features​

↪ When using the Accept Payments feature, merchants can get paid by SEPA Direct Debit with both B2B and Core methods. The feature is only in Sandbox right now; please let us know if you're interested in beta testing!

🔍 There is a new transactions query to make searching transactions easier.

Improvements​

📑 During the KYC process, you can upload supporting documents Swan requires from your end customers, and request a review. Contact us to activate this feature and receive fewer reminder emails from Swan.

✅ With Internal Direct Debit B2B, use the addReceivedInternalDirectDebitB2bMandate mutation to receive the debtor's consent when declaring a payment mandate.

📣 Sometimes, the KYC process is delayed because of website outages for European business registries. Subscribe to the Swan status page to learn about these delays. There is a new section called Onboarding - European Business Registries where we will post a live incident about who is affected and the overall level of impact.

New features​

🪪 Swan takes another step forward to increase the conversion rate to onboard individual French accounts. PVID (Prestataire Verification d'Identité à Distance) is the latest French identity verification process that provides a fast, secure way to onboard end-customers, with a better user experience. Thanks to PVID, the first transfer or electronic signature is no longer required for EU users opening accounts with French IBANs.

Improvements​

🇪🇺 Every word in every language for Web Banking, Onboarding, text messages, and more (almost 7000 words in 6 languages), was reviewed by our new localization team. We hope your experience in the supported language of your choice improves significantly, and please continue sharing your language-specific feedback with us.

📈 We improved webhook performance and resiliency thanks to a full refactoring.

Breaking changes​

📱 We'll no longer send a text message to users when their identity is successfully verified. Why? With the User webhooks, you can track their progress and notify them however you choose.