[BT-152] Migrate Settings - Security/Wallet/Subscription

[mjasikowski]

Description

Current State:

• 6 routes across Security, Wallet, and Subscription settings
• These routes use backTo parameter for return navigation

Implementation:

• Replace getRoute(..., backTo) with createDynamicRoute()
• Add source screens to entryScreens array
• Remove backTo parameter from route definitions
• Test forward/back navigation

Scope

Routes (6):

Route Constant	Path
SETTINGS_MERGE_ACCOUNTS_RESULT	settings/security/merge-accounts/:login/result/:result
SETTINGS_DELEGATE_ROLE	settings/security/delegate/:login/role/:role
SETTINGS_ADD_BANK_ACCOUNT	settings/wallet/add-bank-account
SETTINGS_ADD_BANK_ACCOUNT_VERIFY_ACCOUNT	settings/wallet/add-bank-account/verify-account
SETTINGS_SUBSCRIPTION	settings/subscription
SETTINGS_SUBSCRIPTION_DOWNGRADE_BLOCKED	settings/subscription/downgrade-blocked

Usages

SETTINGS_MERGE_ACCOUNTS_RESULT:

• src/pages/settings/Security/SecuritySettingsPage.tsx:158
• src/pages/settings/Security/MergeAccounts/AccountValidatePage.tsx:117,126,139
• src/pages/settings/Security/MergeAccounts/AccountDetailsPage.tsx:106,122

SETTINGS_DELEGATE_ROLE:

• src/pages/settings/Security/SecuritySettingsPage.tsx:233
• src/pages/settings/Security/AddDelegate/ConfirmDelegatePage.tsx:53,75
• src/pages/settings/Security/AddDelegate/AddDelegatePage.tsx:47

SETTINGS_ADD_BANK_ACCOUNT:

• src/libs/actions/BankAccounts.ts:126
• src/pages/workspace/invoices/WorkspaceInvoicesVerifyAccountPage.tsx:14

SETTINGS_ADD_BANK_ACCOUNT_VERIFY_ACCOUNT:

• Search for usages in bank account flow

SETTINGS_SUBSCRIPTION:

• src/pages/workspace/upgrade/GenericFeaturesView.tsx:32
• src/pages/workspace/WorkspaceOverviewPlanTypePage.tsx:121
• src/pages/settings/Subscription/FreeTrial.tsx:54
• src/pages/settings/Subscription/CardSection/BillingBanner/EarlyDiscountBanner.tsx:90
• src/pages/RestrictedAction/Workspace/WorkspaceOwnerRestrictedAction/index.native.tsx:26
• src/pages/workspace/upgrade/UpgradeIntro.tsx:75
• src/pages/workspace/upgrade/UpgradeConfirmation.tsx:31

SETTINGS_SUBSCRIPTION_DOWNGRADE_BLOCKED:

• src/pages/settings/Subscription/SubscriptionPlan/SubscriptionPlanCardActionButton.tsx:70

Files to modify:

• src/ROUTES.ts - Update route definitions
• src/libs/Navigation/types.ts - Remove backTo from params
• Components listed above

Migration Progress

• SETTINGS_MERGE_ACCOUNTS_RESULT
• SETTINGS_DELEGATE_ROLE
• SETTINGS_ADD_BANK_ACCOUNT
• SETTINGS_ADD_BANK_ACCOUNT_VERIFY_ACCOUNT
• SETTINGS_SUBSCRIPTION
• SETTINGS_SUBSCRIPTION_DOWNGRADE_BLOCKED

Issue Owner

Current Issue Owner: @huult

[huult]

Hi @mjasikowski @collectioneur I’m running into a case with SETTINGS_ADD_BANK_ACCOUNT where dynamic routing doesn’t seem to work correctly.

When we’re on settings/wallet/bank-account-purpose and append to create a dynamic route, the resulting path becomes settings/wallet/bank-account-purpose/add-bank-account, which doesn’t look correct.

Screen.Recording.2026-02-26.at.23.25.02.mov

If we instead update it to settings/wallet/add-bank-account, I’m not sure how we would navigate back to the correct page without a backTo parameter. Using goBack() feels risky, I tried it, but I’m still concerned about potential edge cases.

I checked the documentation but didn’t see this case mentioned. Could you please guide me on how we should handle this scenario?

[collectioneur]

Hi @huult, great catch! This is one of the few edge cases in the app that might not be fully covered by dynamic routes alone.
For this specific scenario, a hybrid approach would likely work best. Here is how we could approach it:

• For instances where add-bank-account can function as a dynamic suffix, we can implement it as a dynamic route.
• For scenarios where that isn't quite feasible, we could create static routes tailored to each flow, explicitly defining the forward and back navigation paths 😄

[huult]

@collectioneur Okay, I’ll try that approach and create a route like settings/wallet/add-bank-account-from-purpose.

[huult]

@collectioneur I saw that you opened a PR for this ticket. Just to confirm, will you be handling it? If so, I’ll work on another ticket.