Documentation Index
Fetch the complete documentation index at: https://docs.younegotiate.com/llms.txt
Use this file to discover all available pages before exploring further.
Real-World Example
Jane finishes a payment setup or one-time payment and lands on Payment Complete. The page should confirm the result, show the right next step, and avoid implying that a failed or pending payment succeeded.Visual Flow
How It Should Work
- It should confirm successful payment setup, completed payment, or scheduled plan creation accurately.
- It should route the consumer back to My Accounts, schedule details, or history as appropriate.
- It should keep the displayed result aligned with the actual payment state.
How It Should Not Work
- It should not display success when payment setup failed.
- It should not duplicate payments when a consumer refreshes the completion page.
- It should not leave the account in the wrong My Accounts tab after completion.
Developer Notes
- Completion pages should be idempotent and status-aware.
- Gateway response and internal schedule/payment state must be reconciled before showing final success language.
Related App Areas
app/Livewire/Consumer/PaymentComplete.phpapp/Services/Consumer/PaymentSettlementCompletionService.phpapp/Services/Consumer/PaymentSetupCompletionService.php