Oracle NetSuite

Cybersource services can be integrated with
Oracle NetSuite
 to simplify your payment management platform. This section describes the payment methods and services that the Cybersource SuiteApp for
Oracle NetSuite
 bundle provides.

Payment Acceptance Services

The bundle supports payment acceptance services that the customer initiates (authorization and sale), and order management services that the merchant handles for credit and debit cards (capture, credit, authorization reversal).
The bundle includes these credit and debit card services:
  • Authentication
  • Authorization only
  • Authorization reversal
  • Capture
  • Credit
  • eCheck
  • Refund
  • Sale (authorization and capture)
  • Tokenization (
    TMS
     and network tokenization)
For the Cybersource Automatic Clearing House (ACH) service, the bundle supports payment acceptance services that the customer initiates (authorization and sale), and order management services the merchant handles(refund). The bundle also supports the tokenization service for ACH.

Order Management Services

The bundle supports order management services for Apple Pay, Google Pay, PayPal, and
Click to Pay
. Order management services support these operations for payment methods Apple Pay, Google Pay, PayPal, and
Click to Pay
:
  • Authorization reversal
  • Capture
  • Credit
  • Sale (supported for
    Click to Pay
     and for PayPal as a workaround for multi-capture functionality)
You must import authorizations that are processed outside of
Oracle NetSuite
 to see details of those authorizations using live integrations or CSV imports. For
Click to Pay
, the PNRef number field of the sales order should hold the details of the authorization ID and Visa order ID in the format of
AuthorizationID_VisaOrderID
. For PayPal, the PNRef number field of the sales order should hold the details of the authorization ID and order ID in the format of
AuthorizationID_OrderID
.

Reporting Services

You can import these reports from Cybersource into
Oracle NetSuite
:
  • Transaction Request Report
  • Payment Batch Detail Report
  • Conversion Detail Report

Invoicing Services

These invoicing actions can be generated in
Oracle NetSuite
 and imported from Cybersource:
  • Creating a draft invoice
  • Create an invoice without sending it
  • Create and sending an invoice immediately

Processor Support

The Cybersource SuiteApp for the
Oracle NetSuite
 bundle supports all processors available through Cybersource. Additional features are available for these processors:
  • Chase Paymentech Solutions
    : Level II and Level III supported for all card brands.
  • FDC Nashville Global
    : Level II and Level III supported for all card brands.
  • Global Payments: Level III supported for all card brands, and Level II supported only for American Express, Diners Club, Discover, JCB, and Maestro.
  • OmniPay Direct
    : Level III supported only for all card brands, and Level II supported for American Express, Diners Club, Discover, JCB, and Maestro.
  • TSYS Acquiring Solutions
    : Level II and Level III supported for all card brands.
  • Credit Mutuel-CIC
    : Level II and Level III supported for all card brands.
  • Elavon Americas
    : Level III supported for all card brands, and Level II supported only for American Express, Diners Club, Discover, JCB, and Maestro.
  • Barclays
    : Level III supported only for all card brands using REST, and Level II is not supported.

Release Notes

This section provides information about functionality, bug fixes, and enhancements for the Cybersource SuiteApp for
Oracle NetSuite
 integration.

January 2024

Cybersource Version 23.5.0 is compatible with
Oracle NetSuite
 2023.2 or earlier
  • Stripping of unsupported characters in
    billTo
     and
    shipTo
  • Web sec code support for ACH transactions
  • Line item support for basic transactions
  • Barclaycard processor L3 support
  • Deprecation of delete scenario for network tokens
  • 3-D Secure enhancements – device information
  • Decoupling of bundled Payer Authentication requests
  • Bug fix for ACH quantity field in REST
  • Bug fix for delay shipment with partial capture
  • Bug fix for PayPal multi-capture
  • Bug fix for delay shipment without multi-currency feature
  • Notice of SOAP and Secure Acceptance deprecation in August 2024
  • Partner Solution IDs update
  • Configuration Guide update

September 2023

