Monitor CPR

This section describes the best practices for monitoring the operations of CPR and impacted invoices.

CPR Payment Execution

For more information on verifying CPR execution, see Implement CPR section. Additionally, the Failure tab within your CPR instance provides insights into any processing failures encountered, preventing CPR from continuing execution.

Check CPR performance

To monitor the performance of your CPR strategies, use the CPR Dashboard. Navigate to Administration > System Health > Configurable Payment Retry Dashboard to view the performance of your CPR strategies. For more information, see the Configurable Payment Retry dashboard.

Gateway Errors and Payment Attempts

Use the gateway error responses to determine whether payment failures should be mapped differently or if tailored logic is required for frequently received responses.

For example,

• If there is a high number of failures related to expired payment methods, consider investigating the use of payment method updater service.

• If there is a high number of failures due to insufficient funds, consider altering the retry logic schedule to retry on more favorable days for your subscriber base or modify the communication sent to better align with retry attempts.

Reviewing Payment Attempt analysis

Examine the Payment Attempt analysis to evaluate the success of configured retry attempts.

For example,

If you are retrying payments 10 times and never see a recovery on the last or second-to-last attempt, consider eliminating these retries.

Reviewing Customer Group performance

Reviewing the performance of a customer group provides insights into how the retry logic impacts payment recovery. If changes are required, you can modify the existing group or create a new one to facilitate easier data evaluation.

For example,

Consider a customer group that has a high number of documents with a retry status of Complete-External . It indicates that something is happening to the document between retry attempts, resulting in zero balance and requiring no retry. This can occur due to one-off payments or document write-offs.