[Due for payment 2025-09-17] [$250] Wallet - The error Invalid IBAN still appears on the other bank country submission

[jponikarchuk]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: v9.1.97-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: #65081
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Device used: Windows 11 / Chrome, Android 13 / Xiaomi Poco F5, iOS 15.8.3 / iPhone 7 Plus
App Component: Other

Action Performed:

1. Login to https://staging.new.expensify.com/
2. Go to Settings > Wallet > Add bank account
3. Choose a country that has IBAN field to fill (e.g. France)
4. Fill the IBAN field with the correct format
5. Fill the bank and holder details with any data
6. Check the Term of service and click confirm
7. Verify the error validation Invalid IBAN will appear
8. Close the RHP and click Add bank account
9. Choose another country that doesn't have IBAN (e.g. Indonesia)
10. Fill all field with random data test
11. Verify that the error Invalid IBAN still appears on the Add bank account confirmation page

Expected Result:

The error Invalid IBAN should not appear on the other submission

Actual Result:

The error Invalid IBAN still appears on the other bank country submission

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021958161719972011917
• Upwork Job ID: 1958161719972011917
• Last Price Increase: 2025-08-20

Issue Owner

Current Issue Owner: @

Issue Owner

Current Issue Owner: @clarajones-expensify

[melvin-bot]

Triggered auto assignment to @clarajones-expensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

Triggered auto assignment to @carlosmiceli (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source