Reviewing Credit Card Requests Paige Freeman March 20, 2026 16:22 Updated The Review CC Requests page provides visibility into credit card processing activity associated with receipts in ThreeSixty Web Client. This page allows users to review credit card request and response information returned by the payment processor, including authorization and transaction details.By reviewing this information, users can verify credit card processing activity, investigate transaction issues, and confirm whether requests were approved by the payment processor.Accessing Review CC RequestsThe Review CC Requests page can be accessed in several ways within the web client. From the left navigation menu, select Accounting > Review CC Requests. From Accounting Central, select Review CC Requests. From the Manage Refunds page, select Review CC Requests from the contextual menu in the results grid. If the page is opened from the left navigation menu or from Accounting Central, the system displays the Find Requests search screen. The Find Requests search screen allows users to locate credit card request records associated with a specific receipt.To open the Review CC Requests screen for a receipt: Enter the appropriate search criteria on the Find Requests page. Review the results displayed in the grid. Select the hyperlinked Receipt No. to open the Review CC Requests page for that receipt. Review CC Requests When the Review CC Requests page opens for a selected receipt, summary information for the receipt appears at the top of the page.This section includes information such as: Card Holder Card No. Receipt Date Currency Amount Receipt No. Selecting the hyperlinked Receipt No. opens the Receipt Review page in a new browser tab.The bottom portion of the page contains the Credit Card Processing Review section. This section displays a grid listing credit card processing requests associated with the receipt.The grid includes the following information: Request Type Amount Date Approved status The Approved column indicates whether the request was approved by the payment processor. A checkmark indicates the request was approved, while an X indicates the request was not approved.Viewing Request DetailsTo review detailed information about a specific credit card request, select the hyperlinked Request Type in the Credit Card Processing Review grid.This opens a read-only detail screen that displays additional information about the request and response received from the credit card processor.The detail screen includes several sections of information, including: Authorization Request/Response Card Holder Information Card Changes Miscellaneous These sections provide detailed transaction information that can be used to review processor responses, verify authorization results, and investigate payment processing activity.AuthorizationThe Authorization section displays the following authorization/verification information: Request Answer ID – the system-generated ID number in the CCP_REQ_ANS table. Batch – the Batch ID of the batch used for the payment. Authorization – the number of the authorization. You can use this number to void a transaction online. Authorization Reference – the token used in the authorization. Original Authorization – the token used in the original authorization. Used for all subsequent transactions (settlements, refunds, void transactions). Deferred Expiration Date – the answer timestamp plus the number of days from the CCP_Auth_Hold_Period application parameter. Log Message – this varies based on the answer received to the request. A concatenation of several fields. Use the icon next to this field to view more text. Settlement Number – the settlement number. If the transaction was good, then the settlement number is the date timestamp. If the transaction was bad, then the settlement number is set to a negative date/timestamp. If the transaction was pre-settled, then the settlement number is set to “-1.” Voucher Number – a system-generated ID that identifies the Personify voucher. If some or all of a credit card payment is to be or has been refunded, then this field will store the voucher ID. A value of zero indicates no voucher exists for the credit card receipt. Original Receipt No. – displays the original receipt number. AVS Result – “Y” indicates the street address passed the authorization. “N” indicates the street address did not pass the authorization. ZIP Result – “Y” indicates the zip/postal code passed the authorization. “N” indicates the zip/postal code did not pass the authorization. CVV Result – “Y” indicates the CVV code passed the authorization. “N” indicates the CVV code did not pass the authorization. Request/ResponseThe Request/Response section provides information on the processor’s response to the credit card request: Request Answer Date – the date and time the payment handler answered the request. Error Code – the error code returned by the credit card processor (if applicable). Reject Reason – the reason the credit card was rejected (if applicable). This field is when the answer is received and it will be blank if the request was approved. Click the "..." button next to this field to view more text. Original Request Type – the request type of the original request from CyberSource or Vantiv. This is not used with PayPal. Original Request Token – the encrypted ORIGINAL_AUTH_REFERENCE from CyberSource or Vantiv. This is not used with PayPal. Click the "..." button next to this field to view more text. Request Token – the encrypted AUTH_REFERENCE from CyberSource or Vantiv. This is not used with PayPal. Click the "..." button next to this field to view more text. Response Code – the code for the type of response from the payment handler. Response Message – the response message from the payment handler. Click the "..." button next to this field to view more text. Processor Response Code – the code for the type of response from the processor. Processor Response Message – the response message from the processor. Click the "..." button next to this field to view more text. Card Holder InformationThe Card Holder Information section lists all of the card and card-holder information: Name on Card – the name of the credit card holder. Country Code – the country name for the billing address of the credit card holder. Address Line 1 – the first line of the credit card holder’s billing address. Processors use the numeric street number to execute AVS (address verification service) verification. Payor does not need to be in our system. City, State, Zip Code – the city, state, and zip code for the billing address of the credit card holder. Prepaid Card – identifies whether the card used for the payment is a prepaid card. Email Address – the email address of the credit card holder. Phone Number – the phone number of the credit card holder. Issuer Number – this is only used on European credit cards. Begin Date – this is only used on European credit cards. Expiration Date – the expiration date of the credit card. Cardholder Type – identifies whether the cardholder is a consumer or a commercial entity. Affluence Level – identifies whether the cardholder is considered high income (Mass Affluent) or high-income/high-spending (Affluent). The Cardholder Type, Prepaid Card, and Affluence Level fields are only populated if you are using Vantiv as your payment handler and you have enabled these features. This data is written to the CCP_Req_Ans table without being validated and the following system types and codes are provided for informational purposes only: AFFLUENT and CARDHOLDER_TYPE.Card ChangesThe Card Changes section displays if payment was made via credit card and it provides information on any changes made to a credit card: Original Card No. – the credit card number used in the transaction (CCP_REQ_ANS.CC_ACCT_NO). Original Expiration Date – the expiration date on the card used in the transaction (CCP_REQ_ANS.CC_EXP_DATE). Original Request Token – the original request transaction. Typically, this field is NULL, but if the transaction is a reference transaction, the system will generate a new token (CCP_REQ_ANS.ORIGINAL_REQUEST_TOKEN). Updated Request Token – the token for the transaction (CCP_REQ_ANS.REQUEST_TOKEN). New Card No. – if the organization is using the auto-updater service, and if the customer’s credit card number has changed, the auto-updater service will populate this field with the new credit card number (CCP_REQ_ANS.NEW_CC_ACCT_NO). New Expiration Date – if the organization is using the auto-updater service, and if the customer’s credit card expiration date has changed, the auto-updater service will populate this field with the new expiration date (CCP_REQ_ANS.NEW_CC_EXP_DATE). New Request Token – if the organization is using the auto-updater service, and if the token for the customer’s credit card has changed, the auto-updater service will populate this field with the new token (CCP_REQ_ANS.NEW_REQUEST_TOKEN). MiscellaneousThe Miscellanous section provides the following information regarding the credit card request: Comments – this is the same as the Request Answer ID, but PayPal refers to it as “Comments.” Requester – User ID of the logged in user that initiated the credit card transaction. Application – the Personify screen or batch process that generated the credit card activity. Merchant ID – the Merchant_ID used to process the credit card activity. Payment Handler – identifies the payment handler used for the credit card transaction. Billing Description – the custom credit card billing description defined for the product on the Custom Credit Card Billing Description Information screen in Product Maintenance. Phone Number – the custom credit card billing description phone number defined for the product on the Custom Credit Card Billing Description Information screen in Product Maintenance. City – the custom credit card billing description city defined for the product on the Custom Credit Card Billing Description Information screen in Product Maintenance. URL – the custom credit card billing description URL defined for the product on the Custom Credit Card Billing Description Information screen in Product Maintenance. Custom credit card billing descriptions are defined at the product level.