Skip to main content

23 April 2026

ยท 2 min read

New featuresโ€‹

๐Ÿ“… On May 21, 2026, public onboarding URLs will switch to Onboarding v2 for all new onboardings, and the v1 public onboarding interface will be retired. The new experience delivers a cleaner onboarding flow with improved data collection for risk assessment and compliance. If you use public onboarding URLs without any prefilling, no action is needed. If you prefill onboarding fields via the API before redirecting users, refer to the migration guide or reach out to your Partner Integration Manager to plan your migration.

Improvementsโ€‹

โœ๏ธ Custom details for the Other purpose: when a supporting document with the purpose Other is requested, a new purposeDetails field on the SupportingDocumentPurpose object specifies what document is needed (for example, "Company structure chart"). Query purposeDetails under requiredSupportingDocumentPurposes and display the description to your account holders to guide their upload. See the supporting documents guide for details.

API updatesโ€‹

Upcoming breaking changesโ€‹

โฑ๏ธ Starting May 20, 2026, Swan is reducing the Consent Notification endpoint timeout 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. If your integration uses in-app consent notifications, make sure your endpoint responds within 2 seconds, ideally with some margin (around 1.5 to 1.8 seconds). If your response is slower, Swan falls back to text message. No action is required if you don't use in-app consent notifications.

โš ๏ธ Starting September 30, 2026, Onboarding API v1 will be shut down and all v1 endpoints will no longer be available. Onboarding API v2 has been generally available since March 2026, delivering improved data validation, expanded country coverage, and better support for risk assessment and compliance. If you're still using v1, migrate before this date. Refer to the migration guide or reach out to your Partner Integration Manager to plan your transition.