Weekly UI/UX

Date: 2025-08-18 · Duration: 53.52000045776367 min Organizer: Nader Attendees: Mike, Nader, nathan.d.dutoit@gmail.com, Raymond

Summary

• Raymond successfully deployed recent fixes for validation issues and merchant creation UI glitches, enhancing the testing experience.
• Basic field validation for business name, website, and MCC code is fully functional, though timing issues with required field indicators need resolution.
• SSN field currently requires dashes; team agreed to implement auto-masking for improved user experience.
• Document upload validation is now mandatory, requiring at least one document before proceeding with the form.
• Critical ‘immutable’ backend errors are hindering save draft functionality, preventing data persistence effectively.
• Despite frontend validation being successful, backend submission is failing with recurring validation error messages, impacting user experience.
• Clarification on ‘submit as lead’ versus ‘submit application’ indicates leads go to Mike for review while full submissions head directly to processing.
• Cancellation functionality is essential for managing test applications and the merchant lifecycle, streamlining processes.
• Team is evaluating a shift from Pay Engine validation to a flattened data storage model to overcome current data saving limitations.
• Ticket 573 has been marked as complete, with all frontend acceptance criteria met despite existing backend integration problems.

Action Items

• Raymond Focus on completing validation implementation matching Google Sheets mapping in ticket 598 (41:42) Implement auto-masking for SSN field to improve user experience, limiting to 9 integers with automatic dash insertion (46:45) Add comments to Google Sheets for any missing field definitions encountered during implementation (47:15)

Mike Review and complete column H in Google Sheets with ‘always’ or ‘optional’ requirements for each field (44:02) Provide detailed thoughts on status management workflow and application lifecycle requirements (35:39)

Nader Discuss backend submission logic with Alexander including PUT endpoint error handling and force submission status management (33:19) Evaluate flattened data storage approach vs current Pay Engine validation model for better partial save support (51:28)