When configuring payment processing in SuiteCommerce Advanced (SCA), it’s essential to understand the rigid hierarchy that governs how profiles are applied. Despite the presence of multiple configuration points, only one truly dictates behavior at runtime—and it cannot be bypassed.
🧩 The Core Constraint: Website-Level Binding
Each website record in NetSuite can be associated with only one payment processing profile. This association is absolute and overrides any other configuration, regardless of domain complexity or customer-specific settings.
- Even if your site operates as a microsite with multiple domains (e.g.,
shop.brandA.com,shop.brandB.com), you cannot assign different payment processing profiles per domain. - The profile set in the website setup is the sole authority. All transactions routed through that site—regardless of domain—will use the same payment processor.
🧍‍♂️ Customer Record Field: Misleading Flexibility
NetSuite also provides a field in the customer record to assign a payment processing profile. However, this field is non-functional in the context of SCA.
- Setting a profile here does not override the website-level configuration.
- It may appear to offer flexibility for customer-specific routing, but in practice, it is ignored during checkout.
đźš« No Workarounds, No Exceptions
This behavior is hardcoded into the SuiteCommerce architecture. Attempts to circumvent it—whether through scripting, custom workflows, or domain-based logic—will not succeed.
- The checkout process strictly adheres to the website’s configured profile.
- Any deviation from this setup will result in failed transactions or unsupported behavior.
âś… Best Practice: Align Website Structure with Payment Needs
If your business requires different payment processors for different brands, regions, or domains, the only viable solution is to:
- Create separate website records in NetSuite.
- Assign a unique payment processing profile to each.
This ensures clean separation and predictable behavior across all customer touchpoints.