Org Web Adapter

Editing pages/mmpy_69_routing_display_confirmation.org

:PROPERTIES:
:ID:       c6f1f169-7baa-4e1f-9b45-58bab04bd145
:END:
#+title: MMPY-69 Routing display confirmation

- source :: https://multimediallc.atlassian.net/browse/MMPY-69
- tags :: [[id:7c3bbb4e-d079-42c4-992c-3e76210911f4][Falcon Nest Project]] [[id:9190ff85-385d-4286-91e2-270d974170e6][Falcon Talon Project]]  [[id:3d675d44-2acc-4de8-bd48-6816b4abae62][Falcon Talon Project Story]]
- epic ::  [[id:12dc2b1c-bf92-4c09-bfb9-9cb194a11dca][MMPY-225 ACH Account Creator Interface]]
- sprint ::  [[id:813661b9-7951-4c52-a53d-df5e4569827a][MM Sprint 28]]
- status ::   [[id:4d41d978-e56f-45c1-88d1-e2c76510972e][Status - Complete]]

* DONE Add ACH routing number checking to frontend :multimediallc:falcontalon:react:work:feature:validation:mmpy225:mmpy69:sprint28:
:PROPERTIES:
:ID:       4ca78469-0fd4-46cc-d25a-a11c963b3757
:END:

- Note taken on [2025-12-10 Wed 12:14]

Got this basically working, but I need to check in with  [[id:b9eaeadb-c0af-4dd0-9bb7-ee8f46f7b231][Nick Circone]] about how we add onBlur effects to fields, as currently it doesn't validate the routing number on keyup.
* DONE Add tests for routing number checking :multimediallc:falconnest:work:feature:validation:mmpy225:mmpy69:sprint28:
:PROPERTIES:
:ID:       f2ca134a-3595-6261-e669-945b3a9f5e0a
:END:

The issue now is that many of our validation paths are returning 500 errors. Need to surface 400s so the frontend can do it right.

* DONE Add tests for routing number checking :multimediallc:falcontalon:react:work:feature:validation:mmpy225:mmpy69:sprint28:
:PROPERTIES:
:ID:       d51e6d0b-6b72-df58-56fe-be6c759d4708
:END:
* DONE Address PR changes :multimediallc:falconnest:mmpy69:mmpy225:work:feature:validation:sprint29:
:PROPERTIES:
:ID:       ad976742-9431-7f00-986f-4c6b1e1bc8c3
:END:
* Background

When collecting Direct Deposit fields, we want to ensure that there aren’t errors.  Many services offer ACH routing number validation and we should incorporate that into our work.

* Requirements

** GIVEN

A payee has entered 9 digits into the routing field

** WHEN

there is a keyup on the last digit or lost focus on the field

** THEN

Based on the work done in MMPY-70: Make an API call to Falcon Nest to ensure that the routing number is valid and display the returned Bank Name & Address as layed out in MMPY-68

If there is an error, display “Bank not found with that routing number”

Do not allow submission or saving if the Routing number is not valid.

Remove BIC requirement

See comment:

https://multimediallc.atlassian.net/browse/MMPY-67?focusedCommentId=49495