Cybersource Version 23.4.0 is compatible with
Oracle NetSuite
 2023.2 or earlier
  • SCA enhancements
  • Source based PS ID
  • Map NS ID on reporting records
  • Payment facilitator support
  • Network tokenization
  • Bug fix for delay shipment handling with foreign currency
  • Bug fix for declined sale operations accepted in
    Oracle NetSuite
     when using SOAP
  • Company name support in payment acceptance and order management
  • Update to Cybersource authentication signature
  • Partner solution IDs update

August 2023

Cybersource Version 23.3.1 is compatible with
Oracle NetSuite
 2023.2 or earlier
  • BFN certification for
    Oracle NetSuite
     2023.2 release
  • Bug fix for Mastercard level III sale for TSYS
  • Bug fix for special character support for REST
  • Company name support for
    Pay by Link
  • Support for hold transaction reason codes multi-select field
  • Fix for subtotal not calculating on
    Pay by Link
  • Auto-cancel pending secure acceptance invoice payments
  • Fix for unexpected token < in JSON in the user event script
  • Fix for incorrect fields being passed for MOTO CIT

July 2023

Cybersource Version 23.3.0.1 is compatible with
Oracle NetSuite
 2023.1 or earlier
  • Patch fix for anti-clickjacking

June 2023

Cybersource Version 23.3.0 is compatible with
Oracle NetSuite
 2023.1 or earlier
  • Alternative payment methods using REST approach (PayPal)
  • Raw request/response rendering (the formatting on the raw request/response fields on the payment event records are removed to overcome the
    Oracle NetSuite
     field character limit from version 23.3.0 onwards.)
  • SuiteApp optimization
  • Invoicing roll-up feature (requires custom transaction feature to be enabled)
  • Invoicing alternate email field sourcing (requires custom transaction feature to be enabled)
  • HTML in saved search formula fix
  • Webstore invoice URL field support for invoice payments through secure acceptance
  • Bug fix for REST reason code mapping
  • Reinstate dummy billing email address
  • Transaction request report by date search
  • Payment batch detail report mapping to
    Oracle NetSuite
     transaction
  • Partner solution ID update
  • Configuration guide update

March 2023

Cybersource Version 23.2.0 is compatible with
Oracle NetSuite
 2023.1 or earlier
  • 3-D Secure 2.0 support
  • SA invoice payment reject scenario fix
  • SA bug fix for alphanumeric transaction IDs
  • log.error issue workaround
  • Customer name special character issue fix
  • Partner solution ID updated
  • Configuration guide updated

January 2023

Cybersource Version 23.1.0 is compatible with
Oracle NetSuite
 2022.2 or earlier
  • REST support for credit and debit card, credit and debit card token, ACH, ACH token, Visa checkout, Apple Pay, Google Pay
  • Transaction level downgrade feature
  • Invoice payment through webstore feature
  • $0 item filtering for sale transaction requests update
  • Secure acceptance request/response on same payment event update
  • Provided support for merchant initiated transaction for REST API
  • Started supporting abbreviation instead of full name for unit of measure
  • Partner solution ID updated
  • Configuration guide updated

September 2022

Cybersource Version 22.2.2 is compatible with
Oracle NetSuite
 2022.2 or earlier
  • AVS CVN international support
  • Secondary tax issue fixed for invoice
  • Secure acceptance tokenization transaction support
  • Hold transaction reason codes for secure acceptance
  • Void transaction error fixed
  • ACH default SEC code support
  • Reporting fields mapping updated
  • Field validation updated
  • Configuration guide updated

September 2021

Cybersource Version 22.2.1 is compatible with
Oracle NetSuite
 2022.2 or earlier
  • Added Level II and III support on transaction level
  • Strong customer authentication implementation for secure acceptance
  • Enhanced secure acceptance flow
  • getAddressee
     issue fixed
  • Secure acceptance cancel pending transaction time gap customization
  • Configuration guide updated
  • Dummy default billing email address functionality removed
