Real-World Example
Jane’s account can move from New Offers to Pending Creditor Response, then to Final Step to Close Deal, then to Payment Plans, and eventually Paid Accounts. Developers should treat these movements as product rules, not just labels in a tab list.Visual Flow
How It Should Work
- It should keep status names, My Accounts tabs, and allowed actions aligned.
- It should update status only through flows that understand negotiation, payment, notice response, and cancellation rules.
- It should make every new status visible in docs, tests, and navigation if it changes the consumer experience.
- It should normalize old or internal status query values to the tab the consumer sees today.
How It Should Not Work
- It should not treat statuses as display-only text.
- It should not add a new status without deciding which tab owns it.
- It should not allow actions from a previous status after the account has moved forward or closed.
Status Ownership Edge Cases
Returned notice responses are not normal declined negotiations. They belong in Notice Responses, can show returned-by-YN or returned-by-sender copy, and must stay out of the Declined / Closed Negotiations tab.
Developer Notes
- This page is for developers changing consumer account movement.
- When a status changes, review MyAccount, payment flows, notice response flows, communications, and background jobs together.
Related App Areas
app/Enums/ConsumerStatus.phpapp/Livewire/Consumer/MyAccount.phpapp/Livewire/Consumer/Traits/MyAccounts/Conditions.phpapp/Livewire/Consumer/Traits/MyAccounts/Offers.php