New features​

💰 Add an Account detail tab in the web banking menu (level 1) lets you access the main IBAN, manage virtual IBANs, and update account settings.

👩🏼‍💻 The web banking has a new profile page that allows users to manage their languages, reminds them to verify their identity, and provides access to FAQ and support.

Improvements​

⛔ UBO doesn't mean anything to French "syndicat de copropriété" and "associations" so we removed them from the nocode onboarding.

⚖️ A "legal representative" tile was added to the dashboard for company account holders.

🔗 The authentication SMS was changed from swan.io to authmsg.co, for better whitelabeling.

🔐 Most of the time, we won't display the Captcha anymore — the one displayed when the user enters their phone number. This doesn't take away from the level of security.

🌬️ The Refund API mutation can now be used on SepaInstantCreditTransferIn transactions

Breaking changes​

📅 The deprecated field executionDate used as an input for the initiateCreditTransfers mutation was permanently removed and replaced by requestedExecutionAt.

🈲 For regulatory reasons, we will no longer accept special characters in the SepaBeneficiary name input fields for the initiateCreditTransfers mutation. Chinese and Cyrillic characters will no longer be allowed.

New features​

⚡ We can now receive Instant SEPA Credit Transfers! These will be shown as SepaInstantCreditTransferIn in the TransactionTypeEnum.

💳 Manage multiple card products from the dashboard, with different designs and spending limits.

Improvements​

💳 Order cards from the web banking with all our API capabilities: card design, format (Virtual, Physical or Single Use), spending settings, one or multiple members, grouped or individual delivery.

📅 The Rolling Reserve for B2B SepaDirectDebitIn transactions in an Account Funding context has been decreased from 4 to 3 inter-bank business days + the booking date/time for SDD-In transactions was changed from 6PM CET to 8PM CET.

🚥 Funding Sources are no longer suspended when a rejection is received for SepaDirectDebitIn within the B2B scheme created for Account Funding. When a rejection is received for InsufficientFunds, core scheme Funding Sources won't be suspended either. This can be simulated via the testing API and by adding a reasonCode in the simulateIncomingSepaDirectDebitReject and simulateIncomingSepaDirectDebitReturn API mutations.

🗓️ We've removed the 14 calendar day limitation on the requestedExecutionAt for initiateFundingRequest. When the requestedExecutionAt input is used, SEPADirectDebitIn transactions created with Upcoming status can now be canceled up to 1 day before the executionDate and 1 hour before Swan cut-off.

Bug fix​

💥 A very small proportion of users experienced errors when using their 6-digit passcode during consent. This has been fixed.

Breaking changes​

👥 The hierarchy of Membership rights has been updated: A member cannot give permissions to others, that they don't themselves have. We will keep you posted on the new rejection that will occur in case this happens.

Upcoming breaking changes​

📅 By the end of October, the deprecated field executionDateused as an input for the intitiateCreditTransfer mutation will be permanently removed and replaced by requestedExecutionAt.

New features​

🌐 We changed the web banking navigation to improve your end-customer's UX. This is the first step of our web banking redesign. Thanks so much for all your feedback!

🔎 We added an API Reference to help you during integration. Use it alongside the Doc and the Explorer.

Improvements​

🌬️ We added some shortcuts to our GraphQL Schema. Now you can get the legal representative account membership directly from the account using account.legalRepresentativeMembership and the account created by the onboarding using onboarding.account (only for onboardings created after 2022-02-01)

Breaking changes​

🔗 The new web banking navigation comes with new URL formats. If you use deep links, you'll have to update them accordingly.

🔐 For security reasons, PUT method is no longer supported when uploading a supporting document.

🏅 For performance reasons, we added a rate-limiting to 60 requests per minute for introspections queries.

💰 For Partners using Account Funding, the mutation addExternalAccountBalance is now deprecated. We just created a new one: addOrUpdateExternalAccountBalance. Both have the following behavior, with no breaking impacts: if you already added a balance for a specific date and then you add another balance for the same date, the existing balance will be updated with the characteristics you set, so you'll always have only one balance for the day.

Upcoming breaking changes​

👥 By the end of September, we will update the hierarchy of Membership rights: A member will not be able to give permissions they don't themselves have, to other members. We will keep you posted on the new rejection that will occur in case this happens.

📅 By the end of October, the deprecated field executionDate used as an input of the intitiateCreditTransfer mutation will be permanently removed and replaced by requestedExecutionAt.

Improvements​

🚔 We added a security captcha when there is some doubt concerning the phone number entered, in order to increase the level of security. This should impact only 0.5% of users.

💳 To avoid strong authentication for the end customer each time the card number is revealed, we now allow calling the same consentUrl for 5 minutes after consenting. For this, we advise you to store the consentId on your side and to run a consent query each time before reusing the consentUrl to check that the consent status is Accepted and the updatedAt is less than 5min.

New features​

📈 Account funding beta testers, you can now push your end customers' balances in order to calculate a funding limit.

Improvements​

🤳 Review and optimize the user experience of our Strong Customer Authentication flows and encourage biometric authentication each time the passcode is used.

📃 Add a supporting document section in the dashboard to consult the list of uploaded documents required for KYC/KYB and upload new ones.

📈 2 new countries are available for company onboarding: Cyprus and Bulgaria

🔍 We added more search filters and sorting in the account list and in the account membership list.

🪝 A new webhook account.closing is triggered when closing an account

✅ The sepaBeneficiary.name input of the initiateCreditTransfer API mutation now needs to have a minimum of 2 characters.

