Skip to main content
Category
NetSuite
Published
Updated
Reading time
18 min read

NetSuite Payment Gateways & Processing: Setup Guide

Which payment gateways NetSuite supports per Oracle docs, how SuitePayments and NetSuite Pay work, setup steps, processor fees, PCI, ACH/EFT and reconciliation.

Contents13 sections ↓

Payment processing in NetSuite covers two directions: collecting money from customers (cards, ACH, digital wallets, invoice payment links) and paying vendors (ACH/EFT files, checks, wires). This guide covers both, with every Oracle-specific fact linked to NetSuite's own Help Center as of October 2026.

Direct answer: NetSuite processes card payments through a payment processing profile that connects a transaction to a gateway. Oracle's preferred gateway partners are CyberSource, MerchantE and PayPal Payflow Pro; regional gateways come through Oracle's Payment Gateway SuiteApp; other processors (Adyen, Braintree, and more) plug in as SuitePayments partner SuiteApps; and NetSuite Pay, underwritten by Versapay, is Oracle's own card and ACH option in the US and Canada.

How payment processing works in NetSuite

Every card or ACH payment that NetSuite sends to a processor goes through a payment processing profile. Oracle: "To process a payment with a particular payment gateway integration, you must create a payment processing profile. The profile contains the parameters needed to establish communication with a payment gateway" (Creating Payment Processing Profiles). A profile is tied to a currency, a subsidiary, the payment methods it supports and the request types it can send (authorization, capture, sale, refund, credit).

Online orders (SuiteCommerce, a connected storefront, or a phone order entered by staff) follow the authorize-then-capture pattern:

  1. Authorization. The gateway authorizes the card for the order amount; funds are held, not moved.
  2. Order processing. The order is reviewed, inventory allocated, fraud rules and payment holds applied.
  3. Capture. When the order ships (or on a schedule), NetSuite sends a capture request; the cash sale or invoice records the payment.
  4. Settlement. The processor settles in batches and pays out a net amount to your bank.
  5. Reconciliation. The bank deposit is matched to the NetSuite payments, with fees recorded separately (see the reconciliation section below).

Invoiced B2B sales skip authorization: the customer receives an invoice, pays by check, wire, ACH, or a card through a payment link, and the customer payment is applied to the open invoice.

Refunds reverse through the same gateway: a credit memo or return creates the amount owed, a customer refund or cash refund sends the refund request to the gateway, and the customer is refunded to the original method.

The quality of the integration determines how much manual cleanup your team does. A good one handles partial captures, voids, refunds and error states cleanly; a weak one leaves orphaned authorizations and mismatched amounts.


Which payment gateways NetSuite supports

Oracle does not publish a single list of every processor, because most processors connect as partner SuiteApps. What the Help Center does document:

OptionWhat it isSource
CyberSourcePreferred gateway partner. NetSuite's card processing includes "fraud management using CyberSource's Decision Manager"Setting Up Payment Processing Profiles, Customer Credit Card Processing
MerchantEPreferred gateway partner, with the same order-screening rules as CyberSourceSame
PayPal Payflow ProPreferred gateway partner; "requires an add-on module be enabled in your NetSuite account"Same
SECPay (PayPoint)Legacy; maintained "only for existing payment card gateways"Same
Regional gatewaysAsiaPay, eWAY Rapid, PayU Latin America, SecurePay, VeriTrans, through the managed Payment Gateway SuiteApp (bundle 47196). "Regional payment gateways don't support credit requests."Payment Gateway
NetSuite PayOracle's integrated card and ACH processing; "underwriting and merchant service are powered by Versapay"; US and Canada; works with Payment LinkNetSuite Pay Overview
PayPal (web stores)The PayPal Integration feature with PayPal Express Checkout for Commerce web storesPayPal Integration and Express Checkout
SuitePayments partner SuiteApps"Pre-integrated SuitePayments partner solutions" listed on SuiteApp.com, for example Adyen and PayPal BraintreePayment Gateways

Two practical notes from Oracle's setup page: "You can use any number of credit card gateways in your NetSuite account", and in OneWorld "you can associate any number of credit card gateways with each subsidiary" (Setting Up Customer Credit Card Processing).


SuitePayments and NetSuite Pay

SuitePayments is NetSuite's name for gateway integrations built with certified payment partners. NetSuite describes it as access to "payment processing partners, including the use of PayPal, Apple Pay or another digital payment method", with fraud screening and 3D Secure checkout, relying on "a unique Payment Processing Profile within your NetSuite account" (NetSuite payment processing). The integration comes with NetSuite; the processing contract and its fees are between you and the payment provider.

