AVS and CVV gateway provisioning for Spreedly

The Payment Service for Optimizely Configured Commerce and Optimizely Commerce Connect uses Spreedly. When provisioning a payment gateway through the Spreedly API, the ability to enable or disable the Address Verification System (AVS) and Card Verification Value (CVV) checks is not a universal feature. This functionality depends on the specific gateway's integration with Spreedly.

For gateways that do not support these controls, you must configure these controls directly within the gateway's own merchant portal or manage them on a per-transaction basis.

The following is a list of popular gateways and their capabilities for AVS and CVV control during provisioning.

Gateways with provisioning-time AVS and CVV control

These gateways let you define AVS or CVV behavior by passing specific fields in the body of your POST /gateways API call when you create or update a gateway.

• Braintree – Provides direct boolean flags to disable AVS and CVV checks.

  Parameter	Value	Description
  skip_avs	Boolean	Set to true to disable AVS checks for all transactions.
  skip_cvv	Boolean	Set to true to disable CVV checks for all transactions.

• CyberSource – Offers granular control over how it handles AVS and CVV mismatches.

  Parameter	Value	Description
  avs_decline_codes	String	A comma-separated list of AVS result codes (like N,U,I) that automatically cause a transaction to decline.
  cvv_decline_codes	String	A comma-separated list of CVV result codes (like N,I,P) that automatically cause a transaction to decline.
  avs_ignore_street	Boolean	Set to true to ignore the street address portion of the AVS check.
  avs_ignore_zip	Boolean	Set to true to ignore the ZIP code portion of the AVS check.

• PayPal Payflow Pro – Uses simple Boolean flags to enable or disable the verification checks.

  Parameter	Value	Description
  avs_enabled	Boolean	Set to false to disable AVS checks.
  cvv_enabled	Boolean	Set to false to disable CVV checks.

• Moneris – Lets you disable AVS and Card Validation Digits (CVD), which is their term for CVV.

  Parameter	Value	Description
  disable_avs	Boolean	Set to true to disable AVS checks.
  disable_cvd	Boolean	Set to true to disable CVD (CVV) checks.

• Authorize.Net – Provides controls for handling transactions with missing AVS data.

  Parameter	Value	Description
  allow_blank_avs_street	Boolean	Set to true to allow transactions, even if the billing street address is not provided.
  allow_blank_avs_zip	Boolean	Set to true to allow transactions, even if the billing ZIP code is not provided.

• iATS – Offers Boolean flags for AVS and CVV.

  Parameter	Value	Description
  avs_enabled	Boolean	Set to false to disable AVS checks.
  cvv_enabled	Boolean	Set to false to disable CVV checks.

Gateways without provisioning-time AVS/CVV control

Based on Spreedly's developer documentation, the following gateways do not offer specific API fields to configure AVS or CVV behavior during gateway provisioning. You must manage these settings within their external dashboards or control panels.

• Stripe – Managed under Stripe Dashboard > Radar rules.
• Adyen – Managed in the Adyen Customer Area risk profiles.
• Worldpay/Vantiv – Managed in the merchant portal.
• Checkout.com – Managed in the dashboard.
• NMI (Network Merchants, Inc.) – Managed in the control panel.
• Elavon
• Sage Pay (now Opayo)
• TSYS Acquiring Solutions
• First Data Payeezy (now Fiserv)
• Shopify
• Global Payments
• Litle & Co.

Recommendation

You should check Spreedly's documentation for the specific gateway you intend to use. If provisioning-time controls are not available, you should establish a process for configuring AVS and CVV rules directly in the gateway's merchant portal as part of your standard configuration procedure.