<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>Swan Docs Blog</title>
        <link>https://docs.swan.io/changelog</link>
        <description>Swan Docs Blog</description>
        <lastBuildDate>Thu, 05 Nov 2026 00:00:00 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <copyright>Copyright © 2026 Swan.</copyright>
        <item>
            <title><![CDATA[5 November 2026]]></title>
            <link>https://docs.swan.io/changelog/5-november-2026</link>
            <guid>https://docs.swan.io/changelog/5-november-2026</guid>
            <pubDate>Thu, 05 Nov 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[New features]]></description>
            <content:encoded><![CDATA[<h2 class="anchor anchorWithStickyNavbar_LWe7" id="new-features">New features<a href="https://docs.swan.io/changelog/5-november-2026#new-features" class="hash-link" aria-label="Direct link to New features" title="Direct link to New features">​</a></h2>
<p>💳 <code>inAppProvisioningData</code> has a new <code>googleWallet</code> argument to support Google's <strong><a href="https://developers.google.com/pay/issuers/apis/push-provisioning/early-access" target="_blank" rel="noopener noreferrer">Unified Push Provisioning API</a></strong>. It's available in production on request, once your Google Console is set up with Swan. We'll update the <a href="https://docs.swan.io/topics/cards/digital/#integration">provisioning guide</a> with instructions on how to integrate.</p>
<h2 class="anchor anchorWithStickyNavbar_LWe7" id="improvements">Improvements<a href="https://docs.swan.io/changelog/5-november-2026#improvements" class="hash-link" aria-label="Direct link to Improvements" title="Direct link to Improvements">​</a></h2>
<p>🔎 You can now view and filter <a href="https://docs.swan.io/topics/merchants/">merchant payment methods</a> from your Dashboard. Open the new <strong>Payment methods</strong> tab under <strong>Dashboard</strong> &gt; <strong>Merchants</strong>, then filter by status, type, or merchant profile ID.</p>
<h2 class="anchor anchorWithStickyNavbar_LWe7" id="api-updates">API updates<a href="https://docs.swan.io/changelog/5-november-2026#api-updates" class="hash-link" aria-label="Direct link to API updates" title="Direct link to API updates">​</a></h2>
<h3 class="anchor anchorWithStickyNavbar_LWe7" id="breaking-changes">Breaking changes<a href="https://docs.swan.io/changelog/5-november-2026#breaking-changes" class="hash-link" aria-label="Direct link to Breaking changes" title="Direct link to Breaking changes">​</a></h3>
<p>🇫🇷 For French companies, Swan no longer prefills ultimate beneficial owners (UBOs) or individual legal representatives from the company registry, to limit the sharing of personal data. Instead, collect this information from your users and submit it during onboarding. Swan continues to retrieve company details, including the legal name, trade name, legal form, registration date, company type, VAT number, and business address.</p>
<ul>
<li><a href="https://docs.swan.io/preview/new-onboarding/legacy-onboarding/company#retrieve-data">Legacy onboarding</a>: UBOs and individual legal representatives are no longer prefilled.</li>
<li><a href="https://docs.swan.io/preview/new-onboarding#company-registry-data">Current onboarding</a>: <code>companyInfoRegistryData</code> returns an empty <code>relatedIndividuals</code> array and still returns <code>relatedCompanies</code>. Collect UBOs and individual legal representatives from your user and send them in <code>company.relatedIndividuals</code>.</li>
</ul>
<h3 class="anchor anchorWithStickyNavbar_LWe7" id="upcoming-breaking-changes">Upcoming breaking changes<a href="https://docs.swan.io/changelog/5-november-2026#upcoming-breaking-changes" class="hash-link" aria-label="Direct link to Upcoming breaking changes" title="Direct link to Upcoming breaking changes">​</a></h3>
<p>📅 From <strong>1 December 2026</strong>, <code>inAppProvisioningData</code> will refuse a Google Pay digital card queried without <code>googleWallet</code>, returning <code>BAD_USER_INPUT</code>, as Google ends legacy push provisioning at the end of December. If you <a href="https://docs.swan.io/topics/cards/digital/guide-add">add cards to Google Wallet</a> from your own app, migrate to the Unified Push Provisioning API before this date. Apple Pay and manual provisioning aren't affected.</p>
<h3 class="anchor anchorWithStickyNavbar_LWe7" id="reminders">Reminders<a href="https://docs.swan.io/changelog/5-november-2026#reminders" class="hash-link" aria-label="Direct link to Reminders" title="Direct link to Reminders">​</a></h3>
<p>👀 On <strong>12 November 2026</strong>, three changes <a href="https://docs.swan.io/changelog/15-october-2026#upcoming-breaking-changes">announced on 15 October</a> take effect:</p>
<ul>
<li>Territory codes (for example, <code>REU</code>) are no longer accepted in country fields. Use the country code instead (<code>FRA</code>).</li>
<li>New birth date rules apply to legal representatives, account admins, and ultimate beneficial owners.</li>
<li>The Account Information Service (AIS) returns the Origin Transaction ID instead of the Payment ID in <code>extra.additional_information</code>.</li>
</ul>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[15 October 2026]]></title>
            <link>https://docs.swan.io/changelog/15-october-2026</link>
            <guid>https://docs.swan.io/changelog/15-october-2026</guid>
            <pubDate>Thu, 15 Oct 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Improvements]]></description>
            <content:encoded><![CDATA[<h2 class="anchor anchorWithStickyNavbar_LWe7" id="improvements">Improvements<a href="https://docs.swan.io/changelog/15-october-2026#improvements" class="hash-link" aria-label="Direct link to Improvements" title="Direct link to Improvements">​</a></h2>
<p>🌍 <strong>The birth postal code is now only required in France.</strong></p>
<ul>
<li><a href="https://docs.swan.io/topics/onboarding/company/fields#individual-birth-information">Company onboarding</a>: for ultimate beneficial owners and legal representatives, it's no longer required when the account country isn't France.</li>
<li><a href="https://docs.swan.io/topics/users#signup">User sign-up</a>: it's only asked when the user was born in France. You no longer need to collect or <a href="https://docs.swan.io/developers/using-api/authentication/guide-get-token-user#url-parameters-optional">prefill <code>birthPlacePostalCode</code></a> for users born outside France.</li>
</ul>
<p>Birth date, city, and country are unchanged.</p>
<h2 class="anchor anchorWithStickyNavbar_LWe7" id="api-updates">API updates<a href="https://docs.swan.io/changelog/15-october-2026#api-updates" class="hash-link" aria-label="Direct link to API updates" title="Direct link to API updates">​</a></h2>
<h3 class="anchor anchorWithStickyNavbar_LWe7" id="upcoming-breaking-changes">Upcoming breaking changes<a href="https://docs.swan.io/changelog/15-october-2026#upcoming-breaking-changes" class="hash-link" aria-label="Direct link to Upcoming breaking changes" title="Direct link to Upcoming breaking changes">​</a></h3>
<p>🌍 From 12 November 2026, territory codes (for example, <code>REU</code> for Réunion) will no longer be accepted in country fields such as birth, address, ID document issuing, and company registration. Use the corresponding country code instead (<code>FRA</code>). Existing records will be updated accordingly.</p>
<p>Onboardings where the account holder lives <a href="https://docs.swan.io/partnership/overview/country-coverage">in an area where Swan doesn't offer accounts</a> will be <code>Invalid</code>. Other country fields, like card delivery addresses, aren't affected. For more details, refer to the <a href="https://docs.swan.io/topics/onboarding/individual/fields#address">individual</a> and <a href="https://docs.swan.io/topics/onboarding/company/fields#company-address">company</a> onboarding fields.</p>
<p>🐣 From 12 November 2026, onboardings will apply <strong>new birth date rules for legal representatives, account admins, and ultimate beneficial owners.</strong></p>
<ul>
<li>Account admins of <a href="https://docs.swan.io/topics/onboarding/company/fields#administrator-birth-information">company</a> and <a href="https://docs.swan.io/topics/onboarding/individual/fields#birth-information">individual</a> accounts must be 18 or older. This also applies to verification renewals and <a href="https://docs.swan.io/topics/accounts/memberships/admin-change">account admin changes</a>.</li>
<li><a href="https://docs.swan.io/topics/onboarding/company/fields#individual-birth-information">Legal representatives</a> (<code>LegalRepresentative</code> or <code>LegalRepresentativeAndUltimateBeneficialOwner</code>) must be 18 or older. A legal representative under 18 will be rejected. There's no maximum age.</li>
<li>Ultimate beneficial owners (<code>UltimateBeneficialOwner</code>) can be any age, including minors. This also applies to verification renewals.</li>
</ul>
<p>A birth date in the future is still rejected. Account members aren't affected.</p>
<p>🔝 At the end of November 2026, <strong>funding limits will be removed</strong>. They belong to a product Swan no longer offers. The following are deprecated accordingly:</p>
<ul>
<li>Mutation: <code>addFundingLimitSettingsChangeRequest</code>.</li>
<li>Queries: <code>fundingLimitSettingsChangeRequests</code>, <code>AccountHolder.fundingLimitSettings</code>, and <code>AccountHolder.fundingLimitSettingsChangeRequests</code>.</li>
<li>Simulation: <code>updateFundingLimitSettingsChangeRequest</code>.</li>
</ul>
<p>🔌 From 12 November 2026, the <strong>Account Information Service (AIS)</strong> will replace the Payment ID with the <strong>Origin Transaction ID</strong>. In AIS transaction responses, the <code>extra.additional_information</code> field will return the Origin Transaction ID (<code>originTransactionId</code>) instead of the Payment ID (<code>paymentId</code>). This change simplifies the reconciliation of fee transactions in accounting tools, such as DATEV in Germany. The Payment ID will no longer be available through AIS. If your integration relies on it, submit a <a href="https://partner-support.swan.io/hc/en-gb/requests/new" target="_blank" rel="noopener noreferrer">Partner support request form</a>. See the <a href="https://docs.swan.io/topics/open-banking/ais#field-mapping">AIS field mapping</a>.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[1 October 2026]]></title>
            <link>https://docs.swan.io/changelog/1-october-2026</link>
            <guid>https://docs.swan.io/changelog/1-october-2026</guid>
            <pubDate>Thu, 01 Oct 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[New features]]></description>
            <content:encoded><![CDATA[<h2 class="anchor anchorWithStickyNavbar_LWe7" id="new-features">New features<a href="https://docs.swan.io/changelog/1-october-2026#new-features" class="hash-link" aria-label="Direct link to New features" title="Direct link to New features">​</a></h2>
<p>🏦 You can now create a <a href="https://docs.swan.io/topics/capital-deposits/france/guide-create-case-v2/">capital deposit case</a> with the new <a href="https://api-reference.swan.io/mutations/create-capital-deposit" target="_blank" rel="noopener noreferrer"><code>createCapitalDeposit</code></a> mutation, which uses the same input format as <a href="https://docs.swan.io/topics/onboarding/">Swan onboarding</a>. A single call creates the onboarding for the company being incorporated and for each shareholder (company or individual), and returns one onboarding ID per entity. Check the <a href="https://docs.swan.io/topics/capital-deposits/france/guide-create-case-v2/">guide</a> for the full reference payload and step-by-step instructions.</p>
<h2 class="anchor anchorWithStickyNavbar_LWe7" id="improvements">Improvements<a href="https://docs.swan.io/changelog/1-october-2026#improvements" class="hash-link" aria-label="Direct link to Improvements" title="Direct link to Improvements">​</a></h2>
<p>👮 <a href="https://docs.swan.io/topics/accounts/#suspension-reasons">Suspension reasons</a> are now available in the API and your Dashboard. <a href="https://docs.swan.io/topics/accounts/closure/guide-get-suspension-info">Retrieve them</a> with the <code>suspensionReasons</code> field on <a href="https://api-reference.swan.io/objects/account-suspended-status/" target="_blank" rel="noopener noreferrer"><code>AccountSuspendedStatus</code></a>, or view them on the account detail page in your Dashboard. When several reasons are active, all of them are displayed. The list is empty for accounts suspended before <strong>September 21, 2026</strong>.</p>
<p>📊 CSV <a href="https://docs.swan.io/topics/payments/overview/guide-export/">transaction exports</a> are now safer to open in spreadsheet applications. Values in payment labels or references no longer run as formulas.</p>
<p>🔎 The <a href="https://docs.swan.io/topics/capital-deposits/">capital deposit</a> case view in your Dashboard is redesigned to make each step clearer and shorten the time to certification. Each case now shows its current step, who's responsible, and the next required action at a glance.</p>
<h2 class="anchor anchorWithStickyNavbar_LWe7" id="api-updates">API updates<a href="https://docs.swan.io/changelog/1-october-2026#api-updates" class="hash-link" aria-label="Direct link to API updates" title="Direct link to API updates">​</a></h2>
<h3 class="anchor anchorWithStickyNavbar_LWe7" id="upcoming-breaking-changes">Upcoming breaking changes<a href="https://docs.swan.io/changelog/1-october-2026#upcoming-breaking-changes" class="hash-link" aria-label="Direct link to Upcoming breaking changes" title="Direct link to Upcoming breaking changes">​</a></h3>
<p>🏦 The <a href="https://api-reference.swan.io/mutations/create-capital-deposit-case" target="_blank" rel="noopener noreferrer"><code>createCapitalDepositCase</code></a> mutation is <strong>deprecated</strong> in favor of <a href="https://api-reference.swan.io/mutations/create-capital-deposit" target="_blank" rel="noopener noreferrer"><code>createCapitalDeposit</code></a>. Both mutations run in parallel during the migration period, so existing integrations aren't affected. Make sure to migrate to the new mutation before the end of 2026, as the <code>createCapitalDepositCase</code> will be removed in the first quarter of 2027.</p>
<p>👮 On <strong>November 2, 2026</strong>, the <code>reasonInfo</code> field on <a href="https://api-reference.swan.io/objects/account-suspended-status/" target="_blank" rel="noopener noreferrer"><code>AccountSuspendedStatus</code></a> will be <strong>deprecated</strong>, joining the already deprecated <code>reason</code> field. Migrate to <a href="https://docs.swan.io/topics/accounts/closure/guide-get-suspension-info"><code>suspensionReasons</code></a>. Both deprecated fields stay available during the migration period.</p>
<p>🌍 New <a href="https://docs.swan.io/topics/payments/credit-transfers/international/#dynamic-forms">beneficiary details</a> are mandatory for Swiss Franc (CHF) and Thai Baht (THB) International Credit Transfers. When you <a href="https://docs.swan.io/topics/payments/credit-transfers/international/guide-initiate">initiate a transfer</a> and save a new beneficiary, or <a href="https://docs.swan.io/topics/payments/credit-transfers/international/guide-add-beneficiary">add a trusted international beneficiary</a>, provide the following:</p>
<ul>
<li>From <strong>November 2, 2026</strong>: <code>address.city</code> and <code>address.country</code> for CHF beneficiaries.</li>
<li>From <strong>November 30, 2026</strong>: <code>email</code> and <code>state</code> (in Thailand) for THB beneficiaries.</li>
</ul>
<p>These requirements apply to new and existing beneficiaries. If you saved a CHF or THB beneficiary without these details, create a new beneficiary with all required details before initiating the transfer. Otherwise, the transfer will fail.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[17 September 2026]]></title>
            <link>https://docs.swan.io/changelog/17-september-2026</link>
            <guid>https://docs.swan.io/changelog/17-september-2026</guid>
            <pubDate>Thu, 17 Sep 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Improvements]]></description>
            <content:encoded><![CDATA[<h2 class="anchor anchorWithStickyNavbar_LWe7" id="improvements">Improvements<a href="https://docs.swan.io/changelog/17-september-2026#improvements" class="hash-link" aria-label="Direct link to Improvements" title="Direct link to Improvements">​</a></h2>
<p>🪝&nbsp;You can now <a href="https://docs.swan.io/topics/cards/digital/guide-get-info">track digital card creation and status changes</a>, including Apple Pay and Google Pay card provisioning, by subscribing to <a href="https://docs.swan.io/topics/cards/digital/#tracking-status"><code>DigitalCard.Created</code> and <code>DigitalCard.Updated</code></a> webhooks.</p>
<p>To retrieve the updated digital card, use the query <a href="https://api-reference.swan.io/queries/digital-card/" target="_blank" rel="noopener noreferrer"><code>digitalCard</code></a>.</p>
<p>🇩🇪 <a href="https://docs.swan.io/topics/accounts/memberships/#country-req"><code>taxIdentificationNumber</code></a> is now optional when onboarding German account members. Tax identification numbers are no longer required to add, invite, or update memberships to accounts registered in Germany.</p>
<h2 class="anchor anchorWithStickyNavbar_LWe7" id="api-updates">API updates<a href="https://docs.swan.io/changelog/17-september-2026#api-updates" class="hash-link" aria-label="Direct link to API updates" title="Direct link to API updates">​</a></h2>
<h3 class="anchor anchorWithStickyNavbar_LWe7" id="upcoming-breaking-changes">Upcoming breaking changes<a href="https://docs.swan.io/changelog/17-september-2026#upcoming-breaking-changes" class="hash-link" aria-label="Direct link to Upcoming breaking changes" title="Direct link to Upcoming breaking changes">​</a></h3>
<p>⚠️&nbsp;The <code>cardContractId</code> field on <a href="https://api-reference.swan.io/interfaces/digital-card#" target="_blank" rel="noopener noreferrer"><code>DigitalCard</code></a> is <strong>deprecated</strong>. This field is renamed <code>cardId</code> and carries the same information.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[30 July 2026]]></title>
            <link>https://docs.swan.io/changelog/30-july-2026</link>
            <guid>https://docs.swan.io/changelog/30-july-2026</guid>
            <pubDate>Thu, 30 Jul 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Improvements]]></description>
            <content:encoded><![CDATA[<h2 class="anchor anchorWithStickyNavbar_LWe7" id="improvements">Improvements<a href="https://docs.swan.io/changelog/30-july-2026#improvements" class="hash-link" aria-label="Direct link to Improvements" title="Direct link to Improvements">​</a></h2>
<p>🔄 <a href="https://docs.swan.io/topics/payments/credit-transfers/sepa/vop/incoming-vop-requests/#verification-outcomes">Incoming Verification of Payee (VoP) requests</a> for accounts in <code>Closing</code> status now go through standard matching, returning Match, Close match, or No match. Previously, these requests returned Impossible to match, blocking senders at the verification step. This aligns VoP with incoming credit transfers, where <code>Closing</code> accounts <a href="https://docs.swan.io/changelog/18-june-2026">already accept transfers to settle outstanding debts</a>. Requests for accounts in <code>Closed</code> or <code>Suspended</code> status still return Impossible to match.</p>
<p>🔄 Document rejection reason labels are now clearer and unified across onboarding, KYC, transaction, and capital deposit flows in your Dashboard. Each label explains exactly why a document was rejected, even when there's no additional rejection message.</p>
<h2 class="anchor anchorWithStickyNavbar_LWe7" id="api-updates">API updates<a href="https://docs.swan.io/changelog/30-july-2026#api-updates" class="hash-link" aria-label="Direct link to API updates" title="Direct link to API updates">​</a></h2>
<h3 class="anchor anchorWithStickyNavbar_LWe7" id="upcoming-breaking-changes">Upcoming breaking changes<a href="https://docs.swan.io/changelog/30-july-2026#upcoming-breaking-changes" class="hash-link" aria-label="Direct link to Upcoming breaking changes" title="Direct link to Upcoming breaking changes">​</a></h3>
<p>🛡️ Starting <strong>August 31, 2026</strong>, the <a href="https://docs.swan.io/topics/payments/direct-debit/guide-add-mandate"><code>addReceivedSepaDirectDebitB2bMandate</code></a> mutation enforces SEPA format validation on two fields:</p>
<ul>
<li><code>creditorIdentifier</code>: must follow the <a href="https://docs.swan.io/topics/merchants/online/sdd/#sci">SEPA Creditor Identifier (SCI)</a> structure, including an ISO two-letter country code, two-digit checksum, creditor business activity code, and national identification feature.</li>
<li><code>mandateReference</code>: must be a valid SEPA mandate reference of up to 35 characters.</li>
</ul>
<p>This prevents creating mandates with incorrect data, which later cause <code>MandateInvalid</code> rejections on outgoing SEPA Direct Debit B2B transactions.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[16 July 2026]]></title>
            <link>https://docs.swan.io/changelog/16-july-2026</link>
            <guid>https://docs.swan.io/changelog/16-july-2026</guid>
            <pubDate>Thu, 16 Jul 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[New features]]></description>
            <content:encoded><![CDATA[<h2 class="anchor anchorWithStickyNavbar_LWe7" id="new-features">New features<a href="https://docs.swan.io/changelog/16-july-2026#new-features" class="hash-link" aria-label="Direct link to New features" title="Direct link to New features">​</a></h2>
<p>💳 You can now stop a physical card from renewing automatically, without canceling it. Call the new <a href="https://explorer.swan.io/?query=bXV0YXRpb24gQ2FuY2VsUmVuZXdhbCB7CiAgY2FuY2VsUGh5c2ljYWxDYXJkUmVuZXdhbChpbnB1dDogeyBjYXJkSWQ6ICIkWU9VUl9DQVJEX0lEIiB9KSB7CiAgICAuLi4gb24gQ2FuY2VsUGh5c2ljYWxDYXJkUmVuZXdhbFN1Y2Nlc3NQYXlsb2FkIHsKICAgICAgX190eXBlbmFtZQogICAgICBwaHlzaWNhbENhcmQgewogICAgICAgIHN0YXR1c0luZm8gewogICAgICAgICAgc3RhdHVzCiAgICAgICAgfQogICAgICB9CiAgICB9CiAgfQp9Cg==&amp;tab=api" target="_blank" rel="noopener noreferrer"><code>cancelPhysicalCardRenewal</code></a> mutation while the card is in the <code>ToRenew</code> status. The card remains active until its expiry date, then expires rather than being renewed and reissued.</p>
<h2 class="anchor anchorWithStickyNavbar_LWe7" id="improvements">Improvements<a href="https://docs.swan.io/changelog/16-july-2026#improvements" class="hash-link" aria-label="Direct link to Improvements" title="Direct link to Improvements">​</a></h2>
<p>📦 You can now add multiple cards to Apple Pay or Google Pay with the new <a href="https://explorer.swan.io/?query=bXV0YXRpb24gQWRkRGlnaXRhbENhcmRzIHsKICBhZGREaWdpdGFsQ2FyZHMoCiAgICBpbnB1dDogewogICAgICBjYXJkSWRzOiBbIiRZT1VSX0NBUkRfSURfMSIsICIkWU9VUl9DQVJEX0lEXzIiXQogICAgICB3YWxsZXRQcm92aWRlcjogQXBwbGVQYXkKICAgICAgY29uc2VudFJlZGlyZWN0VXJsOiAiJFlPVVJfUkVESVJFQ1RfVVJMIgogICAgfQogICkgewogICAgLi4uIG9uIEFkZERpZ2l0YWxDYXJkc1N1Y2Nlc3NQYXlsb2FkIHsKICAgICAgX190eXBlbmFtZQogICAgICBkaWdpdGFsQ2FyZHMgewogICAgICAgIGlkCiAgICAgICAgc3RhdHVzSW5mbyB7CiAgICAgICAgICBzdGF0dXMKICAgICAgICB9CiAgICAgIH0KICAgIH0KICB9Cn0K&amp;tab=api" target="_blank" rel="noopener noreferrer"><code>addDigitalCards</code></a> mutation. It works like <code>addDigitalCard</code>, but it requires only a single consent flow for the entire batch.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[18 June 2026]]></title>
            <link>https://docs.swan.io/changelog/18-june-2026</link>
            <guid>https://docs.swan.io/changelog/18-june-2026</guid>
            <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Improvements]]></description>
            <content:encoded><![CDATA[<h2 class="anchor anchorWithStickyNavbar_LWe7" id="improvements">Improvements<a href="https://docs.swan.io/changelog/18-june-2026#improvements" class="hash-link" aria-label="Direct link to Improvements" title="Direct link to Improvements">​</a></h2>
<p>🔗 You can now control <a href="https://docs.swan.io/topics/onboarding/#links">public onboarding links</a> separately for creating and updating accounts. If you've already turned on public links, both are on by default — adjust them anytime in your Dashboard under <strong>Onboarding</strong> &gt; <strong>Public links</strong>.</p>
<p>🔄 All accounts closed before 2 April 2026 now use the <a href="https://docs.swan.io/topics/accounts/closure/#closure-reason-codes">2026 closure reason codes</a>. All your accounts use the same codes, so you can run data analysis across your full history.</p>
<p>🔄 All capital deposits canceled before 2 April 2026 now use the <a href="https://docs.swan.io/topics/capital-deposits/#cancelation-reason-codes">2026 cancelation reason codes</a>. As with closures, all your capital deposits use the same codes, so you can run data analysis across your full history.</p>
<p>📩 You can now see how your onboarding and Know Your Customer (KYC) email notifications are configured, from your Dashboard under <strong>Settings</strong> &gt; <strong>Notifications</strong>. The following notifications are now visible:</p>
<ul>
<li><strong>Your account terms and conditions</strong> — always on; can't be deactivated or edited for compliance reasons.</li>
<li><strong>First transfer</strong> — contact Swan to change it.</li>
<li><strong>Request supporting documents</strong> — contact Swan to change it.</li>
<li><strong>Request supporting documents reminders</strong> — contact Swan to change it.</li>
</ul>
<p>🔍 You can now filter <a href="https://docs.swan.io/topics/accounts/ibans/#virtual">virtual IBANs</a> by status — <code>Enabled</code> or <code>Canceled</code> — with the <code>status</code> filter on <a href="https://api-reference.swan.io/objects/virtual-ibanentry-connection/" target="_blank" rel="noopener noreferrer"><code>virtualIbanEntries</code></a> in the <a href="https://api-reference.swan.io/queries/account/" target="_blank" rel="noopener noreferrer"><code>account</code></a> query. This makes it easy to surface only <code>Enabled</code> IBANs, even when an account has many virtual IBANs.</p>
<p>📋 You can now create a <a href="https://docs.swan.io/topics/capital-deposits/">capital deposit</a> case for companies whose legal name is longer than 100 characters. The limit on the <code>companyName</code>, <code>accountName</code>, and <code>name</code> fields has increased to 255 characters (previously 100), matching standard French registry formats. No changes needed on your end.</p>
<p>🔄 The conditions for an account to move from <code>Closing</code> to <code>Closed</code> status are changing. Before an account can close, all of the following must be true:</p>
<ul>
<li>The <code>Booked</code> balance is zero.</li>
<li>The last incoming <a href="https://docs.swan.io/topics/payments/credit-transfers/sepa/">SEPA Credit Transfer</a> was more than 30 days ago.</li>
<li>The last outgoing SEPA Credit Transfer was more than 30 days ago (previously 5 days).</li>
<li>No incoming or outgoing transaction is in <code>Upcoming</code> or <code>Pending</code> status, for any payment type (new).</li>
</ul>
<p>Because of these changes, accounts may stay in <code>Closing</code> status longer than before. If your integration tracks closure timing, adjust your expectations accordingly.</p>
<p>🔄 Incoming credit transfers to a <code>Closing</code> account are now accepted when the booked balance is negative. This helps settle outstanding debts before the account is <code>Closed</code>. Transfers to <code>Closing</code> accounts with a zero or positive balance are still returned to the sender, as before.</p>
<h2 class="anchor anchorWithStickyNavbar_LWe7" id="api-updates">API updates<a href="https://docs.swan.io/changelog/18-june-2026#api-updates" class="hash-link" aria-label="Direct link to API updates" title="Direct link to API updates">​</a></h2>
<h3 class="anchor anchorWithStickyNavbar_LWe7" id="upcoming-breaking-changes">Upcoming breaking changes<a href="https://docs.swan.io/changelog/18-june-2026#upcoming-breaking-changes" class="hash-link" aria-label="Direct link to Upcoming breaking changes" title="Direct link to Upcoming breaking changes">​</a></h3>
<p>⚠️ The <code>DormantAccount</code> closure reason is <strong>deprecated</strong>. <a href="https://api-reference.swan.io/enums/close-account-reason-type/" target="_blank" rel="noopener noreferrer"><code>Inactivity</code></a> replaces it, with the description: "Prolonged inactivity according to local regulatory definitions or internal policy." All accounts that previously used the <code>DormantAccount</code> closure reason are now using <code>Inactivity</code>.</p>
<p>If your integration filters, displays, or processes closure reasons by code, update it to handle the new code <code>Inactivity</code> and remove any reference to <code>DormantAccount</code>. See the <a href="https://docs.swan.io/topics/accounts/closure/#closure-reason-codes">updated closure reason codes</a> and <a href="https://docs.swan.io/topics/accounts/closure/#deprecated-reasons">deprecated reason codes</a> for the full mapping.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[7 May 2026]]></title>
            <link>https://docs.swan.io/changelog/7-may-2026</link>
            <guid>https://docs.swan.io/changelog/7-may-2026</guid>
            <pubDate>Thu, 07 May 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Improvements]]></description>
            <content:encoded><![CDATA[<h2 class="anchor anchorWithStickyNavbar_LWe7" id="improvements">Improvements<a href="https://docs.swan.io/changelog/7-may-2026#improvements" class="hash-link" aria-label="Direct link to Improvements" title="Direct link to Improvements">​</a></h2>
<p>🧭 Starting <strong>June 4</strong>, <a href="https://docs.swan.io/topics/payments/credit-transfers/sepa/guide-schedule-so/">Standing Orders</a> execute on their <code>lastExecutionDate</code> value. For example, a Standing Order with <code>lastExecutionDate</code> set to January 10 now runs on January 10 itself.</p>
<p>🛡️ Starting <strong>May 25</strong>, Single Device Authentication rolls out gradually to all OAuth2 flows. A 6-digit verification code replaces the clickable SMS link across all partner integrations, <a href="https://docs.swan.io/changelog/26-february-2026/#improvements">matching the approach already live on Swan's web banking</a>. This closes a remaining authentication fraud vector for partners using their own <code>client_id</code>.</p>
<p>For your end users signing in or signing up from desktop:</p>
<ul>
<li>They receive a 6-digit verification code by SMS, replacing the previous clickable link.</li>
<li>They enter the code on desktop to complete the flow.</li>
</ul>
<p>For <a href="https://docs.swan.io/topics/users/identifications/">identification</a>, two text messages are sent: one with a redirection link, and one to trigger identification on mobile.</p>
<p>No code changes are required, but please update your support documentation, guides, and flow screenshots accordingly.</p>
<h2 class="anchor anchorWithStickyNavbar_LWe7" id="api-updates">API updates<a href="https://docs.swan.io/changelog/7-may-2026#api-updates" class="hash-link" aria-label="Direct link to API updates" title="Direct link to API updates">​</a></h2>
<h3 class="anchor anchorWithStickyNavbar_LWe7" id="upcoming-breaking-changes">Upcoming breaking changes<a href="https://docs.swan.io/changelog/7-may-2026#upcoming-breaking-changes" class="hash-link" aria-label="Direct link to Upcoming breaking changes" title="Direct link to Upcoming breaking changes">​</a></h3>
<p>⚠️ On <strong>June 4</strong>, Swan renames <code>Card</code>-prefixed merchant types and mutations to <code>OnlineCard</code> equivalents for <a href="https://docs.swan.io/topics/merchants/online/cards/">accepting online card payments</a>. The deprecated names are removed on this date; update your queries and mutations before then.</p>
<p>This rename clarifies the distinction between online card acceptance and in-person card acceptance (terminals, Tap to Pay). It only affects partners accepting payments through <a href="https://docs.swan.io/topics/merchants/profiles/guide-request/">merchant profiles</a>. Card issuing is unchanged.</p>
<p><strong>Queries:</strong></p>
<ul>
<li><a href="https://api-reference.swan.io/objects/card-merchant-payment-method/" target="_blank" rel="noopener noreferrer"><code>CardMerchantPaymentMethod</code></a> → <a href="https://api-reference.swan.io/objects/online-card-merchant-payment-method/" target="_blank" rel="noopener noreferrer"><code>OnlineCardMerchantPaymentMethod</code></a>. Affects all queries that resolve <code>CardMerchantPaymentMethod</code> from <code>MerchantProfile.merchantPaymentMethods</code> or <a href="https://api-reference.swan.io/interfaces/merchant-payment-method/" target="_blank" rel="noopener noreferrer"><code>MerchantPaymentMethod</code></a>.</li>
<li><a href="https://api-reference.swan.io/objects/card-transaction/" target="_blank" rel="noopener noreferrer"><code>CardTransaction</code></a> → <a href="https://api-reference.swan.io/objects/online-card-transaction/" target="_blank" rel="noopener noreferrer"><code>OnlineCardTransaction</code></a>. The <a href="https://api-reference.swan.io/enums/payment-product/" target="_blank" rel="noopener noreferrer"><code>PaymentProduct</code></a> enum gains a new <code>OnlineCard</code> value.</li>
<li><a href="https://api-reference.swan.io/objects/card-merchant-payment/" target="_blank" rel="noopener noreferrer"><code>CardMerchantPayment</code></a> → <a href="https://api-reference.swan.io/objects/online-card-merchant-payment/" target="_blank" rel="noopener noreferrer"><code>OnlineCardMerchantPayment</code></a>.</li>
</ul>
<p><strong>Mutations and simulations:</strong></p>
<ul>
<li><a href="https://api-reference.swan.io/mutations/request-merchant-payment-methods/" target="_blank" rel="noopener noreferrer"><code>requestMerchantPaymentMethods</code></a> now requires <code>OnlineCard</code> instead of <code>Card</code>.</li>
<li><code>simulateMerchantPaymentMethodRequestOutcome</code> now requires the <code>OnlineCardMerchantPaymentMethod</code> typename.</li>
<li><code>simulateIncomingCardAuthorization</code> → <code>simulateIncomingOnlineCardAuthorization</code>.</li>
<li><code>simulateIncomingCardBooking</code> → <code>simulateIncomingOnlineCardBooking</code>.</li>
</ul>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[23 April 2026]]></title>
            <link>https://docs.swan.io/changelog/23-april-2026</link>
            <guid>https://docs.swan.io/changelog/23-april-2026</guid>
            <pubDate>Thu, 23 Apr 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[New features]]></description>
            <content:encoded><![CDATA[<h2 class="anchor anchorWithStickyNavbar_LWe7" id="new-features">New features<a href="https://docs.swan.io/changelog/23-april-2026#new-features" class="hash-link" aria-label="Direct link to New features" title="Direct link to New features">​</a></h2>
<p>📅 On <strong>May 21, 2026</strong>, public onboarding URLs will switch to the <a href="https://docs.swan.io/topics/onboarding/">current onboarding API</a> for all new onboardings. The previous public onboarding interface will be retired.</p>
<p>If you use public onboarding URLs without any prefilling, no action is needed. If you prefill onboarding fields through the API before redirecting to the onboarding URL, refer to the <a href="https://docs.swan.io/topics/onboarding/overview/guide-migrate/">migration guide</a> or reach out to your Swan contact to plan your migration.</p>
<h2 class="anchor anchorWithStickyNavbar_LWe7" id="improvements">Improvements<a href="https://docs.swan.io/changelog/23-april-2026#improvements" class="hash-link" aria-label="Direct link to Improvements" title="Direct link to Improvements">​</a></h2>
<p>✏️ <strong>Custom details for the <code>Other</code> purpose</strong>: when a supporting document with the purpose <code>Other</code> is requested, a new <code>purposeDetails</code> field on the <a href="https://api-reference.swan.io/objects/supporting-document-purpose/" target="_blank" rel="noopener noreferrer"><code>SupportingDocumentPurpose</code> object</a> specifies what document is needed (for example, "Company structure chart"). Query <code>purposeDetails</code> under <code>requiredSupportingDocumentPurposes</code> and display the description to your account holders to guide their upload. See the <a href="https://docs.swan.io/topics/accounts/documents/#document-purposes-and-types">supporting documents guide</a> for details.</p>
<h2 class="anchor anchorWithStickyNavbar_LWe7" id="api-updates">API updates<a href="https://docs.swan.io/changelog/23-april-2026#api-updates" class="hash-link" aria-label="Direct link to API updates" title="Direct link to API updates">​</a></h2>
<h3 class="anchor anchorWithStickyNavbar_LWe7" id="upcoming-breaking-changes">Upcoming breaking changes<a href="https://docs.swan.io/changelog/23-april-2026#upcoming-breaking-changes" class="hash-link" aria-label="Direct link to Upcoming breaking changes" title="Direct link to Upcoming breaking changes">​</a></h3>
<p>⏱️ On <strong>May 20, 2026</strong>, the <a href="https://docs.swan.io/topics/users/consent/guide-configure-notifications">consent notification endpoint</a> timeout will be reduced from 3 seconds to 2 seconds. This change applies to consent flows (sensitive operations), not OAuth2 flows such as login or authentication. The shorter timeout gives Swan enough time to fall back to text message within the 3.5-second 3-D Secure (3DS) window.</p>
<p>If your integration uses in-app consent notifications, make sure your endpoint responds within 2 seconds. Aim for 1.5 to 1.8 seconds to leave margin. If your response is slower, Swan falls back to text message. No action is required if you don't use in-app consent notifications.</p>
<p>⚠️ On <strong>September 30, 2026</strong>, the <a href="https://docs.swan.io/preview/new-onboarding/legacy-onboarding/">previous onboarding API</a> will be shut down and all previous endpoints will no longer be available. The <a href="https://docs.swan.io/topics/onboarding/">current onboarding API</a> has been generally available since March 2026. If you're still using the previous API, migrate before this date. Refer to the <a href="https://docs.swan.io/topics/onboarding/overview/guide-migrate/">migration guide</a> or reach out to your Swan contact to plan your transition.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[9 April 2026]]></title>
            <link>https://docs.swan.io/changelog/9-april-2026</link>
            <guid>https://docs.swan.io/changelog/9-april-2026</guid>
            <pubDate>Thu, 09 Apr 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[New features]]></description>
            <content:encoded><![CDATA[<h2 class="anchor anchorWithStickyNavbar_LWe7" id="new-features">New features<a href="https://docs.swan.io/changelog/9-april-2026#new-features" class="hash-link" aria-label="Direct link to New features" title="Direct link to New features">​</a></h2>
<p>🔔 <a href="https://docs.swan.io/topics/cards/physical/guide-activate#activation-reminder-notifications">Physical cards</a> that haven't been activated after their estimated delivery date now trigger automatic reminder emails to cardholders. Reminders are sent at configurable intervals until the card is activated. Configure this from your <strong>Dashboard &gt; Settings &gt; Notifications</strong>.</p>
<p>🧑‍🤝‍🧑 <a href="https://docs.swan.io/topics/accounts/memberships/admin-change">Changing account administrator</a> is now easier to handle for your customers. The dedicated request form determines which supporting documents are required based on company type and reason for change, so requesters upload the right documents on the first attempt. Share the guided form directly with your customers.</p>
<h2 class="anchor anchorWithStickyNavbar_LWe7" id="improvements">Improvements<a href="https://docs.swan.io/changelog/9-april-2026#improvements" class="hash-link" aria-label="Direct link to Improvements" title="Direct link to Improvements">​</a></h2>
<p>📫 Swan now requires email address verification when creating a new project in Sandbox. This limits impersonation risk and reinforces security across all projects.</p>
<p>🛡️ The Web Banking sign-up flow has been updated to strengthen protections against social engineering and fraud. Users now complete sign-up on desktop by entering a 6-digit SMS verification code and their personal information. They then switch to mobile to complete identification via a link sent to their device.</p>
<h2 class="anchor anchorWithStickyNavbar_LWe7" id="api-updates">API updates<a href="https://docs.swan.io/changelog/9-april-2026#api-updates" class="hash-link" aria-label="Direct link to API updates" title="Direct link to API updates">​</a></h2>
<h3 class="anchor anchorWithStickyNavbar_LWe7" id="upcoming-breaking-changes">Upcoming breaking changes<a href="https://docs.swan.io/changelog/9-april-2026#upcoming-breaking-changes" class="hash-link" aria-label="Direct link to Upcoming breaking changes" title="Direct link to Upcoming breaking changes">​</a></h3>
<p>📆 On <strong>April 30</strong>, the deprecated <code>InternalCreditTransfer</code> value will be removed from the <a href="https://api-reference.swan.io/enums/payment-product/" target="_blank" rel="noopener noreferrer"><code>PaymentProduct</code></a> enum. Remove any references to this value from your transaction queries and filtering before this date.</p>]]></content:encoded>
        </item>
    </channel>
</rss>