NetSuite Pay is the option where Oracle handles onboarding. "NetSuite Pay is an integrated payment processing solution designed for NetSuite users", you "complete an application and onboarding process that is embedded in NetSuite (underwriting and merchant service are powered by Versapay)", and it lets you "accept credit card and ACH payments across e-commerce, point of sales, and accounts receivable channels directly in NetSuite." It works with Payment Link to "send e-invoices with a payment link or QR code to a secure payment page", allow partial payments, and send payment notifications. NetSuite Pay detects whether you are in the United States or Canada (NetSuite Pay Overview). Rates are set in that onboarding; Oracle does not publish them.

Which to pick: NetSuite Pay if you are in the US or Canada and want onboarding, AR payment links and card processing in one place; a SuitePayments partner if you already have a processor relationship, sell in more countries, or need that processor's specific payment methods.


How to set up a payment gateway in NetSuite

The steps below follow Oracle's Setting Up Customer Credit Card Processing and Creating Payment Processing Profiles.

  1. Enable the feature. Setup > Company > Enable Features, Transactions subtab, Payment Processing section: check Credit Card Payments. Partner integrations may also need Payment Instruments; check the partner's installation guide.
  2. Open a merchant account with a processor that supports your gateway. Oracle notes that "some merchant accounts only work with certain gateways."
  3. Install the integration if it is a SuiteApp. Partner gateways install as bundles and are switched on at Customization > Plug-ins > Manage Plug-ins; regional gateways need the Payment Gateway SuiteApp.
  4. Create the profile. Setup > Accounting > Payment Processing Profiles, then Enable & New or Add Profile on the Payment Gateway Integrations page. Configure Currency, Subsidiary, Supported Payment Methods, Gateway Request Types and Recommended Actions. Oracle requires "a payment card gateway profile for each settlement currency and merchant bank account your company uses."
  5. Create payment methods per card type. Oracle: "Don't create a generic payment method called Credit Card"; each name must be one the gateway recognizes.
  6. Set preferences at Setup > Accounting > Accounting Preferences, Items/Transactions subtab.
  7. Assign the profile to your web store if you sell online, then test every path: approval, decline, partial capture, void, full and partial refund, saved card, guest and logged-in checkout.

Processor by processor

Stripe + NetSuite

Stripe's own NetSuite product is the Stripe Connector for NetSuite, which Stripe describes as an app to "reconcile your Stripe activity into NetSuite": charges, refunds, disputes and payouts to bank deposits, Stripe Billing invoices, multi-currency payments, and invoice and customer payment pages. Stripe also offers a "free, self-serve version" that lets you "accept payments with a Stripe payment link, without syncing payments or other data to NetSuite" (Stripe docs). Stripe fits teams that already use Stripe Billing, Stripe Checkout wallets or Stripe Connect and want that activity reconciled in NetSuite.

PayPal + NetSuite

PayPal reaches NetSuite three ways: the native PayPal Integration with Express Checkout for web stores, PayPal Payflow Pro as a card gateway (add-on module), and Braintree as a SuitePayments partner SuiteApp. Payouts from channels outside NetSuite need a reconciliation app or a custom build. Our PayPal-NetSuite integration page walks through all three paths with Oracle's setup steps. Most stores offer PayPal next to a card processor rather than instead of one.

CyberSource + NetSuite

CyberSource is one of Oracle's preferred gateway partners and the one NetSuite's documentation ties to fraud tooling: Decision Manager for fraud management, payer authentication, level II and level III purchase card data, and rules that flag orders failing your payment criteria for review (Customer Credit Card Processing). It fits businesses where chargebacks or B2B purchase cards are a real cost. CyberSource does not publish standard pricing; quotes depend on volume and services.

Adyen + NetSuite

Adyen builds its own NetSuite bundles to "offer online, in-app, and in-person payments", including Pay by Link and local payment methods such as iDEAL, Klarna and Google Pay (Adyen docs). It fits multi-country NetSuite OneWorld accounts that want one processor for web and point of sale.

Authorize.Net

Authorize.Net is common in older NetSuite accounts. If you run it today, open Setup > Accounting > Payment Processing Profiles to see exactly which integration your account uses before planning a change, and ask any new processor whether it can import your stored card tokens; if it cannot, customers re-enter card details after the switch.

Published processing fees (US, October 2026)

