NetSuite Pay Workflow: Setup, Payment Link, Settlement

NetSuite Pay setup, Payment Link prerequisites, payment processing, tokenization, and settlement reconciliation for U.S. and Canadian accounts.

·7 min read·View Oracle Docs

NetSuite Pay lets NetSuite users accept credit card and ACH payments across e-commerce, point of sale, and accounts receivable channels. Implementation includes the SuiteApp, merchant-account underwriting, payment-profile configuration, settlement reconciliation, and testing. Payment Link is an optional companion feature for sending invoices with a payment link or QR code.

What does the NetSuite Pay workflow cover?

NetSuite Pay is an integrated payment processing solution for NetSuite users. It supports credit card payments online, over the phone, at the point of sale, or through another digital payment method. For credit card and ACH payments across e-commerce, point-of-sale, and accounts receivable channels, Versapay processes the transactions and they are reconciled.

NetSuite describes the workflow as a combination of payment acceptance, payment-card data protection, transaction visibility, and settlement activity. It provides a complete transaction record, a 360-degree view of customer transaction history, and detailed audit tracking while maintaining the security of payment card data.

Workflow areaWhat NetSuite Pay provides
Merchant onboardingAn application and onboarding process embedded in NetSuite; underwriting and merchant service are powered by Versapay
Payment acceptanceCredit card and ACH payments across e-commerce, point of sale, and accounts receivable channels
Card-data handlingTokenization and safe storage of sensitive credit card data in compliance with PCI DSS
CollectionsAutomated click-to-pay invoices as part of native workflows
Settlement activityDaily and monthly settlement reports and notifications for open settlements that need resolution

NetSuite Pay also provides simple, transparent pricing through a streamlined application and onboarding process. Administrators should treat the merchant application, payment processing profile, and settlement-reconciliation configuration as separate implementation steps rather than assuming that SuiteApp installation alone completes the workflow.

How do you access the NetSuite Pay dashboard?

The NetSuite Pay dashboard provides information about NetSuite Pay benefits, the underwriting process, pricing details, and available help. NetSuite detects whether the account location is the United States or Canada and displays location-specific dashboard content.

To access it, go to NetSuite Pay > NetSuite Pay Overview.

If the dashboard is not visible, set up the custom portlet:

  1. Go to NetSuite Pay > NetSuite Pay Overview.
  2. In the portlet, click the menu and select Set Up.
  3. Select Versapay PL NetSuite Pay Dashboard.
  4. Click Save.

This path is specifically for the dashboard portlet. It does not replace the implementation tasks required to install, apply for, configure, and test NetSuite Pay.

Which payment and customer-facing capabilities are available?

NetSuite Pay clients can accept credit card and ACH payments directly in NetSuite across the listed channels. They can also choose the payment methods they accept, including credit card types and ACH. The solution supports automated click-to-pay invoices in native workflows, which NetSuite says can speed collection times and eliminate hours spent reconciling payments with NetSuite.

For payment card data, NetSuite Pay tokenizes and safely stores sensitive credit card data in compliance with PCI DSS. The source also describes PCI-compliant data security and detailed audit tracking as part of the transaction record available to the business.

NetSuite Pay works with the following customer-facing NetSuite experiences:

  • NetSuite Customer Center
  • SuiteCommerce MyAccount
  • SuiteCommerce Advanced My Account
  • SuiteCommerce Advanced Webstore

Through Customer Center, SuiteCommerce MyAccount, and SuiteCommerce Advanced My Account, business buyers can view invoices, securely add and manage payment methods, and pay faster and more efficiently. The source also identifies SuiteCommerce Advanced Webstore as an integration point.

For related reading, see Automating Payment Adjustments in NetSuite 2026.2 and NetSuite Pay: Enhanced Order Management and Security Features.

How does Payment Link work with NetSuite Pay?

Payment Link works in conjunction with NetSuite Pay and is optional during the NetSuite Pay implementation process. It enables e-invoices that include a payment link or QR code leading to a secure payment page. After Payment Link setup is complete, a customer can use a computer or mobile device to review an invoice on the Payment Link Checkout page, choose a payment method, and submit payment.

Payment Link configuration can include the following options:

Configuration optionSupported behavior
Payment methodsSelect certain payment methods for the payment link
Partial paymentsAllow partial payments
Company presentationInclude a company logo and company information
Customer emailsCustomize email templates that inform customers when payment is accepted or rejected
Invoice accessSend a link or QR code in an email

The general Payment Link feature requires several prerequisites before use:

  1. Enable Payment Instruments at Setup > Company > Enable Features > Transactions > Payment Processing.
  2. Allow online credit card payments.
  3. Set up payment methods.
  4. Set up payment processing profiles for each credit card gateway.
  5. Set up DomainKeys Identified Mail (DKIM) to authenticate emails from the account.

Payment Link can let customers choose a payment method from a selected list; the source identifies credit cards and PayPal among the available methods for the feature. In the NetSuite Pay context, the source also states that customers can pay bills with a click by credit or debit card.

For guidance on a test connection, see Testing Versapay Payment Gateway Connection in NetSuite Pay.

What are the NetSuite Pay setup and approval steps?

