Reviewing Payment Connector Logs

• If no payment detail record is found, either because the parameter that includes the id is missing, or the id is invalid, or the payment detail record was deleted in Salesforce, etc, a TargetX log record is created with the following message:

For CyberSource:
CYBERSOURCEPostResponseHandler: No payment detail found to update!
 
ALL OTHERS:
No payment detail record found, cannot process response.
Post Parameters:
<param>: <value>

• If a parameter was specified in the parameter mapping list, but the response does not include the parameter, a TargetX log record is created with the message:

Response Handler page parameters does not include a parameter named: <parameter>

• If a parameter response mapping references a field that not a valid field on the Payment Detail object, either because of a misspelling or otherwise, a TargetX log record is created with the message:

Response mapping references field '<fieldname> ', which was not found on the Payment Detail object.
<parameter>=<value>

• If the parameter response mapping references a field that is on the reserved field list, a TargetX log entry is created with the message:

Parameter mapped to reserved field: <fieldname>
<parameter>=<value>

• Paypal

  • If the HttpResponse body != VERIFIED, a TargetX Log is created with the response body and responseHandler url with parameters.​​​

• Transact Payments (Cashnet)

  • If Result != 0, a TargetX Log is created with the result, respmessage, and responseHandler url with parameters.

• Nelnet

  • If there is an MD5hash mismatch,  a TargetX Log is created with the responseHandler url with parameters.