Cybersource Version 22.2.0 is compatible with
Oracle NetSuite
 2022.1 or earlier
  • External MIT initial authorization support in
    Oracle NetSuite
  • Redirect message display for external checkout transaction
  • AVS/CVN response code display in
    Oracle NetSuite
     for sale transactions
  • Payment import optimization for
    Pay by Link
     invoicing feature
  • $0 shipping and handling issue fix for customer deposit
  • SuiteApp installed version display on SuiteApp configuration page
  • Payment method mapping simplification
  • Default merchant ID and invoice create action support for
    Pay by Link
     invoice feature
  • Default Cybersource invoice ID to
    Oracle NetSuite
     invoice number support
    Pay by Link
     invoice feature
  • ACH and ACH token (as general token) transaction support in
    Oracle NetSuite
  • Auth
     response issue fix
  • ShipTo
     addressee issue fix
  • Configuration guide updated

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.

Configuring SuiteApp

The SuiteApp integration supports the payment acceptance and order management services for credit and debit cards, and the order management service supports alternative payment methods: Apple Pay, Google Pay, PayPal, and
Click to Pay
.
The below sections provide details for configuring the payment acceptance and order management services. You must go through each section in order for detailed instructions on how to configure each feature.

Enabling the Plug-in

You must first enable the plug-in before you begin configuring the SuiteApp features.
  1. In your
    Oracle NetSuite
     account, click
    Customization
    .
  2. On the left panel, click
    Plugins
    , and click
    Manage Plug-ins
    .
  3. Ensure that the
    CYBERSOURCE FOR NETSUITE
     box is checked, and then click
    Save
    .

Completing the SuiteApp Configurations

You must complete the following configuration to use all of the features offered in the Cybersource
Oracle NetSuite
 integration. Each feature requires detailed actions, which are explained further in the linked sections below:

Mapping Payment Methods

Payment method mapping is automatically completed for credit and debit cards, ACH, and tokens and for order management and Secure Acceptance payment methods (such as, Google Pay, Apple Pay, Secure Acceptance credit and debit card) if the payment name matches the supported plug-in payment methods. If the payment method name does not match the payment name, follow these steps to map the payment methods:
  1. In your
    Oracle NetSuite
     account, on the top navigation, hover over
    Cybersource Integration
     >
    SuiteApp Configuration
    . Click
    SuiteApp Configuration
    .
  2. On the top navigation, hover over
    SuiteApp Configuration
    , >
    Step 2: Payment Method Mapping
     >
    Map Payment Methods
    .
  3. In the
    PAYMENT NAME
     row, choose the corresponding payment name from the drop-down list for that payment method.

Mapping Check for Card Types

Sometimes the same credit and debit card can be referred with different names in
Oracle NetSuite
 and Cybersource. For example, credit and debit card American Express can be referred to as Amex in
Oracle NetSuite
 and as American Express in Cybersource. To cross reference the credit and debit card names between two systems, mapping is required.
Follow these steps to map credit and debit card names between the Cybersource and
Oracle NetSuite
 applications with a unique number:
  1. Go to Customization, choose
    Lists
     >
    Records
     >
    Fields
     >
    Record Types
    .
  2. From the results, select the custom record
    Card Type Mapping
    , and click the
    List
     link.
  3. Verify that the mapping of the credit and debit card name between
    Oracle NetSuite
     and Cybersource is correct.
  4. If the mapping does not exist on the list page, click
    New Card Type Mapping
     to add a new mapping.
  5. Enter the
    Oracle NetSuite
     payment method name in
    Name
     field.
  6. Enter the card type value in the
    Card Type ID
     field (this is a unique numeric value).
  7. Enter the Cybersource payment method name in
    Card Type Name
     field.
  8. Uncheck the
    Inactive
     box.
  9. Click
    Save
    .
  10. Click the
    Edit
     link to update the credit and debit card name on any existing mappings.

Configuring Payment Processing Profiles

