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 7th), 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!

New features​

🇫🇷 Offer Capital Deposit to your French customers. Enable the registration of new companies directly from your product, by providing an account and proof that the share capital has been wired by shareholders.

📦 Ship a group of cards altogether to the same address using the addCardsWithGroupDelivery mutation. It's more cost-effective, and better for the planet!

Improvements​

🆔 Simulate Sandbox user's identification status from the dashboard

📅 Transactions are better sorted in our web banking thanks to a new transaction.executionDate field. For Upcoming transactions, it reflects the requested execution date. For all other transactions it reflects the creation date.

💳 The maximum number of cards you can create using the addCards mutation has been increased from 200 to 500

🪝 New webhooks are available for creating and updating Received Direct Debit Mandates

📝 SEPA Direct Debit-Out B2B Mandates Amendments can now be registered with Swan using the UpdateReceivedSepaDirectDebitB2bMandate mutation.

Bug fix​

📠 We fixed some bugs for the users of old browsers (IndexedDB issues)

Breaking changes​

🏦 New PaymentProduct and TransactionType enum values have been added in order to provide you with a greater level of detail and an improved experience. These new enum values that were previously listed as COMING SOON are now populated. The enum values marked COMING SOON will be populated during the next release. Some other enum values (listed as SOON TO BE DEPRECATED) will be deprecated in the next Swan release, therefore please make sure you take these changes into account.

🙅🏼‍♂️ We will start sending the following RejectedReasonCodes for card transactions that were created during the last release: CardNotActivated, InvalidPin, InvalidPinAttemptsExceeded

🙅🏾‍♀️ Many new Rejections related to the card and already added during the last release are now populated. They should provide you with a greater level of detail and an improved experience.

New features​

↪️ We fully support all kinds of Received Sepa Direct Debit: Core and B2B.

🔚 You can now close an account by API using the closeAccount mutation.

Improvements​

♻️ It's now possible to release a card authorization using the Event Simulator.

🔍 You can now filter cards by statuses for a given Account Membership using the accountMembership.cards query.

📃 Default pagination has been increased to 50 items per page in the payments query in order to align with other queries.

📝 For each card transaction on the Account Statement, the description field now shows the cardholder name and the last four digits of the card.

✉️ Webhooks offer 2 new onboarding events: Onboarding.Created and Onboarding.Updated

🔄 Exponential backoff when retrying failed webhook events, with up to a maximum of 7 retries.

Bug fix​

✅ The list of accepted characters in the reference field of the initiateCreditTransfer mutation has been updated to match current SEPA guidelines.

💳 The image returned in the cardUrl (card query) is now updated when the Account Member name is updated

💥 When issuing cards, Cardholder names and delivery addresses can include special characters and accents like "Amélie" or "Hauptstraße".

Breaking changes​

🆔 It's been 3 months now (that's 3 releases ago), that partners integrating by API must make sure their UX entices users to prove their identity. To give you time to develop this user flow, we've been texting all users about identity verification as soon as they are created. Starting today, we no longer send new users this sms.