On This Page

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
    .