SuiteApp Installation and Update

You must have a
Business Center
 account to install the SuiteApp integration.
Go to the Business Center Registration website to create an account. Follow the email instructions that you received to activate your merchant account, and then log in to the Business Center to complete the registration process.
From your
Business Center
 account, you also need your merchant key ID and shared secret key to enable the integration with
Oracle NetSuite
. For steps on how to generate a shared secret key, see Creating a Shared Secret Key Pair. Store your merchant key ID and shared secret key for later use.

Installing SuiteApp

Follow these steps if you are installing Cybersource SuiteApp for
Oracle NetSuite
integration for the first time:
  1. In your
    Oracle NetSuite
    account, click
    Customization
    .
  2. On the left panel, click
    SuiteBundler
    , and then click
    Search & Install Bundles
    .
  3. In the
    KEYWORDS
    field, enter
    Cybersource for
    Oracle NetSuite
    .
  4. Click the bundle ID
    316818
    .
  5. Click
    Install
    .

Installing the SuiteApp Update

Follow these steps if you already installed the SuiteApp integration.
  1. In your
    Oracle NetSuite
    account, click
    Customization
    .
  2. On the left panel, click
    SuiteBundler
    , and then click
    Search & Install Bundles
    .
  3. In the
    KEYWORDS
    field, enter
    Cybersource for
    Oracle NetSuite
    .
  4. Click the bundle ID
    316818
    .
  5. From the list, ensure that the
    Replace Data
    option is selected for the following contents:

    ADDITIONAL INFORMATION

    • API response code/message
    • Processor Name
    • Sec Code
  6. Click
    Update Bundle
    to start the update.
  7. To verify progress, follow Steps 1-4 to go to the list of bundles.

Installing SuiteApp from Legacy Profile

Follow these steps to migrate from the
Oracle NetSuite
legacy profile to the SuiteApp profile:
  1. Install the SuiteApp integration. For more information, see Installing SuiteApp.
  2. Configure the new Payment Processing Profile and configure the required settings. For more information, see Configuring Payment Processing Profiles.
  3. After you configure the new processing profile following the steps from the linked section in the previous step, enable the new profile for the existing payment method and websites in the Payment Processing Profile form. Test the new profile integration in test mode.
  4. When the configuration is working properly, uncheck the
    Test mode
    box in the Payment Processing Profile form to use the integration in live mode.
  5. Search for any default Payment Processing Profile assigned on the customer master record. If necessary, remove the legacy profile and update it to the new SuiteApp profile. This ensures you have updated the reference to the new profile.
  6. Remove the reference to the legacy profile from the website setup, and assign the new SuiteApp profile to the same website.
  7. Clear the
    Authorization
    and
    Sale request type
    from the legacy profile to partially disable the legacy profile. This ensures that new authorizations or sales do not process with the legacy profile.
  8. Verify that the open sales orders and cash sales were authorized by the legacy profile. Configure a related transaction (cash, sale, or refund) with the legacy profile itself so that related payment events are shown on the transaction.

    ADDITIONAL INFORMATION

    If a sales order (authorization) is executed with a legacy Cybersource profile, and a cash sale is executed with a new SuiteApp profile, the capture happens successfully until the merchant ID and the gateway in the legacy profile and in the new SuiteApp profile match. However, during a Sales Order Payment event, the reference is shown only for the Authorization. It might not show the capture payment. The capture payment event is visible in the cash sale record only.
  9. When all sales orders authorized by the legacy profile are processed, uncheck the
    Capture
    box, and
    Inactivate
    the legacy profile to fully disable the legacy profile.