This article aims to highlight some of the behavioral and UI differences you may notice after transitioning from the legacy NetSuite integration to our managed NetSuite plug-in.

Below are some of the common differences you may see after switching.

• By default our managed integration will cancel transactions in NetSuite when a request receives a declined response. You can override this behavior by utilizing the Hold Transaction Reason Codes field in the payment processing profile. Please refer to the user guide for more information on using the Hold Transaction Reason Codes field.
  • The Managed NetSuite Plug-In is Not Holding Orders with a 233 Reason Code

• The legacy NetSuite integration would send a dummy email by default when there wasn't one present on the customer record in NetSuite. Our managed plugin can perform this same behavior, however you will need to enable the Use Dummy Billing Email Address checkbox in the payment processing profile.

• For recurring billing transactions in NetSuite, the legacy NetSuite integration would automatically send a card expiration date of 12/2099 for stored cards in NetSuite whose expiration date had already lapsed. Our managed integration will use the actual expiration date stored with the card in NetSuite. So if the card expiration date has expired, our integration will send the actual expired expiration date as that is what is stored with the card in NetSuite. Please see the article below for more information.
  • Recurring Orders Are Failing Due to an Expired Card After Switching to the Managed NetSuite Plug-In

• Our Managed plugin pulls the address data for transactions differently than the legacy NetSuite integration. Please see the articles below for more information.
  • Where is billing and shipping address data sourced from using the Cybersouce NetSuite plug-in?
  • Transactions Are Failing Due to Missing or Incorrect Billing Address Info Using the Managed Netsuite Plug-in

• The processing profile that is used for our managed integration is completely separate from the processing profile used with the legacy integration. Certain fields that were used in the legacy profile are not used in our integration's processing profile. Additionally, our integration's processing profile will have additional fields and sections that may not have appeared in the legacy processing profile. To process transactions with our Managed integration, you will need to create a new processing profile. For more information on the fields that appear in our integration's processing profile, please refer to the bundle user guide.

• Our Managed integration utilizes REST and SOAP keys for the API connection method meanwhile the legacy integration utilized Simple Order keys for the API connection method. 
  • I’m Getting “Authentication failed” When Using the Managed NetSuite Plug-In

• Using our Managed plugin, the ability to ignore AVS/CSC results is not set at the transaction level. This functionality is only able to be set in the payment processing profile.

• Setting ‘Cancel Order’ for an AVS/CVN rule in the payment processing profile, will trigger an auto Auth Reversal/Void when transactions are accepted by Cybersource but encounter the specific rule trigger.
  • Orders Are Canceled in NetSuite Even Though the Sale Was Successful via the Managed NetSuite Plug-in
     

We recommend testing your workflows in the test environment prior to moving to the production environment. Depending on your workflows/processes, you may need to adjust some of your workflows/processes to take into account the behavioral differences.