Cybersource Merchant Parameters Paige Freeman January 25, 2024 15:05 Updated You must have access to the Settings.ApplicationSettings security application to access this page. Credit card processors (i.e., payment handlers) have system type and code records, as well as subcode records, to store the value of parameters needed by the payment handler. The values defined for App_Subcode PAYMENT_HANDLER records default into merchant parameters of the same name as the App_Subcode.SUBCODE record on the Merchant Setup screen. Merchant-level parameters are first created in the App_Subcode table so that, when a new merchant is created, the parameters related to credit card merchants are created in the App_Interface_Dtl table by copying the records from the App_Subcode table. The parameters in the table below are defined on the Merchant Setup page for the Cybersource payment handler: Parameter Description ACTIVE This parameter indicates the status of the Payment Handler and Merchant combination. Only active merchants can be used when processing credit cards, setting up Cash accounts, and running batch jobs. Valid options: Y (default) N CC_PROFILE_NON_INV_ORDS This parameter indicates whether or not to create a credit card profile for all receipts. Valid options: Y N (default) CCP_AUTH_HOLD_PERIOD The number of days a credit card authorization can be held for backorders. Merchants should get this information from their processor. By default, this is set to 8. CURRENCY The currency the Payment Handler operates in. By default, this is set to USD. FORCED REFUND This parameter controls whether CyberSource processes refunds to credit cards that were settled outside of Personify (such as a lockbox processor). If you set this to “Y,” then you must also verify the merchant transaction settings are as follows: Allow Non-referenced Credits = Yes Credits may exceed original transaction amount = Yes Valid options: Y N (default) IGNORE_AVS This parameter controls whether customers are required to provide the zip code of the credit card billing address when using a credit card as payment for a purchase. To comply with PA-DSS standards, this AVS code is not stored in the database. This parameter applies to both back office and web transactions. Valid options: Y (default) N IGNORE_CVV This parameter controls whether customers are required to provide a security number (CVV code) when using a credit card as payment for a purchase. To comply with PA-DSS standards, this CVV code is not stored in the database. Valid options: Y (default) N If the IGNORE_CVV parameter is set to "N" and you want to require the security number (CVV) in the back office, you MUST add the "NULL" value to the REJECT_CVV_RESULT_CODES parameter for your payment handler. If so, if the credit card security number is NOT entered in the back office, the following error message will display: Your credit card cannot be charged at this time. You may have left the CVV2 number blank. Please try again making sure you entered the correct CVV2 number. MERCHANT LOGON The user ID for logging on to the merchant website. MERCHANT PASSWORD All Cybersource issued P12 keys created after the implementation date will be secured with a password set by the user during key generation within the Cybersource Business Center. This password is encrypted when it is passed. PARTNER SOLUTION ID The assigned Partner ID. This defaults to 9AVJAB9V and should not be changed. PRE VALIDATE CREDIT CARD This parameter controls whether organizations pre-validate a credit card by generating a zero-dollar authorization before processing the credit card for full authorization. The pre-validation tests the CVV or AVS so that the customer has the opportunity to provide the correct information. When this parameter is set to “Y” and either “Ignore_AVS” = “N” or “Ignore_CVV” = “N”, then the system will generate a zero-dollar authorization to validate the account information before processing the credit card for full authorization. The system will make sure that the card passes AVS and CVV before any customer money is put on hold. Otherwise Personify will reject a transaction with an AVS error, but customer money would still be locked. Valid options: Y N (default)