Configure a new payment processing profile to support credit and debit cards and other payment methods. Follow these steps to navigate to the Payment Processing Profile:
  1. In your
    Oracle NetSuite
     account, on the top navigation, hover over
    Cybersource Integration
     >
    SuiteApp Configuration
    . Click
    SuiteApp Configuration
    .
  2. On the top navigation, hover over
    Configuration
     >
    SuiteApp
     >
    Step 3: Payment Processing Profile
    . Click
    Create Payment Processing Profile
    .

Primary

From the Payment Processing Profile, follow these steps to complete the Primary section of the Payment Processing Profile:
  1. In the Primary section, in the
    WEB SITE
     box, choose the website for which this profile must be applied.
  2. In the
    Name
     field, enter a name for the payment processing profile (such as
    Payment Integration
    ).
  3. From the
    Subsidiary
     drop-down list, choose the subsidiary to which the profile should be mapped.
  4. From the
    Charge Currencies
     box, choose a currency.
  5. From the
    Settlement Currency
     drop-down list, choose which currency you want to accept.
  6. From the
    Settlement Bank Account
     drop-down list, choose the bank account for receiving payments.
  7. Check the
    Support Line Level Data
     box to support line data for the integration.
  8. Check the
    Test Mode
     box to integrate with the Payment Gateway Test account for processing the payment transactions. Clear the
    Test Mode
     box to run the integration with the Payment Gateway Production account.

Payment Acceptance and Order Management

Follow these steps to complete the Payment Acceptance and Order Management section of the Payment Processing Profile:
  1. In the Payment Acceptance and Order Management section, in the
    Merchant ID
     field, enter the Cybersource merchant ID.
  2. In the Payment Processing Profile, choose one of the level types:
    • Level II
       to pass the Level II data.
    • Level III
       to pass the Level III data.
    • Basic
       to pass the default data to the gateway.
  3. Choose the processor name. Click
    Blank
     to pass the request to gateway with the default structure, which is processor agnostic.

Payment Facilitator

From the Payment Facilitator drop-down list, choose the desired Payment Facilitator for the subsidiary corresponding to this Payment Processing Profile. This field can be left blank if Payment Facilitator is not used. For more information, see Enabling a Payment Facilitator.

Payer Authentication Configuration

Select the desired Strong Consumer Authentication (SCA) settings for certain scenarios. You can select one or more of these settings:
  • Check the
    Enforce Strong Consumer Authentication for All Transactions
     box to enable SCA for all transactions.
  • Check the
    Enforce Strong Consumer Authentication When Saving Cards
     box to enable SCA when the card is being saved for the first time.
  • Check the
    Proceed To Authorization when ECI Values are 00/07
     box to proceed with the authorization when the Electronic Commerce Indicator values are 00 or 07, which means the cardholder was unable to authenticate for various reasons.

REST Keys Configuration

You must enter the required REST information you obtained from the
Business Center
:
  1. In the
    REST Key ID
     field, enter the REST Key Identifier value from the
    Business Center
    .
  2. In the
    REST Secret Key
     field, enter the REST Secret Key value from the
    Business Center
    .
For steps on how to generate a key ID and a secret key, see Creating a Shared Secret Key Pair.

SOAP Key Configuration

Currently, you can enter REST or SOAP credentials to use the services, but SOAP and Secure Acceptance will be removed from SuiteApp in August 2024. If you are using SOAP or Secure Acceptance, consider moving to REST before August 2024.

Transaction Hold Reason

Select the reason codes when a payment must be put on hold (such as 101 - MISSING_FIELD, 102 - INVALID_DATA). For more information about reason codes, see Reason Codes for Oracle NetSuite.

Merchant Reference Number Customization

Set one of these options in the
For Capture
 field and one in the
For Refund
 field:
  • Sales Order #
     to set the merchant reference code to the sales order number
  • Cash Sale #
     to set the merchant reference code to the cash sale number
  • Cash Refund #
     to set the merchant reference code to the cash refund number

Fraud Management

Check the
Enable Fraud Management
 box to use the Decision Manager rules or the rules enforced by the Cybersource machine learning system. Clear this option to ignore the Cybersource Fraud Management Services.
