Failed Payments Report

The Failed Payments Report allows administrators to search and review a list of unsuccessful payment transactions within a specific date range. Its primary purpose is to help identify exactly why a user's transaction did not process by providing access to detailed transaction records and specific payment provider error codes. This article is intended for OPS-COM administrators.

Setup and Configuration

There is no specific system configuration required to access this report. Running the failed payments report is a standard administrative function available to users with the appropriate financial reporting and payment management permissions enabled on their account profile.

Using this Feature

Administrators can generate a list of unsuccessful transactions and drill down into the specific error details in just a few steps.

1. To access

   Hover the report go to theover Payments drop down menu and selectclick Search Failed Payments.
   
   

   

   
   
2. The Failed Payments Report screen will open.

   Enter athe specific date range you wish to report on andusing clickthe provided date fields.

3. Click the Search.
   
   

   button.

   
   
   
4. The screen

   Review willthe refresh with agenerated list of failed paymentpayments displayed for thatthe dateselected range.time Inperiod.

   our
example
5. we

   Click arethe looking atspecific OctoberConfirmation 1st,Code 2018link to open the full transaction record and view detailed failure information.

OctoberUnderstanding 15th,Provider 2018.Error Codes:
During thatWhile timesome periodpayment theregateways werereturn a detailed text explanation indicating exactly why a payment failed, other providers will simply supply a numerical error code (e.g., Response Code 481).

Key Information Displayed

• Failed 5Payment List: The initial search results display a high-level overview of the failed payments.attempts, The list showsincluding the payPay Id,ID, confirmation code, total amount of the payment, the date of the failed payment and the user name associated with the payment.
  
  

  

  
  
  
• To drill down further click on the Confirmation Code button to access the transaction record.
  
  

  

  
  
  
• The transaction record screen will open where you can see details about the failed transaction.
  
  

  

  
  
  
• Some payment providers will return detailed information with an explanation as to why the payment failed, whileand otherthe providersassociated willuser's simplyname.
  supply
an
• error

  Transaction code.
  InRecord thisDetails: caseDrilling notedown that there isinto a specific confirmation code reveals the full transaction record. This includes any detailed information or response codes returned directly by your third-party payment provider.

---

Best Practices and Considerations

• Investigating Codes: Perform a quick web search for the specific credit card response code if your gateway only provides a number. For example, searching for "Credit card response code of481" 481will indicatedquickly inreveal the information.
  
  

  

  
  A 481 code indicatesthat there is an error in the information provided.provided Usuallyby the user, usually an incorrect expiration date or an incorrect billing address.
  The
  definition
for
• these

  User codesSupport: areUse easilythe information found in athe webtransaction search.record Into thisproactively caseassist ausers searchwho forcall Creditin cardregarding payment issues, guiding them to double-check specific fields (like their postal code or CVV) based on the gateway's response code 481 provided the explanation.
  
  code.