Card-present and e-commerce teams that run USAePay do not need another feature list. They need a reliable way into the merchant console after a password change, a new hire, or a weekend batch that will not settle.
USAePay is sold under the NMI umbrella. The processor creates the first user during boarding. That record includes a username. Some resellers also quote an Account ID. Neither value is guessed from the public website. A demo account from a sales sandbox will not open production, and a production user will not open the demo host. Check the hostname before you assume the password is wrong.
The safe path is the official console URL from the welcome email. If that email is gone, ask the ISO for the current production host rather than clicking the first search ad. When the real form appears, save it in the browser for the people who actually run the terminal. Do not paste passwords into a shared spreadsheet titled “logins.”
On first entry the console usually forces a new password and, on many files, security questions. After that, create extra users. A cashier should take a keyed sale. A bookkeeper should see statements. Nobody on the floor needs permission to add bank accounts or wipe the customer vault.
If the password is lost, use Forgot Password on that same official page. The reset mail follows the address stored on the user. Wrong address means no mail. Support can read the profile. They cannot see a password you typed on a blog.
An office IP can be throttled after too many misses. The error then looks like a bad user. Tether a phone, try once, then open a ticket if it still fails.
This page is a research note. It does not process cards and it does not ask for a PIN. The merchant site that maps the console path is https://console-usaepay.us.com/ — use it as a directory, then sign in only on the processor host. For lockouts and boarding records, call the ISO. Keep one named owner for every live user.