In the Decision Manager Reject field, choose the
External Fraud Reject Hold
 to keep the payment on hold when the Cybersource Fraud Management services rejects the payment. Choose the
External Fraud Reject Hold and Cancel Order
 to cancel the order when the Cybersource Fraud Management services reject the payment.

AVS/CVN Rules

By default, only Address Verification Service (AVS) code N results in an AVS decline. Use the
Decline AVS Flags
 field to specify a list of AVS codes that should result in an AVS decline. You must include the value N in the list if you want to receive declines for AVS code N. These are the available codes are 1, 2, 3, 4, 5, A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U, V, W, X, Y, Z.
Choose the
Ignore AVS Response
 box to disable AVS functionality. If this box is checked, the plugin ignores the results from the Cybersource AVS, even when you use Decline AVS flags. The plugin processes the payment transaction when a customer's address information does not match the billing address of the credit or debit card account.
The
No AVS Match
,
AVS Service Not Available
, and the
Partial AVS Match
 settings indicate how SuiteApp handles AVS results returned during an authorization and sale operation. For each AVS setting, in their respective field, choose one of these actions:
  • Accept
  • Cancel Order
  • Verification Review

Credit Card Verification (CSC) Rules

Check the
Ignore CSC Response
 box to disable CSC functionality. If this box is checked, the plugin ignores the results from the Cybersource CVN service. The plugin processes the payment transaction even when the CSC code entered does not match the security code of the credit and debit card account.
These settings indicate how SuiteApp handles CVN results returned during an authorization and sale operation:
  • CSC Not Submitted
  • CSC Not Supported by Cardholder Bank
  • CSC Service Not Available
  • CSC Check Failed
  • No CSC Match
For each CSC setting (listed above), in their respective field, choose one of these actions:
  • Accept
  • Cancel Order
  • Verification Review

Override Options

Check the
Use Dummy Billing Email Address
 box to use a dummy email on requests with an empty email address.

Secure Acceptance
 Profile Configuration

Follow these steps to
Secure Acceptance
 as a payment method, if you are using it:
  1. In the
    Profile ID
     field, enter your
    Business Center
    Secure Acceptance
     profile ID.
  2. In the
    Access Key
     field, enter your
    Business Center
    Secure Acceptance
     access key.
  3. In the
    Key Secret
     field, enter your
    Business Center
    Secure Acceptance
     key secret.
  4. In the Web Store URL field, enter the
    Web Store URL
     link. Make sure that you replace the relevant account ID on the following URL
    https://accountid.secure.
    Oracle NetSuite
    .com/app/site/backend/returnfromplacedorder.nl
    . You can find the account ID in
    Setup/Company/Company Information/Account ID
    . After logging in to
    Oracle NetSuite
    , the account ID is visible on the URL as well (such as:
    https://tstdrv2134322.secure.netsuite.com/app/site/backend/returnfromplacedorder.nl
    ).
  5. In the Web Store Invoice URL field, enter the
    Web Store Invoice URL
    . Make sure that you replace the relevant account ID on the following URL along with the website version.
    https://<accountid>.secure.
    Oracle NetSuite
    .com/c.<accountid>/<websiteversion>/my_account.ssp
    Examples:
    • For SuiteCommerce Advanced:
      https://123456.secure.
      Oracle NetSuite
      .com/c.123456/sca-src-2022-2-0/my_account.ssp
    • For SuiteCommerce:
      https://123456.secure.netsuite.com/c.123456/scs/my_account.ssp
    • For SiteBuilder:
      https://123456.secure.netsuite.com/c.123456/sbe-src-kilimanjaro/my_account.ssp
      . You can find the account ID in
      Setup/Company/Company Information/Account ID
      . When you login to
      Oracle NetSuite
      , the account ID will be visible on the URL as well. (for example,
      https://tstdrv2134322.secure.netsuite.com/app/site/backend/returnfromplacedorder.nl
      ).

Merchant Defined Data Mapping