ProcessorCard rateACH / bank debitSource
Stripe2.9% + 30¢ domestic cards; +1.5% international cards; +1% if currency conversion is requiredACH Direct Debit 0.8%, $5.00 capStripe pricing
PayPalStandard card payments 2.99% + $0.49; Advanced card payments 2.89% + $0.29; PayPal Checkout and Venmo 3.49% + $0.49ACH 0.80%, capped at $5.00PayPal merchant fees, last updated Oct 1, 2026
AdyenVisa and Mastercard: $0.13 + Interchange++ + 0.60%; "a minimum invoice depending on industry or business model"Varies by methodAdyen pricing
Authorize.NetAll-in-one: 2.9% + 30¢; gateway only: 10¢ per transaction + 10¢ daily batch fee; $25 monthly gateway feeeCheck 0.75%Authorize.Net pricing
CyberSource, NetSuite PayQuoted per merchant; no public rate cardQuoted—

Rates are the vendors' standard published prices; negotiated rates at volume are common and not reflected here.


SuiteCommerce payment considerations

Card data stays out of NetSuite's front end. Partner gateways render hosted payment fields or redirects in the SuiteCommerce checkout, so card numbers go from the shopper's browser to the processor. Your gateway choice changes how those fields look and which wallets appear (Apple Pay, Google Pay, PayPal, local methods).

3D Secure 2. Oracle's guidance for stores that need it is to run SuiteCommerce or the latest SuiteCommerce Advanced "and use a gateway that provides native 3D Secure 2 support"; Site Builder has no native support (Migrating from 3D Secure 1 to 3D Secure 2).

ACH on the web store. Oracle's prerequisites are a third-party SuiteApp that supports ACH, an ACH-type payment method with Display in Web Site checked, and a payment processing profile whose Gateway Request Types include Authorization and Capture Authorization (Prerequisites for ACH Payments on Web Stores).

Alternative payment methods. Some wallet and bank methods do not support authorization. For those, Oracle has the profile send sales requests instead, and "a customer deposit is automatically created and associated with the sales order", applied when the order is billed (Alternative Non-Credit Card Payment Methods for Web Store Orders).

Testing. Test every path before go-live: declined cards, partial refunds, voided orders, saved payment methods, guest versus logged-in checkout, and split shipments with partial captures.


B2B payment options in NetSuite

B2B customers expect payment terms, purchase orders and bank payments that consumer checkouts do not cover.

Payment terms and invoicing. NetSuite's native AR handles Net 30, Net 60, 2/10 Net 30 and custom terms without any gateway. The customer pays by check, wire or ACH within terms, and the payment is applied to the invoice.

ACH instead of cards on large invoices. Card fees scale with the amount; ACH fees are low or capped. At Stripe's published rates, a $50,000 invoice costs $5.00 by ACH Direct Debit (0.8%, $5 cap) versus $1,450.30 by domestic card (2.9% + 30¢). That gap is why many B2B sellers steer large invoices to ACH and accept cards for smaller ones.

Payment links on invoices. NetSuite Pay with Payment Link, or a partner's link-to-pay feature, puts a pay button or QR code on the e-invoice so the customer pays online and the payment lands on the invoice.

Card on file. Stored payment instruments on the customer record let you charge cards for recurring orders or on invoice due dates.

Wires. Large and international B2B payments still arrive as wires, outside any gateway. Your AR team matches them to open invoices, with bank data import and Match Bank Data doing most of the matching.

For portals where customers place orders and pay invoices, see our NetSuite B2B portal options.


Paying vendors: ACH, EFT and checks

Electronic Bank Payments. "The Electronic Bank Payments SuiteApp (formerly called NetSuite Electronic Payments) enables you to process bank payments of your vendor bills, employee expenses, partner and employee commissions, and customer refunds, and also enables you to receive bank payments from customers" (Electronic Bank Payments Overview). It generates payment files and direct debits "using each bank's predefined file format" and Positive Pay files; it does not transmit them to the bank, so the file is uploaded to your bank portal or sent through a bank connectivity integration. For US vendors, the vendor bank record's Payment File Format offers ACH-CCD/PPD or ACH-CTX (Free Text); other countries have their own formats in Oracle's Payment Formats for Countries.

EFT is the umbrella term. Electronic funds transfer covers ACH in the US, SEPA in Europe and domestic schemes elsewhere. When people search "NetSuite EFT", they usually mean one of three flows: vendor payments (outbound AP), customer direct debits (inbound AR), or payroll direct deposit.

