Key Differences Between Legacy NetSuite Integration and Managed NetSuite SuiteApp

Introduction

This article highlights some of the behavioral and UI differences you may notice after transitioning from the legacy NetSuite integration to the managed NetSuite plug-in (SuiteApp). Review these differences to understand changes in transaction handling, configuration, and data processing.

Common Differences

• Declined Transactions Behavior:
  By default, the managed integration cancels 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.
  See also: "The Managed NetSuite Plug-In is Not Holding Orders with a 233 Reason Code."
• Handling Missing Customer Emails:
  The legacy NetSuite integration would send a dummy email by default when there wasn't one present on the customer record in NetSuite. The managed plug-in can perform this same behavior; however, you must enable the Use Dummy Billing Email Address checkbox in the payment processing profile.
• Recurring Billing and Card Expiration Dates:
  For recurring billing transactions in NetSuite, the legacy integration would automatically send a card expiration date of 12/2099 for stored cards whose expiration date had already lapsed. The managed integration uses the actual expiration date stored with the card in NetSuite. If the card expiration date has expired, the integration will send the actual expired date.
  See also: "Recurring Orders Are Failing Due to an Expired Card After Switching to the Managed NetSuite Plug-In."
• Address Data Sourcing:
  The managed plug-in pulls address data for transactions differently than the legacy NetSuite integration.
  See also:
  • "Where is billing and shipping address data sourced from using the Cybersource NetSuite plug-in?"
  • "Transactions Are Failing Due to Missing or Incorrect Billing Address Info Using the Managed Netsuite Plug-in"
• Processing Profile Differences:
  The processing profile used for the managed integration is completely separate from the legacy integration. Certain fields from the legacy profile are not used, and the managed integration's profile includes additional fields and sections. To process transactions with the managed integration, you will need to create a new processing profile. For more information on the fields that appear in the managed profile, please refer to the bundle user guide.
• API Connection Method:
  The managed plug-in utilizes REST and SOAP keys for the API connection method, while the legacy integration used Simple Order keys.
  See also: "I’m Getting 'Authentication failed' When Using the Managed NetSuite Plug-In."
• AVS/CSC Results Handling:
  Using the managed plug-in, the ability to ignore AVS/CSC results is not set at the transaction level. This functionality is only set in the payment processing profile.
• Auth Reversal/Void Triggers:
  Setting ‘Cancel Order’ for an AVS/CVN rule in the payment processing profile will trigger an automatic authorization reversal or void when transactions are accepted by Cybersource but encounter the specific rule trigger.
  See also: "Orders Are Canceled in NetSuite Even Though the Sale Was Successful via the Managed NetSuite Plug-in."

Recommendations

• We recommend testing your workflows in the test environment before moving to production.
• Depending on your workflows/processes, you may need to adjust some of your workflows/processes to account for these behavioral differences.

Note: Always refer to the user guide and linked articles/support topics for further details on specific behaviors or troubleshooting steps.