NetSuite Payment Processing: Gateways, Methods & Setup (2026)

NetSuite payment processing: collecting money and paying vendors

Payment processing in NetSuite covers both sides: collecting payments from customers (credit cards, ACH, electronic payments) and disbursing payments to vendors (checks, ACH/EFT, wire transfers). Getting both sides right means faster cash collection, lower processing costs, and accurate financial records.

TL;DR: NetSuite supports payment processing through SuitePayments (built-in payment gateway integration), third-party gateway connections (Stripe, PayPal, Authorize.net), and electronic payment features for vendor disbursements (ACH/EFT, checks). For customer-facing payments, SuitePayments provides PCI-compliant credit card processing with tokenization. For vendor payments, NetSuite generates ACH files and check runs. The key consideration is PCI compliance — how you handle credit card data within NetSuite affects your compliance requirements.

---

Customer payment collection

SuitePayments

SuitePayments is NetSuite's built-in payment processing framework. It provides:

• Gateway management: Connect and manage multiple payment gateways from within NetSuite
• Credit card processing: Authorize, capture, and refund credit card transactions
• ACH/eCheck: Accept electronic check payments from customers
• Tokenization: Store customer payment methods as tokens (not actual card numbers) for PCI compliance
• Recurring billing: Process recurring charges on stored payment methods

Supported gateways through SuitePayments include:

• CyberSource (now Visa)
• Authorize.net
• PayPal
• Payflow Pro
• Worldpay
• Adyen

Payment flow for online orders

When a customer places an order (through SuiteCommerce, Shopify, or another storefront):

1. Authorization: The payment gateway authorizes the card for the order amount. Funds are held but not yet captured.
2. Order processing: The order is reviewed, inventory allocated, fraud checks run.
3. Capture: When the order ships (or on a schedule), NetSuite sends a capture request to the gateway. Funds are transferred.
4. Settlement: The gateway settles the transaction, and funds arrive in your bank account (typically 1-2 business days).
5. GL recording: NetSuite records the cash receipt against the customer's AR balance.

Payment flow for invoiced sales

For B2B customers paying invoices:

1. Invoice sent: Customer receives the invoice with payment options
2. Customer payment portal: Customer can pay online through a payment link on the invoice (if configured)
3. Payment received: ACH, credit card, or check — payment is recorded against the invoice
4. Application: The payment is applied to specific invoices, reducing the AR balance

Refunds and credits

Refund processing flows through the same gateway:

1. Credit memo: Created in NetSuite for the amount to be refunded
2. Refund transaction: NetSuite sends a refund request to the payment gateway
3. Customer receives refund: Through the original payment method
4. GL recording: AR is adjusted, cash is reduced

---

PCI compliance

Why it matters

If you process, store, or transmit credit card data, you must comply with PCI DSS (Payment Card Industry Data Security Standard). Non-compliance can result in fines, higher processing fees, and liability for data breaches.

NetSuite's approach

Tokenization: SuitePayments replaces actual card numbers with tokens. The token can be used to process future transactions, but if your NetSuite instance is compromised, the tokens are useless without the gateway's decryption.

Gateway-hosted payment pages: For SuiteCommerce and other web storefronts, the payment form can be hosted by the gateway (iframe or redirect). Card data never touches your NetSuite server.

PCI scope reduction: By using tokenization and hosted payment pages, you reduce your PCI scope from the full SAQ D (self-assessment questionnaire for merchants that handle card data directly) to SAQ A or SAQ A-EP, which have far fewer requirements.

What to avoid

• Storing raw card numbers in NetSuite custom fields — this is a PCI violation
• Emailing credit card numbers — even in encrypted emails
• Processing cards manually through a separate terminal without recording in NetSuite — creates reconciliation gaps
• Using outdated gateways that don't support tokenization

---

Vendor payment disbursement

ACH/EFT payments

For paying vendors electronically:

1. Configure vendor banking: Enter vendor bank account and routing numbers on the vendor record
2. Approve vendor bills: Bills go through approval workflow
3. Create payment batch: Select bills to pay via Transactions > Payables > Pay Bills
4. Generate ACH file: NetSuite creates a NACHA-formatted file
5. Submit to bank: Upload the ACH file to your banking portal
6. Reconcile: Match bank debits to NetSuite payment records

ACH payments are cheaper than checks ($0.25–1.00 per transaction vs. $3–8 per check including printing, postage, and handling) and clear faster.

Check payments

For vendors that require checks:

1. Configure check printing: Set up check format (alignment, bank account, check stock)
2. Create payment batch: Select bills to pay by check
3. Print checks: NetSuite generates checks on pre-printed check stock (laser printer compatible)
4. Record check numbers: Assigned automatically when printed
5. Mail checks: (Consider check mailing services to avoid this entirely)

Wire transfers

For high-value or international payments:

• Wire transfers are typically initiated through your bank's portal, not directly from NetSuite
• Record the wire in NetSuite as a vendor payment after execution
• Include wire reference numbers for reconciliation

Virtual cards

A growing payment method where you generate a single-use virtual card number for each vendor payment:

• Revenue opportunity: Virtual card programs typically earn 1–1.5% rebate on spend
• Security: Single-use numbers can't be reused if compromised
• Vendor acceptance: Not all vendors accept card payments (many charge a convenience fee)

---

Payment automation tools

NetSuite Electronic Bank Payments

The native module for ACH/EFT payment generation. Supports:

• NACHA (US ACH)
• BACS (UK)
• SEPA (Europe)
• Country-specific formats for many other regions

Tipalti

Third-party AP automation that handles the full payment cycle:

• Vendor onboarding and tax form collection
• Multi-method payment execution (ACH, wire, check, PayPal, virtual card)
• Global payments (190+ countries)
• Tax compliance (1099, W-8/W-9)
• NetSuite integration via SuiteApp

Paystand

B2B payment network focused on eliminating transaction fees:

• Zero-fee ACH and bank-to-bank payments
• Smart lockbox for check digitization
• NetSuite integration
• Best for companies looking to reduce payment processing costs

---

Payment reconciliation

The reconciliation challenge: your payment gateway, your bank, and your NetSuite GL all need to agree.

Customer payment reconciliation

1. Gateway settlement report: The gateway settles transactions daily, depositing a net amount (gross transactions minus fees, refunds, and chargebacks)
2. Bank deposit: The net amount appears in your bank account
3. NetSuite GL: Individual payment records totaling the gross amount, with fees recorded separately

The gap between gross (what NetSuite records) and net (what the bank receives) is the processing fees. Configure NetSuite to record fees as they're deducted so the bank deposit matches the GL.

Vendor payment reconciliation

1. NetSuite payment records: Each vendor payment with amount and date
2. Bank debits: Each ACH debit or check clearing
3. Matching: Match NetSuite payments to bank debits by amount, date, and reference

With bank feeds enabled, this matching happens largely automatically through Match Bank Data.

---

Frequently Asked Questions

How does payment processing work in NetSuite?expand_more

What payment gateways does NetSuite support?expand_more

Is NetSuite PCI compliant?expand_more

Can NetSuite generate ACH payment files?expand_more

What is SuitePayments in NetSuite?expand_more