Improvementsβ
π The birth postal code is now only required in France.
- Company onboarding: for ultimate beneficial owners and legal representatives, it's no longer required when the account country isn't France.
- User sign-up: it's only asked when the user was born in France. You no longer need to collect or prefill
birthPlacePostalCodefor users born outside France.
Birth date, city, and country are unchanged.
API updatesβ
Upcoming breaking changesβ
π From 12 November 2026, territory codes (for example, REU 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 (FRA). Existing records will be updated accordingly.
Onboardings where the account holder lives in an area where Swan doesn't offer accounts will be Invalid. Other country fields, like card delivery addresses, aren't affected. For more details, refer to the individual and company onboarding fields.
π£ From 12 November 2026, onboardings will apply new birth date rules for legal representatives, account admins, and ultimate beneficial owners.
- Account admins of company and individual accounts must be 18 or older. This also applies to verification renewals and account admin changes.
- Legal representatives (
LegalRepresentativeorLegalRepresentativeAndUltimateBeneficialOwner) must be 18 or older. A legal representative under 18 will be rejected. There's no maximum age. - Ultimate beneficial owners (
UltimateBeneficialOwner) can be any age, including minors. This also applies to verification renewals.
A birth date in the future is still rejected. Account members aren't affected.
π At the end of November 2026, funding limits will be removed. They belong to a product Swan no longer offers. The following are deprecated accordingly:
- Mutation:
addFundingLimitSettingsChangeRequest. - Queries:
fundingLimitSettingsChangeRequests,AccountHolder.fundingLimitSettings, andAccountHolder.fundingLimitSettingsChangeRequests. - Simulation:
updateFundingLimitSettingsChangeRequest.
π From 12 November 2026, the Account Information Service (AIS) will replace the Payment ID with the Origin Transaction ID. In AIS transaction responses, the extra.additional_information field will return the Origin Transaction ID (originTransactionId) instead of the Payment ID (paymentId). 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 Partner support request form. See the AIS field mapping.