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.

New features​

🤳 Users can now consent using biometry. To try it out for yourself, just clear your browser data. During your next consent, we'll ask you to register your FaceId, TouchId, or Fingerprint. Passcode will only be requested if a user has changed their mobile device.

📲 Some of you wish to send notifications via your own app, to offer a great UX just like the best neobanks. This is now possible. Just define your preferred consent notification channel, SMS or App, by using the new updateUserConsentSettings mutation.

✅ Thanks to the new updateOnboarding and finalizeOnboarding mutations you are not obligated to use our #nocode interfaces. You can onboard customers directly from your product, if you prefer.

Improvements​

🔍 We added new account filters : canManageAccountMembership, canManageBeneficiaries, canInitiatePayments and new accountMemberships filters: status, canInitiatePayments, canManageAccountMembership, canManageBeneficiaries.

📜 The list of transactions associated to a received direct debit mandate can now be retrieved using the API.

🏃 The dashboard lets you sort webhook event logs using 2 new filters: eventId and resourceId. View each webhook's KPIs for the last 7 days: hits, counter, and error rate. We also added 2 new events: Onboarding.created and Onboarding.updated.

🚮 Transactions where paymentProduct is SEPACreditTransfer and status is Upcoming can now be canceled using the cancelTransaction mutation.

Bug fixes​

💳 When requesting physical cards, the Company Name and the Name/Last Name are now truncated to 38 characters. This is a mail delivery requirement.

🌍 The card language (used for 3DS, ATM screens and delivery envelopes) is dynamically assigned. Available languages: DE, FR, IT, NL, EN, ES. When a language is not available, the default language is EN.

Breaking changes​

🔢 Pagination on the accountHolders, accountMemberships, and accounts queries has been fixed. It might break if you implement the filter on the front-end. These queries now only return the requested number of items, rather than all items at once.

New features​

🍏 Swan's Apple Pay offer is expanded across 19 EU countries: 🇦🇹 Austria, 🇧🇪 Belgium, 🇨🇾 Cyprus, 🇪🇪 Estonia, 🇫🇮 Finland, 🇫🇷 France, 🇩🇪 Germany, 🇬🇷 Greece, 🇮🇪 Ireland, 🇮🇹 Italy, 🇱🇻 Latvia, 🇱🇹 Lithuania, 🇱🇺 Luxembourg, 🇲🇹 Malta, 🇳🇱 Netherlands, 🇵🇹 Portugal, 🇸🇰 Slovakia, 🇸🇮 Slovenia, and 🇪🇸 Spain.

18 November​

New features​

👥 Add up to 200 account memberships using just one consent with the addAccountMemberships mutation.

💳 Add up to 200 cards, and print their physical version using just one consent with the addCards mutation. Since card creation is executed asynchronously, we created a new card status: Processing. We deprecated the status filter on the cards query and created statuses so you can filter when there are multiple ones.

✅ The new ibanValidation query helps you verify the format of an external IBAN, get all available bank info (name, BIC code, etc.) and account data available for this IBAN, as well as the reachability of this IBAN across all SEPA schemes.

📃 Sepa Direct Debit Core Mandates are now visible in the API under the account.receivedDirectDebitMandates query and can be suspended with the suspendReceivedDirectDebitMandate mutation or resumed with the resumeReceivedDirectDebitMandate mutation.

🤳🏾 During SCA, avoid asking your customer to enter their phone number, first name, last name, and birth date on the Swan user form. Query parameters during the oauth 2 process let you do this.

Improvements​

🪝 Some webhook events used to be fired a few milliseconds too early, and now are fired right on time.

🔄 Just in case a webhook event is incorrectly integrated on your side, we've added a retry button to the dashboard.

📬 Simulate physical card delivery from the dashboard.

🇪🇺 Our compliance team did a lot of work to allow you to onboard individuals and now companies across all of Europe.

New features​

🤖 Swan's Google Pay offer is expanded across 15 EU countries: 🇦🇹 Austria, 🇧🇪 Belgium, 🇪🇪 Estonia, 🇫🇮 Finland, 🇫🇷 France, 🇩🇪 Germany, 🇬🇷 Greece, 🇮🇪 Ireland, 🇮🇹 Italy, 🇱🇻 Latvia, 🇱🇹 Lithuania, 🇳🇱 Netherlands, 🇵🇹 Portugal, 🇸🇰 Slovakia, 🇸🇮 Slovenia, and 🇪🇸 Spain.

21 October​

New features​

🤳🏾 Embedded Web SCA is out! After 2 years of good and loyal service, it's "bye-bye" to Swan app! Having to use Swan app was a major issue for many of you...so we look forward to receiving your feedback on this improvement!

💳 Supsend and Resume Card directly from the web banking

📬 Get the shipping information of a physical card from the web banking

Improvements​

💳 Display card numbers during the addCard or addSingleUseVirtualCard consent by using the new viewCardNumbers property. This way, you save the time of one consent and can use the card immediately