New features​

⚡ We implemented a fallback option for Instant SEPA Credit Transfers. When an instant transfer is unavailable, whether for technical reasons or due to a manual risk assessment, the instant transfer will run as a standard transfer instead. Your customer won't need to reinitiate a transfer or consent a second time.

• How? We added a new input mode to the initiateCreditTransfer mutation, as well as the new filter includeRejectedWithFallback to the transactions query.
• Tip: We recommend you choose false by default so your customers won't see the rejected instant transfer on their transaction history.

Improvements​

📃 To reduce back and forth with our KYC team, we're asking some partners to collect additional supporting documents during onboarding for some use cases:

• Lithuanian companies: Company Registration, UBO Declaration
• Netherlands, Austria, Luxembourg companies: UBO Declaration
• German self-employed: Self-employed Registration

🇩🇪 For German account onboarding (accountCountry: DEU), three fields are now API-optional:

• UBO birth date: individualUltimateBeneficialOwners.birthDate
• UBO birth city: individualUltimateBeneficialOwners.birthCity
• UBO birth postal code: individualUltimateBeneficialOwners.birthCityPostalCode

📼 We added a new field originTransaction to the API at the transaction level. It contains its parent transaction (for example, the card debit for a card debit reversal).

🧪 We added Instant SEPA Credit Transfers and their associated recalls to the Event Simulator on your Dashboard.

💳 You can now approve authorizations with a partial amount. To do so, indicate the partialAuthorizationAmountValue within your payment control response. Note that not all authorizations can be authorized partially; to identify eligible authorizations, look for the allowsPartialAuthorization:true on the payment control notification we send you.

Bug fix​

⚒️ We fixed some latency issues on our OAuth 2.0 server. Let us know if you still have trouble getting your access tokens.

Breaking changes​

💥 We added a new value SwornStatement in SupportingDocumentPurposeEnum. To avoid breaking changes on your side, please take these into account. We'll request this supporting document during onboarding for Spanish companies.

New features​

🎨 The onboarding and transfer pages have a fresh, new design. And guess what? We'll be ready to share our code and design system with you in the coming weeks.

📈 We added Capital Deposits to the Dashboard > Data section, which was the first step to removing the current Dashboard. Next, you'll be able to upload documents and simulate everything with the Event Simulator.

New features​

🇩🇪 IBANs starting with DE are live after 3 successful months in beta. You can use them via the API or no-code, across all use cases including B2B and B2C! To test them, use the new German onboarding link. You'll find it in your Dashboard, on the Settings/Onboarding tab. The German onboarding flow is a little different, in order to comply with German law. Learn more about requirements for individual and company German accounts.

🪪 Verify the identity of individual account holders using a Qualified Electronic Signature. This new identification level is mandatory for individual German IBANs but can also be used for individual French IBANs in order to avoid the first transfer to finalize their identification process.

Improvements​

⚡ Our reachability on Instant SEPA Credit Transfers has been extended to TIPS in addition to EBA-RT1. We're now connected to most banks for initiating and receiving these transactions.

Breaking changes​

💥 We will begin using some changes we already warned you about, and have added them to the Graph. To avoid breaking changes on your side, please take these into account:

• New transaction types: SepaInstantCreditTransferInRecall and SepaInstantCreditTransferOutRecall.
• New rejection reason codes for SepaInstantCreditTransferOut transactions: CreditorBankTechnicalErrorOccurred and CreditorBankTimeout.

New features​

✅ We added a new account activation tab to the Web Banking. This makes it easy for our no-code customers to finalize the account holder verification process. Just follow the steps.

✉️ Non-verified users can now use reset passcode by email.

💰 On March 1 2023, we will start charging banking fees directly on your customers' Swan accounts. This is the first phase of our billing project. Ultimately, this will enable you to choose which fees you want to charge your customers through Swan, and lead to additional revenue.

Improvements​

📃 You can now use the accountStatement query to return an account statement from its id.

Breaking changes​

💥 As mentioned in past release notes, the new rejection reasons for CardOut transactions are as follows: RetryWithChipAndPin, PinRequiredForFurtherTransaction, InvalidSecurityNumber, and InvalidExpirationDate. These have been added to the Graph. Please take them into account to avoid breaking changes on your side.

New features​

🎨 The Web Banking has a fresh new design for transaction history, members, and card tabs. And guess what? We're getting ready to share our code and design system with you.

