On This Page

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.