Skip to content

fix: add a hot fix for blocked routing numbers #299

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ash-wright123 merged 1 commit into from
Mar 4, 2026
Merged

fix: add a hot fix for blocked routing numbers #299

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/views/microdeposits/RoutingNumber.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,7 @@ export const RoutingNumber = (props) => {
})

// If reason is IAV_PREFERRED, load institutions to prepare for user choice.
if (resp.blocked_routing_number.reason_name === BLOCKED_REASONS.IAV_PREFERRED) {
if (resp.blocked_routing_number.reason === BLOCKED_REASONS.IAV_PREFERRED) {
Copy link
Collaborator

@wesrisenmay-mx wesrisenmay-mx Mar 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we have plans to fix the tests for this?

Copy link
Collaborator

@wesrisenmay-mx wesrisenmay-mx Mar 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also do we have plans to write an e2e test that would have caught the bug that customers found?

const loadedInstitutions$ = defer(() =>
api.loadInstitutions({
routing_number: values.routingNumber,
Expand Down
Loading