FAS - replacement chq new flow.
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
When a chq that was input into FAS has been returned NSF, the current process is to create a new RS and link it to the original.
[FAS - replacement chq flow.docx](https://api.zenhub.com/attachedFiles/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBNkpuQ1E9PSIsImV4cCI6bnVsbCwicHVyIjoiYmxvYl9pZCJ9fQ==--12addc14ac7a47d34966092b144b107e9151675c/FAS%20-%20replacement%20chq%20flow.docx)
Mock up link:
https://www.figma.com/design/rO4qLKPIsLMiDPU9gvrUqk/FAS---Fee-Accounting-System-Enhancement?node-id=9-2
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the attached “FAS - replacement chq flow.docx” and the linked Figma mockup; the issue names no source files, entry points, or tests. Done means implementing the approved NSF replacement-cheque flow, including creating a new RS and linking it to the original, with the resulting behavior matching those artifacts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- flask, javascript, postgres, python
- Domain
- full-stack, payments
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100