- ID
- c6f1f169-7baa-4e1f-9b45-58bab04bd145
MMPY-69 Routing display confirmation
- source :: https://multimediallc.atlassian.net/browse/MMPY-69
- tags :: Falcon Nest Project Falcon Talon Project Falcon Talon Project Story
- epic :: MMPY-225 ACH Account Creator Interface
- sprint :: MM Sprint 28
- status :: Status - Complete
DONE Add ACH routing number checking to frontend
- ID
- 4ca78469-0fd4-46cc-d25a-a11c963b3757
- Note taken on
Got this basically working, but I need to check in with 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
- ID
- f2ca134a-3595-6261-e669-945b3a9f5e0a
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
- ID
- d51e6d0b-6b72-df58-56fe-be6c759d4708
DONE Address PR changes
- ID
- ad976742-9431-7f00-986f-4c6b1e1bc8c3
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