SuiteCommerce
NetSuite 2023.1
2026-04-19

ACH Payments Now Available on SuiteCommerce Web Stores

SuiteCommerce, SuiteCommerce MyAccount, and SCA 2023.1+ now support ACH (Automated Clearing House) payments in checkout and My Account flows, requiring the Payment Instruments feature to be enabled.

Affects:SuiteCommerceSuiteCommerce AdvancedSuiteCommerce MyAccountPayment Instruments

What Changed

ACH payment processing is now available as a payment method on Commerce web stores. This applies to:

  • SuiteCommerce
  • SuiteCommerce MyAccount
  • SuiteCommerce Advanced (SCA) — 2023.1 release and later

End users on your Commerce site can now:

  • Pay an invoice using an ACH transaction
  • Pay a sales order during the checkout flow
  • Add, edit, or remove an ACH payment instrument from My Account

Important: This feature is distinct from ACH Processing (the back-office batch payment feature). The two are unrelated.

Prerequisites

  • The Payment Instruments feature must be enabled before ACH payment methods can be created or used on the web store. This is enabled via Setup > Company > Enable Features > Transactions (see Oracle's docs on Enabling the Payment Instruments Feature under Order Management).
  • Payment setup tasks must be completed in NetSuite before ACH is available on the storefront. Oracle references a dedicated prerequisites page (Prerequisites for ACH Payments on Web Stores) for the full checklist.

What To Do

  1. Enable the Payment Instruments feature if it is not already active. Navigate to Setup > Company > Enable Features and confirm it is checked under the Transactions subtab.
  2. Complete ACH payment setup in NetSuite following Oracle's Prerequisites for ACH Payments on Web Stores and Set Up ACH Payments for Commerce Web Stores guides.
  3. Review SCA version: If you are running SuiteCommerce Advanced, confirm you are on the 2023.1 release or later. Earlier SCA versions do not support this feature.
  4. Test the user experience: Oracle documents specific UX flows for ACH in Web Store User Experience for ACH Payments. Review the documented limitations (Limitations of ACH Payments on Web Stores) before going live.
  5. Customizations check: If you have custom checkout or My Account SuiteCommerce extensions that override payment method rendering or payment processing logic, verify they do not conflict with the new ACH payment instrument type.

Gaps in the Source

Oracle's documentation does not specify which record types or fields are involved (e.g., whether a new paymentinstrument subtype is created), what SuiteScript or REST API surface is exposed for ACH instruments, or whether any new roles/permissions are required. If you need to interact with ACH payment instruments programmatically, inspect the Payment Instrument record in your sandbox after enabling the feature and review the Records Browser for any new subtypes or fields.