♻️ A new simulation (simulateReleaseReservedBalance) lets you release the reserved balance for a transaction. As a reminder, the reserve balance depends on the rolling reserve

⛔ When the blockSDD field is set to true at the account level, SDD-Out transactions presented on any virtual IBAN attached to it will be rejected.

🛑 Onboarding API data validation: new rejection type raised in case of incorrect data format/type

Bug fix​

⌛ We fixed some performance issues with the card and the account membership list

Breaking changes​

📃 The Supporting Document status has been renamed from ReviewPending to PendingReview.

💥 accountHolder.fundingLimitand and accountHolder.instantFundingLimit were deprecated since the previous release and have been totally removed.

Upcoming breaking changes​

📃 We changed the upload method from PUT to POST. PUT still works but is now deprecated and will be removed by end of August.

🎙️ Next release, we will implement a rate-limiting to 60 req/minutes for introspections queries.

New features​

📈 Instantly load your customers' accounts with SEPA Direct Debit. This is one of our biggest features of the year! Contact us if you're interested in joining the beta testers group.

🤳🏿 Accept up to 100 consents with just one single Strong Customer Authentication.

📄 When finalizing your customers' onboarding, you can now use the API to consult the list of minimum required supporting document purposes. Using this feature will reduce a lot of back-and-forths. In 90% of account openings, we require documents for just one single purpose. However, if an individual presents a higher risk than expected, we ask for additional documents.

Improvements​

✅ Clearly see where you are in the activation process, right from the dashboard header. Just click “Activate.”

📃 If you're opening accounts for companies, you can now upload supporting documents using the nocode onboarding interface.

👤 For a better UX, we decided to remove the last page of user registration (Sign in).

🔍 You can now search a first or last name in the account membership list.

🪝 A new webhook onboarding.updated is triggered when onboarding is finalized.

🔄 Funding sources are listed in the dashboard.

✖️ A funding source with Pending or Enabled status can be Canceled by any account member with Can Manage Account Membership user rights using the cancelFundingSource mutation.

👮🏻 The Account Verification status of a SDD B2B funding source is automatically switched to verified when the Rolling Reserve amount is released from the reserved balance (if no R-transaction has been received)

💳 A new reason code has been added for refused card transactions: MerchantShouldResubmitAuthorization

💸 Card spending was not being released when the authorization amount was released.

Bug fix​

💳 Some card options were recently desynchronized at our card processor. We've fixed this.

Breaking changes​

💥 Account funding is in beta, so there are sometimes breaking changes: accountHolder.fundingLimit and accountHolder.instantFundingLimit is deprecated and moved to a new resource accountHolder.fundingLimitSettings respectively in accountHolder.fundingLimitSettings.fundingLimit and accountHolder.fundingLimitSettings.instantFundingLimit.

Upcoming breaking changes​

📃 Next release, in early July, we will rename the Supporting Document status ReviewPending to PendingReview.

New features​

📈 Seamlessly load your customers' accounts, with SEPA Direct Debit. Contact us if you want to join the beta testers group.

💳 Skip identity verification for some corporate cardholders.

🔐 Users can reset their passcode via facial recognition in less that 3 minutes.

Improvements​

🔍 The dashboard data list now includes search, count, filters, and more. We'll add more each cycle, so you can enhance your customer support experience. Let us know if you have any feedback or special wishes.

📬 Simulate the reception of a physical card using the Testing API. The event simulator will soon feature this, as well.

New features​

🎨 Full redesign of our dashboard to improve the Developer Experience.

Improvements​

❌ Your customer service folks can easily cancel upcoming credit transfers, or cancel and suspend cards, thanks to some new buttons.

🗒️ Account statements are listed in the dashboard, or you can generate them yourself.

📆 In the onboarding API, we added creation date and last updated date, and improved some error messages.

Bug fix​

🆔 The cardId is now correctly sent within the redirection URL of the activatePhysicalCard mutation.

Breaking changes​

🔢 We activated pagination on onboarding.

New features​

📈 Display your customers' data on the dashboard. This is a great first round; the next release will feature even more data with added filters and a search field.

💳 Cardholders can now activate a card after receiving it, thanks to the new activatePhysicalCard mutation. They just have to input the identifier printed on the card and give their consent.

📃 Upload supporting documents using the generateSupportingDocumentUploadUrl mutation during the onboarding. This way you don't have to ask users a second time by email.

Improvements​

🛒 To facilitate the interpretation of the merchantCategoryCode, you can now get the description of each code in the merchantCategoryDescription field for every transaction of CardTransactiontype.

Bug fix​

💵 The amounts displayed in thecard.spending.amount.value field are now more consistent. Values previously returned as 0 will now be returned as 0.00

Breaking changes​

👩🏻‍💻 To update the verification status of an individual account holder, you have two options:

• From the dashboard using the event simulator for Update Account Holder (instead of the sandbox users page).
• From the Testing API with the updateAccountHolder mutation (instead of updateSandboxUser)

📉 We've decided to reduce the number of cards we can issue using addCards mutation up to 250 while we fix a performance issue.

Upcoming breaking changes​

💳 Please note that after the next release (estimated for April 7), the physical card identifier will return null if its status is ToActivate.

New features​

🦺 A new Testing API exposes the event simulators and Sandbox user management. Developers can now call them programmatically and perform end-to-end tests without having to connect to the Dashboard. Big improvement to our developer experience! Try it now!