In the
Merchant Defined Data Mapping
 fields, choose the Merchant Defined Data Mapping field if you want the field value from the transaction to sync to the
Business Center
. This service is not supported when Payer Authentication (3-D Secure) is enabled due to limitations.
Under the Decision Manager section, Payer Authentication (DMPA) is not supported as of now. You must disable the DMPA rules set in the
Business Center
.

Default Custom Messages and Developer ID

Enter the customer messages that you want displayed for each of these scenarios:
  • External Reject Message
    : Enter the custom message to be displayed for transactions that are rejected.
  • External Hold Message
    : Enter the custom message to be displayed for transactions that are kept on hold.
  • Developer ID
    : Enter the developer ID (for example, 20083856). This ID is populated by the solution partner or solution integrator who performs the implementation on your behalf.

ACH Configuration

Choose the
Default SEC Code
 for all ACH transactions through
Oracle NetSuite
. You can change the SEC (Standard Entry Class) Codes at the transaction level. These are the SEC codes you can choose:
  • PPD
    : Pre-arranged payment or deposit
  • CCD
    : Corporate credit or debit
  • TEL
    : Telephone initiated entries
Oracle NetSuite
 SuiteCommerce automatically sets the SEC code for transactions to WEB (internet initiated/mobile entry).

Webhook Configuration for Network Tokenization

If you want to enable creating a webhook subscription, check the
Webhook Subscription
 box. Then enter a custom name in the
Webhook Name
 box and a custom description in the
Webhook Description
 box.
For more information, see Enabling Network Tokenization.

Payment Information

In the
Supported Payment Methods
 field, select all of the payment methods that you require. In the
Gateway Request Types
 field, select all of the gateway request types that you require (authentication, authorizations, capture authorization, credits, refunds, sales, void authorizations).

Tokenization

Check the
Replace Payment Card by Token
 box to support tokenization (tokenization is supported through Strong Customer Authentication (SCA) and not
Oracle NetSuite
). Then, in the
Payment Card Token Payment Method
 field, select the payment method. For ACH, in the
General Token Payment Method
 field, select the payment card token payment method.

Configuring Reports

The Cybersource SuiteApp for
Oracle NetSuite
 bundle provides these reporting services, which you can import from Cybersource into
Oracle NetSuite
:
  • Transaction Request Report
  • Payment Batch Detail Report
  • Conversion Detail Report

Configuring Invoicing

The Cybersource invoicing feature enables you to create invoices and share them with your customers. You can manage invoices and import existing invoices within
Oracle NetSuite
.
If an invoice is created in
Oracle NetSuite
, Cybersource recommends you make all of the updates to that transaction on
Oracle NetSuite
 and have the feature update the corresponding invoice in
Business Center
. If an invoice is created in the
Business Center
 and imported into
Oracle NetSuite
, Cybersource recommends that all updates to that transaction be done on the
Business Center
 and have the feature update the corresponding invoice in
Oracle NetSuite
.

Enabling Payment Instrument Support

You must enable the Payment Instruments configuration to use these specific features:
  • Tokenization
  • Network Tokenization
  • ACH
  • Multi-Capture
  • Delay Shipment
  • Merchant Initiated Transactions (MIT Mandate)
  • Invoicing –
    Pay by Link
Follow these steps to enable Payment Instruments:
  1. Go to
    Setup
     >
    Company
    . Click
    Enable Features
    .
  2. Click the
    Transactions
     tab.
  3. Scroll down to the Payment Processing section, and check the
    Payment Instruments
     box.

Enabling a Payment Facilitator

