You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version Number: v9.4.94-0 Reproducible in staging?: Yes Reproducible in production?: Unable to validate in Prod - Provide reasoning. If this was caught during regression testing, add the test name, ID and link from BrowserStack:#101909 Email or phone of affected tester (no customers): N/A Issue reported by: Applause Internal Team Bug source: Pull Request QA execution Device used: Windows 10 App Component: Other
Action Performed:
Requires an account whose bank fails GIACT ownership verification (a bank that does not support Plaid, added manually).
Sign in as that account.
Go to Settings > Wallet > Add bank account and choose to enter bank details manually.
Enter the routing and account numbers, complete the personal details step and submit.
Verify the error shown is "Unable to verify bank account ownership. Please chat with Concierge for further assistance."
Result: Generic error "An unexpected error occurred…" is displayed
Expected Result:
After failing GIACT error shown is "Unable to verify bank account ownership. Please chat with Concierge for further assistance."
Actual Result:
After failing GIACT error shown is "Unable to verify bank account ownership."
Root Cause: The App shows the ownership error exactly as the server sends it. The App does not contain the text "Unable to verify bank account ownership" at all, so it cannot drop the "Please chat with Concierge…" sentence. The server response is missing that sentence.
This appears to be a backend/internal issue. A separate internal investigation is needed.
Recommended Fix: No App change. An internal engineer with backend access should confirm what the server returns for this GIACT failure and add the Concierge sentence there if it's wanted. Otherwise, update the expected result in the QA steps.
The full string with the Concierge sentence appears in the App only as a unit test fixture: tests/unit/BankAccountsTest.ts:80. The PR's manual test used a stubbed response, so the expected text was never checked against a real server response.
The issue contradicts itself. "Action Performed" says the generic error appeared. "Actual Result" says "Unable to verify bank account ownership." appeared. This analysis goes with "Actual Result". If the generic error does appear, please attach a screenshot.
Next Steps: Please escalate to an internal engineer with backend access. Reply with @MelvinBot <your feedback> to refine this analysis.
Activity
applause-bot commentedon Sep 27, 2026
While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/727e713df529e3db57744d4dc8840df2bf161bcc1b610025d3e181eee5fdb3ec
MelvinBot commentedon Sep 27, 2026
Issue Analysis
Root Cause: The App shows the ownership error exactly as the server sends it. The App does not contain the text "Unable to verify bank account ownership" at all, so it cannot drop the "Please chat with Concierge…" sentence. The server response is missing that sentence.
Recommended Fix: No App change. An internal engineer with backend access should confirm what the server returns for this GIACT failure and add the Concierge sentence there if it's wanted. Otherwise, update the expected result in the QA steps.
[Payment due @daledah] Surface the server's bank account ownership error instead of generic copy worked as intended: QA saw the server's error, not the generic "An unexpected error occurred…" fallback.
Investigation details
0, so the server error always wins: src/libs/actions/BankAccounts.ts:550-558.getLatestErrorMessagereturns the newest error string unchanged. It doesn't split or shorten it: src/libs/ErrorUtils.ts:86-103.DotIndicatorMessage, which renders the whole thing: src/components/SubStepForms/ConfirmationStep.tsx:94-99.Next Steps: Please escalate to an internal engineer with backend access. Reply with
@MelvinBot <your feedback>to refine this analysis.view run
melvin-bot commentedon Sep 27, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ahmedGaber93 (
External)[-]BA- Incomplete error message displayed for failed GIACT ownership verification[/-][+][$175] BA- Incomplete error message displayed for failed GIACT ownership verification[/+]melvin-bot commentedon Sep 27, 2026
Job added to Upwork: https://www.upwork.com/jobs/~022104265808290401528
NicolasBonet commentedon Sep 30, 2026
This is a backend change, so must be handled internally, as it's pretty straightforward and is causing issues in prod, I have moved along with it.
[-][$175] BA- Incomplete error message displayed for failed GIACT ownership verification[/-][+]BA- Incomplete error message displayed for failed GIACT ownership verification[/+]NicolasBonet commentedon Oct 1, 2026
Merged, so changing periodicity while we deploy.
NicolasBonet commentedon Oct 7, 2026
This should be fixed now.