Skip to main content

​
Real-World Example

Jane wants to confirm which payments cleared on a deactivated or completed account. Payment History should show her the payment records tied to that account without reopening negotiation actions.

​
Visual Flow

​
How It Should Work

  • It should show payment records for the selected consumer account.
  • It should make amount, date, and status understandable.
  • It should remain available where historical payment context is needed.

​
How It Should Not Work

  • It should not show payment records for another consumer or creditor account.
  • It should not make historical payment review look like an active payment setup page.
  • It should not hide failed or cancelled payment records when they explain account history.

​
Developer Notes

  • The Payment History screen is available for deactivated accounts. Completed accounts use the completed payment summary instead.
  • Load the screen with GET /accounts/{consumer}/payments/history.
  • Download its agreement with GET /accounts/{consumer}/payments/agreement.
  • The history response is intentionally compact and does not include Schedule Plan actions or calendar metadata.
  • History records must match gateway/job outcomes.
  • routes/consumer/index.php
  • app/Livewire/Consumer/PaymentHistory.php
  • app/Jobs/Concerns/ProcessesScheduleTransactionPayments.php
Last modified on July 11, 2026