A Payment Facilitator (PayFac) is registered by an acquirer to facilitate transactions on behalf of merchants. With the introduction of a PayFac, the merchant becomes a sub-merchant, and the PayFac becomes the main merchant.
If you are using the multi-subsidiary customer feature in
Oracle NetSuite
, ensure that there is a Payment Processing Profile for each transacting subsidiary to enable payment processing for transactions pertaining to those subsidiaries.
The PayFac feature in the SuiteApp is supported only using REST keys. To support PayFac processing, additional configuration is required in order to enter the sub-merchant information.
Follow these steps to configure the PayFac feature:
  1. On the top navigation, hover over
    Cybersource Integration
     >
    SuiteApp Integration
    . Click
    SuiteApp Integration
    .
  2. Hover over
    SuiteApp Configuration
     >
    Step 3: Payment Processing Profile
    . Click
    View Payment Processing Profiles
    .
  3. Click
    Edit
     next to the profile that you need to enable the Payment Facilitator.
  4. Scroll down to the Payment Facilitator section.
  5. In the
    Payment Facilitator
     drop-down field, click
    New
    .
  6. Enter a name for the Payment Facilitator in the
    Name
     field.
  7. Open the
    Aggregator Information
     tab and complete all of the mandatory fields. These include:

    ADDITIONAL INFORMATION

    • Aggregator Name
    • Aggregator ID
    • Sub Merchant Name
    • Sub Merchant Country
    • Sub Merchant State
    • Sub Merchant City
    • Sub Merchant Postal Code
    • Sub Merchant Address1
    • Sub Merchant Email
    • Sub Merchant Phone Number
    • Sub Merchant Card Acceptor ID
    • Sub Merchant Region
  8. Open the
    Merchant Information
     tab and complete all of the mandatory fields. These include:

    ADDITIONAL INFORMATION

    • Merchant Descriptor Name
    • Merchant Country
    • Merchant State
    • Merchant City
    • Merchant Postal Code
    • Merchant Address1
    • Merchant Contact
    • Merchant Category Code
    • Merchant Tax ID
    • Merchant Sales Organization Code
  9. Save
     the Payment Facilitator record.

Enabling Network Tokenization

A network token is a network scheme generated token, that represents customer card information for secure transactions that reference an actual PAN.
Before you can enable a MID for Network Tokenization, you must provision it with a Token Requestor ID (TRID) for each card scheme. The Network Tokenization feature in the SuiteApp supports only REST keys.
Oracle NetSuite
 must subscribe to the necessary webhook notifications and ingest them for changes to the card. The system automatically creates the subscription when processing the authorization when the webhook subscription feature is enabled in the profile. If you perform an authorization as an external event, you must update the subscription ID in
Oracle NetSuite
 along with the import of the tokens to accept webhook notifications for these card changes.
Oracle NetSuite
 processes only these token updates:
  • Active: The system updates the
    Payment Card Token Inactive
     field based on this value.
  • Deleted: The system deletes the Payment Card Token record from
    Oracle NetSuite
    .

Configuring Network Tokenization

Follow these steps to configure the network tokenization feature:
  1. On the top navigation, hover over
    Cybersource Integration
     >
    SuiteApp Integration
    . Click
    SuiteApp Integration
    .
  2. Hover over
    Configuration
     >
    Step 3: Payment Processing Profile
    . Click
    View Payment Processing Profiles
    .
  3. Click
    Edit
     next to the profile that you need to enable network tokenization.
  4. Scroll down to the Webhook Configuration for Network Tokenization section, and check the
    Webhook Subscription
     box.
  5. Go to back to
    Cybersource Integration
    , and then go to
    SuiteApp Integration
    .
  6. Hover over
    Configuration
     >
    SuiteApp Integration
    . Click
    Copy Webhook - Notification URL
    . You must enter the
    Oracle NetSuite
     Suitelet URL in your
    Business Center
     webhook settings.
  7. Go to your
    Business Center
     account.
  8. In your
    Business Center
     account, go to
    Payment Configuration
    , and click
    Webhook Settings
    .
  9. Click
    Create
    .
  10. In the
    URL
     field, enter the
    Oracle NetSuite
     Suitelet URL to receive the webhook notifications.
  11. Turn on the
    Enable
     switch.
  12. From the list, select the same Shared Secret Key that you use for the subscription record in
    Oracle NetSuite
    .
  13. Click
    Save
    .

Configuring External Subscriptions

