Add a new column Status Confirmed On in payments report

[ajeety4]

Product Description

Adds a new column Status Confirmed On in payments report. This column displays when the status of payment was last fetched from the provider.

Technical Summary

Ticket.

Feature Flag

MTN_MOBILE_WORKER_VERIFICATION

Safety Assurance

Safety story

A minor change for adding a new column. Changes behind an unused FF.

Automated test coverage

Test cases are updated.

QA Plan

None

Rollback instructions

• This PR can be reverted after deploy with no further considerations

Labels & Review

• Risk label is set correctly
• The set of people pinged as reviewers is appropriate for the level of risk of the change

[sentry]

Bug: The _handle_payment_status_retry() function omits the new PAYMENT_STATUS_CONFIRMED_ON field in the dictionary it returns during intermediate retries after a request error.
_{Severity: HIGH | Confidence: High}

🔍 Detailed Analysis

When a PaymentRequestError occurs during a payment status check, the _handle_payment_status_retry() function is called. If the retry count has not been exceeded, the function returns a dictionary that only includes the PAYMENT_STATUS_ATTEMPT_COUNT. This return value is missing the newly introduced PAYMENT_STATUS_CONFIRMED_ON field. As a result, when bulk_update_cases() processes this incomplete data, the case property for the confirmation timestamp is not updated. This leaves the timestamp stale, which contradicts the feature's goal of showing when the status was last fetched.

💡 Suggested Fix

Update _handle_payment_status_retry() to include the PAYMENT_STATUS_CONFIRMED_ON field with the current UTC timestamp in the dictionary it returns during intermediate retries. This will ensure consistency with other status update paths.

🤖 Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: corehq/apps/integration/payments/services.py#L394-L400

Potential issue: When a `PaymentRequestError` occurs during a payment status check, the
`_handle_payment_status_retry()` function is called. If the retry count has not been
exceeded, the function returns a dictionary that only includes the
`PAYMENT_STATUS_ATTEMPT_COUNT`. This return value is missing the newly introduced
`PAYMENT_STATUS_CONFIRMED_ON` field. As a result, when `bulk_update_cases()` processes
this incomplete data, the case property for the confirmation timestamp is not updated.
This leaves the timestamp stale, which contradicts the feature's goal of showing when
the status was last fetched.

_{Did we get this right? 👍 / 👎 to inform future reviews.
Reference ID: 8082363}

[ajeety4]

This is intentional, as the payment status is still pending confirmation from the provider due to a request error. Once the maximum retry count is exceeded, we update PAYMENT_STATUS_CONFIRMED_ON with the timestamp of the last retry.