🔐 Secure all webhooks by adding a secret in the HTTP Request.

🔁 Automatically trigger the funding of a Swan account based on pre-defined events without user consent. Restricted to account funding SEPA Direct Debit B2B with rolling reserve.

Improvements​

🇫🇷 Automatically fetch UBOs for French registered companies with the updateOnboardCompanyAccountHolder mutation. This was already available in the no-code interface and now it's in the API.

💸 Indicate a spendingLimit when using the addCard mutation. To avoid breaking changes, the spendingLimit is an optional input for the addCard mutation.

🤳🏾 Create a card and add it to Apple Pay or Google Pay simultaneously using the multiple consent feature.

Bug fix​

💰 We have fixed some bugs on Capital Deposit:

• Account Holders linked to multiple Capital Deposits don't have status errors anymore.
• Shareholder status is now properly updated when the funds are deposited.
• We fixed an error that was preventing some Capital Deposits from moving to completion.

Breaking changes​

💥 We will begin using some changes we already warned you about, and have added them to the Graph. To avoid breaking changes on your side, please take these into account:

• New types of Transaction FeeTransaction and InternalDirectDebitTransaction
• A new enum at Transaction level: paymentProduct = Fees and transactionType = FeesOut, FeesIn
• A new payment mandate type InternalDirectDebitPaymentMandate
• A new received payment mandate type InternalReceivedDirectDebitMandate
• A new rejection reason code on SepaInstantCreditTransferOut and SepaInstantCreditTransferIn
• A new enum at Onboarding level: companyType = SelfEmployed

Upcoming breaking changes​

⚠️ In February we will start using a lot of changes that have been added to the Graph. To avoid breaking changes on your side, please take these into account:

• New rejection reasons for CardOut transactions. The new values are: RetryWithChipAndPin, PinRequiredForFurtherTransaction, InvalidSecurityNumber, InvalidExpirationDate.
• New rejection reason codes for SepaInstantCreditTransferOut transactions. The new values are: CreditorBankTechnicalErrorOccurred and CreditorBankTimeout.
• New transaction types SepaInstantCreditTransferInRecall and SepaInstantCreditTransferOutRecall.
• Add Refused in accountHolder.verificationStatus enum

New features​

💸 Initiate SEPA Instant Credit Transfers (SepaInstantCreditTransferOut) transactions using the existing initiateCreditTransfers API mutation with the isInstant input flag. Please note that to guarantee instantaneity, we automatically reject instructions that hit our risk scoring engine (with the RegulatoryReason rejection reason code). In this case, we recommend you suggest your users to issue a new, non-instant SEPA Credit Transfer transaction (SepaCreditTransferOut).

🤖 Use server-to-server consent to avoid any human interaction with the new grantConsentWithServerSignature mutation! To start playing with this highly secure yet easy feature, head to your Sandbox > Developers > Server Consent. If you are interested in using this feature in Live, please reach out to your PIM (Product Integration Manager), check the documentation and start consenting on the go!

⚡ During onboarding, once we have verified the legal representative of the account holder is not a politically exposed person or on a sanctions list, we will distribute the IBAN via API and Web Banking. Most times, this should occur within 10min after ID Verification is completed.

Improvements​

💳 Display the numbers of a physical card using the new viewPhysicalCardNumbers mutation. This is especially useful if you only issue physical cards.

🔐 When using server-to-server consent to add single-use virtual cards, the AddSingleUseVirtualCardSuccessForProjectOwnerPayload will now return a card in ConsentPending status. The card will be enabled after the consent is validated. We would still recommend that you verify the card status before using it.

Upcoming breaking changes​

⚠️ In early January we will start using a lot of changes that have been added to the Graph in order to improve the product in the following month of the release. Please make sure you take it into account before we use them to avoid breaking changes on your side:

• New types of Transaction FeeTransaction and InternalDirectDebitTransaction
• A new enum at Transaction level: paymentProduct = Fees and transactionType = FeesOut, FeesIn
• A new payment mandate type InternalDirectDebitPaymentMandate
• A new received payment mandate type InternalReceivedDirectDebitMandate
• New rejection reason codes on SepaInstantCreditTransferOut and SepaInstantCreditTransferIn
• A new enum at Onboarding level: companyType = SelfEmployed

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.