LEAR: what if NR expires after filing is filed but before it's paid?
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
Suppose a user completes a bootstrap filing with a NR and clicks File and Pay, and then for some reason payment fails. (Either they canceled CC payment or some other reason.) If the user doesn't come back to the entity dashboard and retry payment before the NR expires then they are blocked -- the entity dashboard will report a "NR expired" error and not load.
This is a similar scenario to starting a bootstrap filing with a NR, and not finishing it before the NR expires.
What should we do about it?
- ensure the user knows what will happen if they don't retry payment or finish their bootstrap filing
- have some way to clean up this blocked filing
- do we care what status the filing is?
- what should we show in the MBR?
- can OPS do anything to help the user?
This issue affects all registrations, incorporations, amalgamations and continuation-ins with a NR if the user files it and defers payment until after the NR expires.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.