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.
Don't miss out on our Question of the Week! You only have until tomorrow, November 6, 2025, 2PM ET to comment your answers and earn rewards! Click here for more details.
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!
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.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more
SecPay / PayPoint Problems
We've been having problems recently billing some of our transactions that have been authorized through SecPay (now PayPoint). Here are the details:
- A Sales Order - Cash Sale is created and processes through SecPay correctly. A Defer transaction is created in SecPay.
- When we try to bill (often times just a few hours after the Sales Order is created) charging the card fails. When we log into SecPay, you can see that the "release" attempt for the initial defer transaction has failed.
We have called SecPay tech support several times and they insist that NetSuite is initiating a completely new transaction at the billing stage instead of releasing the original defer and this is what is causing the problem.
0