If you created subscriptions outside of
Oracle NetSuite
, then you must create a subscription record in
Oracle NetSuite
. Follow these steps to create a subscription record:
  1. Go back to
    Cybersource Integration
     >
    SuiteApp Integration
    . Click
    SuiteApp Integration
    .
  2. Go to
    Configuration
     >
    Step 3: Payment Processing Profile
    . Click
    View Payment Processing Profiles
    .
  3. Click
    Edit
     next to the profile you need to create a subscription record.
  4. Scroll down to the Webhook Configuration For Network Tokenization section, and click
    New
    .
  5. Enter these required fields:
    • Subscription ID
      : Enter the Webhook Subscription ID
    • PPP Record ID
      : Enter the internal ID of the payment processing profile record to use with this subscription.
      Keep the associated payment processing profile active, or update this field with the active payment processing profile record ID to accept webhook notifications. If the
      PPP Record ID
       field is empty, has invalid data, or is associated with an inactive profile or missing REST keys,
      Oracle NetSuite
       does not process the webhook notifications for token updates.
    • Webhook Security Key
      : Enter the Webhook Security Key
    • Merchant ID
      : Enter the Merchant ID
  6. Click
    Save
    .
  7. Import the payment card tokens into
    Oracle NetSuite
    .

Oracle NetSuite
 Merchant-Initiated Transactions

The MIT mandate ensures that merchants, acquirers, and issuers understand the transaction processing cycle. The MIT framework introduces a global standard for identifying transaction intent and whether a transaction is merchant initiated (without participation of cardholder).
The MIT framework facilitates exemptions from Strong Customer Authentication (SCA) using 3-D Secure depending on the transaction context (such as recurring transactions or Mail-Order/Telephone-Order (MOTO) transactions).

Benefits of Complying with the MIT Mandate

Merchants, acquirers, and issuers can link a series of related transactions.
  • MIT transactions—token-based transactions in particular, have better approval rates when the issuer can identify them.
  • MIT and token-based transactions can be processed without strong customer authentication (these transactions might otherwise fail, especially in regions complying with PSD2).
  • Transaction transparency, which results in higher authorization rates and improved cardholder experience.

Supported MIT Transaction Types

The MIT transaction types mentioned below are industry-specific transactions supported by the plugin:
  • Resubmission: A merchant resubmits transactions that request authorization but were declined due to insufficient funds while the goods or services were already delivered to the cardholder. A merchant in this situation can resubmit the request to recover outstanding debt from cardholders.
  • Reauthorization: A merchant initiates a reauthorization when the original order or service is not complete or fulfilled within the authorization validity limit set by the scheme. Common instances that require reauthorizations include delayed shipments, split shipments, extended stays, and extended rentals.
  • Delayed Charges: A delayed charge is associated with an agreement between you and the cardholder for services rendered. Merchants might use delayed charges after providing services such as lodging, travel, or auto rental.
  • No Show: A no-show transaction occurs when you and a cardholder have an agreement for a purchase, but the cardholder does not meet the terms of the agreement. No-show transactions are often used in hotels or restaurants where bookings are not honored despite the agreement entered into by the cardholder.
  • Unscheduled/Auto Top-up: This type of transaction uses a stored credential for a fixed or variable amount and does not occur on a scheduled or regularly occurring transaction date. The cardholder must provide consent for the merchant to initiate one or more future transactions.
If a MIT type is not selected, the transaction is flagged and processed as MOTO by default.
To avoid issues processing a MIT with a custom role, you must provide the payment instrument permission to the role. The
Payment Type
 field is supported only when the Payment Instrument feature is enabled.
Follow these steps to assign the role:
  1. Go to
    Setup
    .
  2. Click
    Users/Roles
    , and click
    Manage Roles
    .
  3. Click
    Customize
     on the role you want to assign the permission to.
  4. Scroll down, and under the Permissions tab, click the
    Lists
     subtab.
  5. Find the
    Payment Instrument
     row and set permission level to
    Full
    .
  6. Click
    Save
    .

Reference Information

This section contains reference information that is useful when integrating with
Oracle NetSuite
.