Skip to main content
Welcome to the preview portal — This is an early release of the new Doc Hub experience, with more content coming soon.
Technology Partner

Configure Payment Processing Profile


Configure the Payment Processing Profile

To define how payments are processed through the SuiteApp, configure the payment processing profile.

Go to the Payment Processing Profile by choosing Configuration > SuiteApp > Step 3: Payment Processing Profile > Create Payment Processing Profile and complete these required settings.

Primary

Complete these fields:

  • In the Name field, enter the name of the payment processing profile.
  • In the Subsidiary field, specify which subsidiary within your NetSuite environment this profile applies to.
  • In the Charge Currencies field, specify the currency or currencies that you accept.
  • Test Mode: enable only to send transactions to the Platform test environment.

Payment Configuration

Complete these fields:

  • In the Merchant ID field, enter your Merchant ID.
  • In the Level Type field, set the default transaction level type by choosing Basic, Level II, or Level III. This setting can be overridden for individual payments when necessary.

Keys Configuration

Complete these fields:

  • In the Key ID field, enter the key ID from your REST shared secret key.
  • In the Secret Key field, enter the shared secret from your REST shared secret key.

Address Verification (AVS) Rules

Complete these fields:

  • In the No AVS Match field, choose how to handle orders with a no match (AVS) response.
  • In the AVS Service Not Available field, specify how to handle orders with an AVS unavailable response.
  • In the Partial AVS Match field, specify how to handle orders with a partial match AVS response.

Card Verification Rules

Complete these fields:

  • In the CSC Not Submitted field, specify how to handle orders with a Card Security Code (CSC) not submitted response.
  • In the CSC Service Not Available field, specify how to handle orders with a CSC unavailable response.
  • In the CSC Check Failed field, specify how to handle orders with a CSC check failed response.
  • In the CSC Not Supported by Cardholder Bank field, specify how to handle orders when the card issuer does not support CSC checks.
  • In the No CSC Match field, specify how to handle orders with a no match CSC response.

Merchant Reference Number Customization

Complete these fields:

  • In the For Capture field, specify which NetSuite ID to pass as the Merchant Reference Number to the Platform during a capture.
  • In the For Refund field, specify which NetSuite ID to pass as the Merchant Reference Number to the Platform during a refund.
  • In the For Customer Deposit field, specify which NetSuite ID to pass as the Merchant Reference Number to the Platform during a deposit.

Payment Information

Complete these fields:

  • In the Supported Payment Methods field, select the payment methods that can be processed with this payment processing profile.
  • In the Gateway Request Types field, select the payment actions to enable for the payment processing profile:
    • Authorization: sends an authorization request. When the authorization is approved, you must manually request a capture.
    • Sale: automatically captures the transaction when the authorization is approved.

Payment Processing Profile: Optional Settings

These settings are optional, but your merchant ID (MID) configuration or regional regulations might require some of them.

Primary

Complete this field:

  • Processor Name: enter a processor name only when you are processing Level II or Level III transactions.

Fraud Management

Complete these fields:

  • Enable Fraud Management: enable this field when you expect fraud screening responses from the Platform. Fraud Screening must still be configured for your MID in the .
  • Decision Manager Reject: specify how to handle transactions with a fraud screening Reject response.

Payment Authentication Configuration

Complete these fields:

  • DMPA Required: enable so that fraud management rules can determine if Payer Authentication 3-D Secure should be used with a transaction.
  • Payer Authentication Mode: choose one of these options:
    • Yes: all transactions are processed through 3-D Secure.
    • No: no transactions are processed through 3-D Secure.
    • Data Only: Visa and Mastercard transactions are processed through 3-D Secure, without challenges. No other card brands are processed with 3-D Secure.
  • Enforce Strong Consumer Authentication for All Transactions: when this field is enabled, all web store transactions are 3-D Secure challenged.
  • Enforce Strong Consumer Authentication when Saving Cards: when this field is enabled, any customer saving their card for future purchases is 3-D Secure challenged.

