Configuring the Native Gateway
- Introduction
- Address Verification Service (AVS)
- Card ID Verification (CVV or CVV2)
- Fraud Screening
- Validation Settings
- Descriptor Display
1. Introduction
Our support team will take care of most aspects of gateway configuration for you. As usual, if you have questions about any of this stuff, please contact us.
2. Address Verification Service (AVS)
By default, AVS is off. You may choose to enable AVS checks and reject transactions for a variety of reasons. If you have questions about that, just ask.
When AVS is enabled, we only check AVS for the initial transaction after a credit card is added or updated. This avoids declined payments if the cardholder address changes mid-subscription. If the billing address was checked and passed once, it doesn't need to be checked again. This represents an advantage of using the native gateway over other services.
3. Card ID Verification (CVV or CVV2)
By default, we do not reject (decline) transactions due to a CVV mismatch. You may choose to enable CVV checks.
If you have questions about CVV checking and requiring CVV, just ask.
4. Fraud Screening
By default, fraud screening is disabled. You may choose to enable fraud screening features for an additional fee.
When fraud screening is enabled and a transaction is denied by the fraud checks, the Cheddar API will return the 422 response code and 6006 auxCode with a message of "The transaction was declined - contact support".
5. Validation Settings
It is highly recommended to enable the credit card validation feature for both new subscription and card changes. Using validation means that the credit card will be validated with a real authorization, a real-world end to end test of the credit card. This is the best way to ensure that the credit card is legitimate and in good standing. Failing to enable this feature makes it possible for a customer to inadvertently enter invalid credit card details resulting in a failure of their next payment later on. Validation provides for the ability for you to give immediate feedback to the customer in the event that the details they've entered are incorrect. That happens quite often.
Additionally, a validation authorization is required to take advantage of fraud checks, AVS checks, or CVV checks.
If your processing platform supports it, the native gateway will use a 0.00 "validate" transaction for validation instead of the traditional small auth/void.
6. Descriptor Display
You may optionally set a value for the Descriptor Display to match the descriptor set by your merchant account acquirer. This value is used on Cheddar's Hosted Pages to indicate to the customer what they should expect to see on their bank statement. It's best to make sure the descriptor is recognizable to your customers to lower the risk of your customers mistaking a charge on their card as fraudulent.