A typical vendor ACH run:

  1. Store the vendor's bank details on the vendor record with the right payment file format.
  2. Approve vendor bills through your approval workflow.
  3. Select the bills to pay in the Electronic Bank Payments bill payment page and generate the file.
  4. Upload the file to the bank and record any bank-side rejections.
  5. Reconcile the bank debits to the NetSuite bill payments.

Checks print from NetSuite on pre-printed check stock, with check numbers assigned at print. Wires are usually initiated in the bank portal and recorded in NetSuite as the vendor payment, with the wire reference kept for reconciliation.

Third-party AP platforms. If you want vendor onboarding, tax forms and multi-method payouts handled outside NetSuite, AP automation platforms such as Tipalti and Paystand integrate with NetSuite; our AP automation guide compares the approaches.


Payment reconciliation: gross, net and fees

Your processor, your bank and your NetSuite GL have to agree, and they record the same money differently:

  1. NetSuite holds the individual customer payments at the gross amount.
  2. The processor settles in batches and deducts fees, refunds and chargebacks.
  3. The bank receives one net deposit per payout.

The gap between gross and net is fees and adjustments. Record them as separate lines (an expense account for processing fees, another for chargebacks) on the deposit, so the deposit equals the bank line. Then match it on the Match Bank Data page, which shows "side-by-side grids of imported bank lines and account transactions in NetSuite"; your role needs the Reconcile permission (Matching Bank Data).

When payments come from several processors or from channels outside NetSuite, a payout reconciliation app or a processor's own connector (Stripe Connector for NetSuite, Celigo's Payout-to-Reconciliation app for PayPal, Braintree, Stripe, Authorize.net and Amazon Pay) does the matching and creates the deposits and fee lines for you.


How to choose

Where you sell. NetSuite Pay covers the US and Canada. Selling across more countries and local payment methods points to a partner such as Adyen or a regional gateway.

Average order value. High-volume, low-value consumer orders favor simple blended card pricing. High-value B2B invoices favor ACH and interchange-plus pricing, where the percentage matters more than the fixed fee.

Fraud exposure. If chargebacks are a line on your P&L, weigh the fraud tooling (CyberSource Decision Manager is the one NetSuite documents natively) as heavily as the rate.

Subscriptions. Decide whether billing lives in the processor (Stripe Billing) or in NetSuite (SuiteBilling), and pick the integration that keeps revenue recognition in one place.

What you already run. Switching processors means new profiles, new testing and possibly re-collecting stored cards. Switch when the savings or capabilities are concrete.


PCI DSS: what NetSuite handles and what you own

What NetSuite says about itself. "NetSuite is Payment Card Industry Data Security Standard (PCI DSS) level 1 compliant." Card numbers belong only in NetSuite's encrypted fields (the Payment Instruments or Credit Card subtab on customers and the payment fields on sales orders, cash sales, deposits, payments and refunds). Numbers are masked to at most the first six and last four digits, and viewing unmasked numbers requires the View Unencrypted Credit Cards permission, granted only through Customer Support with a signed agreement and "for project work for a period of 90 days" (Payment Card Number Security and Compliance).

What you own.

  • Never store card numbers in custom fields, notes or memos. Oracle: "Entering payment card information in unencrypted fields violates the PCI Data Security Standard."
  • Never email card numbers, and don't key cards into a separate terminal without recording the payment in NetSuite.
  • Role permissions. Limit who can process refunds and see payment instruments.
  • Your annual Self-Assessment Questionnaire. Which SAQ applies depends on how card data reaches the processor (hosted fields, redirect, or staff keying cards in the NetSuite UI). Confirm it with your acquirer.
  • Third parties. Keep evidence that your processor and any app that touches card data are PCI compliant.

Frequently asked questions

What clients ask before signing


Sources

Mercedes · BrokenRubik

Replies by email within 24 hours

Mercedes

Working on something in NetSuite? Tell us in a line what you're trying to do, and a consultant will reply with next steps.

A person reads every message. No sales sequence.

Share
BrokenRubik

BrokenRubik

NetSuite Development Agency

Independent NetSuite consultancy specializing in NetSuite ERP, SuiteCommerce development, and enterprise integrations. 100+ companies served since 2017, from mid-market to enterprise OneWorld deployments.

10+ years experienceCeligo Standard Partner +2
NetSuite ERPSuiteCommerce AdvancedSuiteScript 2.xNetSuite Integrations+4 more

Related