Transaction Hold Reason

Complete these fields:

  • Hold All Rejected Transactions: when this field is enabled, any transaction that is declined or rejected is marked as On Hold in NetSuite.
  • Hold Transaction Reason Codes: choose which decline or reject reasons to assign to orders marked On Hold in NetSuite. This setting is ignored when the Hold All Rejected Transactions option is enabled. For a list of reason codes, see Understanding Reason Codes.

Merchant Defined Data Mapping

Merchant Defined Data Mapping: select up to 20 NetSuite data elements to pass to the Platform in any transaction request. If these data elements are for fraud screening reasons, the same data elements must be set in the .

The data elements must be created in the Merchant Defined Data Mapping custom record before they can be configured in the Payment Processing Profile. See Map Merchant Defined Data Fields.

Address Verification (AVS) Rules

Complete these fields:

  • Ignore AVS response: when this setting is enabled, the AVS response is ignored.
  • Decline AVS flags: enter the values you want to treat as a decline, separated by commas. By default, N is treated as a decline. When Ignore AVS response is enabled, this setting is ignored. For a list of AVS codes, see Understanding Address Verification Service (AVS) Result Codes.

Card Verification (CSC) Rules

Complete this field:

  • Ignore CSC Response: when this setting is enabled, the CSC/CVV response is ignored.

Override Options

Complete these fields:

  • Use Dummy Billing Email Address: when this setting is enabled, a dummy email address is added to a payment transaction when a customer email address is not available.
  • Send Token As: if you are using Token Management Service (TMS), choose the TMS token type to use in transactions.
  • Network Tokens: if your MID is enabled for Network Tokens, enable this option to tell the SuiteApp to check for Token Life Cycle updates during Sales Order and Cash Sale creation.
  • Default PayPal Version: choose the version that is configured for your MID. To maintain backward compatibility, it can be overridden at transaction level.

Payment Facilitator

Link a Payment Facilitator record to the Payment Processing Profile. See Configure a Payment Facilitator for more details.

Default Custom Messages and Developer ID

Complete these fields:

  • External Reject Message: enter a custom message to display when a transaction is rejected.
  • External Hold Message: enter a custom message to display when a transaction is kept on hold.
  • Developer ID: enter a developer ID if one has been assigned to the developer or system integrator who supports your implementation.

Tokenization

Complete these fields:

  • Replace Payment Card by Token: check this to enable tokenization of payment cards.
  • Payment Card Token Payment Method: choose the token method used during payment method configuration. This is typically Payment Card Token if the automatic Payment Method creation was used.

Google Pay

Complete these fields to enable Google Pay in SuiteCommerce:

  • Google Pay Merchant ID: enter your Google Pay merchant ID.
  • Google Pay Merchant Name: enter the name to display to customers paying with Google Pay.

ACH/eCheck Configuration

In the ACH Configuration section, complete this field:

  • Default SEC Code: choose the default Standard Entry Class (SEC) code for ACH/eCheck transactions. This setting can be overridden for individual payments when required.

In the Tokenization section, complete these fields:

  • Replace Payment Card by Token: check this to enable tokenization of ACH/eCheck accounts.
  • General Token Payment Method: choose the ACH/eCheck token payment method used during payment method configuration. This is typically ACH Token if the automatic Payment Method creation was used.

New Payment Processing Profile View

The New Payment Processing Profile view is an alternative layout for managing payment processing profiles. It adds the Test Connection feature and the profile-level Enable Features tab.

To enable the new view, in a payment processing profile toggle Switch to New View. To switch back to the classic view, toggle Switch to Classic View.

Test Connection

The New View lets you confirm that the merchant ID and REST shared secret key entered in the payment processing profile are valid, by testing the connection.

A Test Connection button is located at the top and bottom of the Payment Processing Profile screen. Clicking the button validates that the merchant ID and the REST shared secret key are correct.

Next steps: After you finish configuring the payment processing profile, return to Create a Payment Processing Profile to continue the configuration.

Last published: November 18, 2026