Discussions
Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Update your Profile with your Support type to get your Support Type badge.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
NetSuite 2025.2 Release Notes - This document summarizes the changes to NetSuite between 2025.2 and the previous release.
To help you get the most out of your 2025.2 Release Preview account, review the topics outlined in the 2025.2 Release Preview Guide.
SuiteWorld October 6 - 9, 2025: Agenda Builder is live!
Read on for the latest updates including:
• Agenda Builder launch
• SuiteWorld On Air registration
• New NetSuite Prompt Studio Contest
• And more!
Check out this thread to learn more!
Read on for the latest updates including:
• Agenda Builder launch
• SuiteWorld On Air registration
• New NetSuite Prompt Studio Contest
• And more!
Check out this thread to learn more!
Duplicate authorisations with SECPay transactions via Netsuite
I have recently noticed that when a customer places an order on my netsuite ecommerce site, an autorisation code is obtained.
When the order is billed, instead of 'releasing' the transaction using the same authorsation code, netsuite is performing a new transaction and obtaining a new authorisation code.
This causes problems with customers who are taken close or over their credit limit.
Is the only answer to this problem to uncheck 'Require Authorisation for Credit Card Transactions' in web site setup?
I have used SECPay for a number of years before becoming a netsuite user with their defer function sucessfully reusing the original authorisation code.
0