Implementation begins with the NetSuite Pay SuiteApp and proceeds through merchant-account approval and configuration. The documented sequence is:

  1. Install NetSuite Pay from the SuiteApp Marketplace. The SuiteApp is automatically installed for new customers in the United States.
  2. Sign the Estimate/Order Form. Customers in the United States and Canada, excluding Quebec, can download the SuiteApp and sign the form by using DocuSign. Customers in Quebec must contact their account manager to complete signing.
  3. Enable all prerequisite features.
  4. Complete the Versapay merchant account application.
  5. Wait for application approval. The processing partner’s underwriting team responds within 48 hours after receiving a complete application. Questions or document needs may be handled by phone call or email, and delayed responses can slow approval.
  6. Configure the NetSuite Pay payment processing profile.
  7. Configure automated settlement reconciliation.
  8. Optionally set up Payment Link. This can occur in parallel while waiting for merchant-account approval.
  9. Connect to a Versapay Test Payment Gateway to test NetSuite Pay functionality before processing real transactions.

The embedded application and onboarding process is part of NetSuite Pay, while underwriting and merchant service are powered by Versapay. A test gateway connection is therefore a documented pre-production step, not a substitute for merchant approval or payment-profile configuration.

For additional related reading, see NetSuite Pay SuiteApp Enhancements: Compliance and Testing 2026.1 and NetSuite Pay: Integrated Payment Processing Solution 2026.1.

How are payments and settlements handled?

When customers make credit card or ACH payments, Versapay processes the transactions and they are reconciled. NetSuite Pay makes daily and monthly settlement reports available and notifies users about open settlements that need resolution.

The setup documentation specifically includes automated settlement reconciliation as a configuration task. Teams responsible for settlement activity should account for both the configuration step and the ongoing review of available settlement reports and open-settlement notifications. The source does not describe a separate external reconciliation process; it states that click-to-pay invoices can eliminate hours spent reconciling payments with NetSuite.

Who This Affects

  • NetSuite administrators: Install the SuiteApp, enable prerequisite features, configure the payment processing profile, configure automated settlement reconciliation, and set up the dashboard portlet when needed.
  • Finance and accounts receivable teams: Use click-to-pay invoices, review daily and monthly settlement reports, and address open settlements that need resolution.
  • Teams sending invoice emails: Configure Payment Link, selected payment methods, partial-payment behavior, company information, notification templates, and DKIM prerequisites.
  • Commerce and customer-service teams: Support payment experiences across e-commerce, point of sale, accounts receivable, Customer Center, and the listed SuiteCommerce experiences.

For related workflow material, see Workflow Performance Optimization in NetSuite and Scheduled Workflow Logs for Enhanced Tracking in NetSuite 2026.1.

Key Takeaways

  • NetSuite Pay supports credit card and ACH payments across e-commerce, point of sale, and accounts receivable channels directly in NetSuite.
  • The implementation path includes SuiteApp installation, form signing, prerequisite features, a Versapay merchant application, approval, payment-profile configuration, settlement reconciliation, and test-gateway validation.
  • Payment Link is optional and can be configured while merchant-account approval is pending; it supports invoice emails with payment links or QR codes.
  • NetSuite Pay tokenizes and safely stores sensitive credit card data in compliance with PCI DSS, while providing transaction history and detailed audit tracking.
  • Daily and monthly settlement reports are available, and users receive notifications for open settlements that need resolution.

Related Topics

  • NetSuite Pay Setup
  • Using NetSuite Pay
  • Accounts for NetSuite Pay

General Notices

Frequently Asked Questions (4)

What prerequisites must be configured before using Payment Link with NetSuite Pay?
Before using Payment Link you must enable Payment Instruments (Setup > Company > Enable Features > Transactions > Payment Processing), allow online credit card payments, set up payment methods, create payment processing profiles for each gateway, and configure DomainKeys Identified Mail (DKIM) to authenticate account emails.
What are the main implementation steps to set up NetSuite Pay and obtain merchant approval?
Implementation begins with installing the NetSuite Pay SuiteApp (auto-installed for new U.S. customers), signing the Estimate/Order Form (DocuSign for U.S. and Canada except Quebec), enabling prerequisite features, and completing the Versapay merchant application. After underwriting approval (typically within 48 hours of a complete application), configure the NetSuite Pay payment processing profile, set up automated settlement reconciliation, optionally configure Payment Link, and connect to a Versapay test payment gateway for validation.
How are payments processed and settlements reconciled in NetSuite Pay?
Versapay processes credit card and ACH transactions and those transactions are reconciled in NetSuite Pay. The solution provides daily and monthly settlement reports, notifies users about open settlements that need resolution, and requires configuring automated settlement reconciliation as part of the setup.
How does NetSuite Pay protect and store payment card data?
NetSuite Pay tokenizes and safely stores sensitive credit card data in compliance with PCI DSS. It also provides a complete transaction record with customer transaction history and detailed audit tracking as part of the payment workflow.
Source: NetSuite Pay Workflow Oracle NetSuite Help Center. This article was generated from official Oracle documentation and enriched with additional context and best practices.

Was this article helpful?

More in Billing

View all Billing articles →