Setting Up Payment Processing Profiles in NetSuite
Set up payment processing profile in NetSuite for each payment card gateway you use. You can set up multiple profiles in NetSuite based on your business needs. You must set up a payment card gateway profile for each settlement currency and merchant bank account your company uses.
NetSuite integrates with the following preferred gateway partners:
-
CyberSource
-
MerchantE
-
PayPal Payflow Pro (This processor requires an add-on module be enabled in your NetSuite account. For more information, contact your NetSuite account representative.)
NetSuite currently maintains SECPay as a legacy gateway partner only for existing payment card gateways.
NetSuite also integrates with additional regional gateway partners that provide payment card processing services in specific countries. See Regional Payment Gateways.
Before you set up a payment card processing profile in NetSuite, you must:
-
Establish a merchant account. See Establishing a Merchant Account.
-
Set up the merchant account with the gateway you will be using in NetSuite. See Setting Up a Merchant Account with a Payment Gateway.
To set up a payment card processing profile:
-
Go to Setup > Accounting > Payment Processing Profiles > New.
-
Click the Add Profile next to the gateway integration you want to set up.
The gateway integration must be installed in your account. Otherwise, Install shows instead of Add Profile.
For instructions for setting up a preferred gateway, see CyberSource and MerchantE.
For information about setting up a regional gateway, see Setting Up Regional Payment Gateways.
The new payment card processing profile page includes a section where you select the types of payment requests the gateway will process:
-
Authentications – process requests for cardholder authentication when required. The Payment Processing Plug-in must support 3D Secure 2 for the Authentication operation to be available.
Support for 3D Secure 1 ended on October 15, 2022. See End of Support for 3D Secure 1 for more information, including information about migrating your website technologies from 3D Secure 1 to 3D Secure 2.
-
Authorizations – process requests to place a hold on a credit line for a specified amount until fulfillment is complete.
Warning:When you use a payment processing profile that does not support authorization to process card payments on sales orders, make sure you follow the card acceptance guidelines of your payment card issuer.
If your business involves shipping goods to your customers, you must process the sales order with a payment processing profile that supports authorization. Funds must be deposited only when goods have been fulfilled.
Use a payment processing profile that does not support the authorization request on a sales order only when you provide an immediate delivery of goods or services.
-
Captures – process charges against authorizations after fulfillment.
-
Sales – process authorization and funds capture for immediate fulfillment of products or services.
-
Credits – process requests to distribute funds a cardholder without reference to a previous transaction.
-
Refunds – process requests for refunds that reference a previous transaction.
-
Voids – process requests for voiding authorizations. Only CyberSource and MerchantE support voiding authorizations.
In most cases, select all request types for a gateway to fully use the gateway processing functionality and provide smooth payment card processing for your website. All the gateway request types are enabled by default when you set up a new payment card gateway. For information about how to set these options when changing payment card gateways, see Transitioning to a New Gateway and Disabling the Old Gateway.
If you select the Sales request and leave the Authorizations request blank, the processing profile will perform a direct sale request. When you select this profile on a sales order, the funds are captured before fulfilling the order. The captured funds are associated with the order as a customer deposit.
Payer Authentication
Enable the Payer Authentication on a payment processing profile to redirect the shopper to a payer authentication site. On this site, shoppers enter or create passwords for their payment cards. Payer authentication protects you from chargebacks for unauthorized transactions by verifying that the cardholder makes the purchase. This also provides enhanced security for cardholders.
Allow Request ID to Meet Payment Card Field Requirements
On a Payment Processing Profile page, check the Allow Request ID to Meet Payment Card Field Requirements box to allow payment cards to be charged by referencing the original Request ID when the order is authorized outside of NetSuite.
These are orders passed to NetSuite using SOAP web services. This preference enables the payment card entered on the external order to be charged by referencing the request ID from the originating authorization rather than requiring card information to be present on the sales order in NetSuite.
Restricting Payment Processing Profiles by Customer Data
To prevent processing payments with incompatible payment processing profiles, you can show in the Payment Processing Profile field only those payment processing profiles that support all of the following requirements:
-
The selected payment method
-
Customer’s currency
-
Customer’s subsidiary (One World accounts only)
If you use One World intercompany accounts, this restriction prevents one subsidiary from using another subsidiary’s payment processing profiles.
To restrict payment processing profiles by customer data:
-
Go to Setup > Accounting > Preferences > Accounting Preferences.
-
Click the Items/Transactions subtab.
-
Under Payment Processing, check the Use Strict Rules for the Selection of Payment Processing Profiles.
Important:When this preference is enabled, it takes precedence over the Restrict Payment Methods by Customer Currency preference on the Shopping subtab of your Website record at Commerce > Websites > Website List. This means that even if the Restrict Payment Methods by Customer Currency is disabled, only those payment methods that support the shopper’s currency are displayed on your web store.
In addition, if no payment method supports the shopper’s currency, no payment method shows on the Payment Information page of your web store. (This is the opposite behavior of the Restrict Payment Methods by Customer Currency preference.)
-
Click Save.
Now, only compatible payment processing profiles show in the Payment Processing Profile field on the Payment subtab of a sales order, cash sale, or any other transaction that has this subtab.
Regional Payment Gateways
NetSuite integrates with payment card gateways that provide card processing services for a specific country or region. To use a regional payment card gateway, the Payment Gateway SuiteApp must be installed in your account. The SuiteApp is automatically provisioned in some accounts. For others, you must install it from Customization > SuiteBundles > Search & Install Bundles. For more information about installing the Payment Gateway SuiteApp, see Installing the Payment Gateway SuiteApp.
Regional payment gateways do not support credit requests.
To learn more, see the following topics: