Support team: 1-781-574-0500 or support@aurusinc.com
Support Portal: http://www.aurusinc.com/support-portal.php
Account Representative: kmamidishetty@aurusinc.com
Questions about issues experienced on the CCT operating system.
Processing questions, and assistance (i.e. what went through their platform, how was it funded, etc.), and general business (assistance with websites / reporting tools, merchant account updates, etc.).
Card terminal and accompanying cable replacements.
Be prepared with any pertinent information included but not limited to-
The serial number from the bottom of the CCT for the salon you are working with.
The business name and owner’s name, for reference as necessary.
Any details about the situation being dealt with, to provide to the Aurus rep you work with.
Whizpay logs.
Aurus can update devices remotely, so be absolutely sure that it’s finding an internet connection before you proceed – they can take care of the rest, once you have provided all the details.
The latest version of SuperSalon from ioffice.supersalon.com/update
A support integrated credit card processor (see below).
Merchant account provided by Aurus to the customer.
Help from ProPoint staff to help configure the software and hardware to allow processing!
Under Aurus software settings, check the readout for terminal version. If CCT version is 13.45 or higher then proceed. to step 2.
If CCT version is lower than 13.45 do not update – Coordinate with Aurus team to update the swiper.
Downgrade the location back to 5.9.15 if possible to restore CCT functionality until the time Aurus can get the swiper updated.
Make sure .net framework is installed, minimum of 4.5 but use most current.
This step is vital, if .net framework is not installed the patch files will not properly unpack the AESDK installer.
After updating .net, run the 6.0 AIO to update from previous versions.
This AIO contains the AESDK updater and is required for Aurus locations.
After the update file is run restart the computer if it did not automatically.
Verify the AESDK is on 5.0.1.7 through SW settings before continuing.
Apply the most current 6.2.x or higher patch.
Test CCT functionality.
Ingenico swipers are not compatible with the new update, and will need to remain on version 5.9.15 until future notice. Only the Verifone MX swipers can be updated.
Tip setups are manual on Aurus end – record them before scheduling Aurus to update the terminal and notify Aurus what the tips are, IE 1, 2, 3$ vs 10-15-20%
If tips are not setup correctly after the update, Aurus will need to be contacted with what it should be set to.
If beeping – communication error, verify ecrip and ecurl match the IP address of the POS, and ensure IP is static.
Manual entry has changed, it used to be press Cancel, and manual entry would show.
After update – 3 half swipes or 3 failed swipes triggers manual entry.
Pressing Cancel after the update will fully cancel the transaction.
Download and install AESDKInstall.bat
Read the requirements page for Aurus processing, and make sure the salon you are working with fulfills all of the criteria.
Go to C:/SuperSalon/SSproject/Include/Aurus and run the file titled AESDKInstall.bat as Administrator. You can also find it at http://download.supersalon.com/updates/
The image below illustrates the command line processes that will be seen during the installation.
Open services.msc and check that the AurusEnterpriseSDK service has a Status of “Running”.
Check that these ports aren’t already open for some reason before you create new rules to do so.
Take the naming scheme seriously as you create each rule in the Firewall, to make it easier for any technician troubleshooting in the future!
If the client uses a third-party firewall that is different from the one that comes stock with Windows, use the following for port configuration if Aurus does not start.
Pos1.auruspay.com
Port-22
Open inbound and outbound rules in the Windows Firewall, for ports 15583, 8000, 22 for both TCP and UDP. This means there will be 4 rules:
Aurus1 – TCP Inbound
Aurus2 – UDP Inbound
Aurus3 – TCP Outbound
Aurus4 – UDP Outbound
See the Opening a Firewall Port article to learn how to do this.
Click here if you don’t know how to configure a Windows PC to have a static IP address.
Press 1 – 5 – 9 keys at the same time to enter the configuration menu.
Try entering one of the default passwords listed below and press enter, in order until one of them works-
166832
121337
Check that the device is on version 10.66.
Go to Admin → Config → Config.user1 and set both the ECRIP and ECRURL to the IP address of the POS – it will be the same IP address you configured the POS to use statically in the previous step.
Press 1 – 5 – 9 keys at the same time to enter the configuration menu.
Try entering one of the default passwords listed below and press enter, in order until one of them works-
166832
121337
Check that the device is on version 11.54.
Go to Admin → Config → Config.user1 and set both the ECRIP and ECRURL to the IP address of the POS – it will be the same IP address you configured the POS to use statically in the previous step.
Press 1 – 9 – 5 – 7 in order! – not at the same time, like on the MX9 devices.
Try entering one of the default passwords listed below and press enter, in order until one of them works-
835779
905305
46436426
315302
911985
Once you are in the screen go to Test Term ID 87279831 and confirm that the version is 9.10.
Press “-” and “Clear” at the same time to reboot.
Go to Admin → Config → Config.user1 and set both the ECRIP and ECRURL to the IP address of the POS – it will be the same IP address you configured the POS to use statically in the previous step.
Press 1 – 9 – 5 – 7 in order! – not at the same time, like on the MX9 devices.
Try entering one of the default passwords listed below and press enter, in order until one of them works-
835779
905305
46436426
315302
911985
Once you have access, go to Test Term ID 87279831 and confirm that the version is ??????
Go to Setup → Software Settings → Hardware → Payment Processor. Under the Payment Gateway, select Payment Processor, set it to Aurus, and click the done button.
With Aurus selected as the Payment Processor, scroll down to find the following and confirm connection status:
The current state of the Aurus Windows Service.
A button to restart the aforementioned service if necessary.
The current version of the CCT firmware.
The current status of the CCT to show communication with SuperSalon.
The current AESDK version being used by the system.
Go to Setup → Software Settings → Hardware → Payment Processor and scroll down to the Aurus section. Click the Payments List button. Select all necessary payment methods, click done, save the page, and press f5.
Go to Setup → Payment Methods, and confirm that the automated utility properly loaded the payment methods. If for some reason the utility did not work, continue below to learn how to manually add the necessary payment methods.
Payment types can also be entered manually one at a time from the Payment Methods sub menu by using the illustration below as a guide for the different card types. Only do this when necessary, as the automated payment method utility in software settings is intended to prevent mistakes and limit time spent configuring settings.
It is also possible to add them all at once via inserting them directly into the database using the following SQL insert query shown below. Check with a senior technician before attempting this!
INSERT INTO `services` (`ID`, `type`, `code`, `description`, `dirty_bit`, `issuer_id`, `payment`, `register`) VALUES (NULL, 'Payment', 'VIC', 'Visa Credit Card', '1', 'VIC', 'credit', '10' );
INSERT INTO `services` (`ID`, `type`, `code`, `description`, `dirty_bit`, `issuer_id`, `payment`, `register`) VALUES (NULL, 'Payment', 'MCC', 'Master Credit Card', '1', 'MCC', 'credit', '11' );
INSERT INTO `services` (`ID`, `type`, `code`, `description`, `dirty_bit`, `issuer_id`, `payment`, `register`) VALUES (NULL, 'Payment', 'AXC', 'AMEX', '1', 'AXC', 'credit', '12' );
INSERT INTO `services` (`ID`, `type`, `code`, `description`, `dirty_bit`, `issuer_id`, `payment`, `register`) VALUES (NULL, 'Payment', 'DCC', 'Diners Clb Card', '1', 'DCC', 'credit', '13' );
INSERT INTO `services` (`ID`, `type`, `code`, `description`, `dirty_bit`, `issuer_id`, `payment`, `register`) VALUES (NULL, 'Payment', 'NVC', 'Discover Credit Card', '1', 'NVC', 'credit', '14' );
INSERT INTO `services` (`ID`, `type`, `code`, `description`, `dirty_bit`, `issuer_id`, `payment`, `register`) VALUES (NULL, 'Payment', 'JBC', 'JCB Credit Card', '1', 'JBC', 'credit', '15' );
INSERT INTO `services` (`ID`, `type`, `code`, `description`, `dirty_bit`, `issuer_id`, `payment`, `register`) VALUES (NULL, 'Payment', 'DBD', 'Debit Cards', '1', 'DBD', 'credit', '16' );
INSERT INTO `services` (`ID`, `type`, `code`, `description`, `dirty_bit`, `issuer_id`, `payment`, `register`) VALUES (NULL, 'Payment', 'IND', 'Interac', '1', 'IND', 'credit', '17' );
INSERT INTO `services` (`ID`, `type`, `code`, `description`, `dirty_bit`, `issuer_id`, `payment`, `register`) VALUES (NULL, 'Payment', 'VID', 'Visa Debit', '1', 'VID', 'credit', '18' );
INSERT INTO `services` (`ID`, `type`, `code`, `description`, `dirty_bit`, `issuer_id`, `payment`, `register`) VALUES (NULL, 'Payment', 'MCD', 'Master Debit', '1', 'MCD', 'credit', '19' );
INSERT INTO `services` (`ID`, `type`, `code`, `description`, `dirty_bit`, `issuer_id`, `payment`, `register`) VALUES (NULL, 'Payment', 'AXD', 'American Express Debit', '1', 'AXD', 'credit', '20' );
INSERT INTO `services` (`ID`, `type`, `code`, `description`, `dirty_bit`, `issuer_id`, `payment`, `register`) VALUES (NULL, 'Payment', 'DCD', 'DinersClub Debit', '1', 'DCD', 'credit', '21' );
INSERT INTO `services` (`ID`, `type`, `code`, `description`, `dirty_bit`, `issuer_id`, `payment`, `register`) VALUES (NULL, 'Payment', 'NVD', 'Discover Debit', '1', 'NVD', 'credit', '22' );
INSERT INTO `services` (`ID`, `type`, `code`, `description`, `dirty_bit`, `issuer_id`, `payment`, `register`) VALUES (NULL, 'Payment', 'JBD', 'JCB Debit', '1', 'NVD', 'credit', '23' );
INSERT INTO `services` (`ID`, `type`, `code`, `description`, `dirty_bit`, `issuer_id`, `payment`, `register`) VALUES (NULL, 'Payment', 'DBC', 'Credit Card MCard', '1', 'DBC', 'credit', '23' );
Issue:
Aurus is receiving alerts as “Invalid Store Identifier/Invalid POS ID” which refers to Invalid Registry name(Computer name) in Device Registration Process from the stores.
They have come up with fix where we need to run this file on POS so that it will set the parameter and AESDK will not go for registration as a result of that alert will not be generated.
What does it do?
It will update the “Is registered” Parameter to “This Device is Registered”
How do we do this?
Please download – https://ioffice.supersalon.com/update/Aurus_AESDKConfigUpdate.zip
Unzip contents Place both files on C: \AurusInc\AurusEnterpriseSDK
Stop Aurus Service
Rename the file “C: \AurusInc\AurusEnterpriseSDK\Log\logfile” for today
Run the exe
Start Service
This will create a new file for today
Check the value in the Last created file.ISREGISTERED N is the wrong value. Something like “This device is already registered” is good
If you do not get that value please check the date to make sure the right file is being renamed.
The reason we are using these steps is because a newly created log reads these values only and easier to see what they were before and after (edited)
How long does it take?
When you execute the file it will show a blank command prompt for about 2 mins
Then you are done!
Locations affected
https://docs.google.com/spreadsheets/d/16fOMNTIvB0H4DwaJwmqTxJ3iYSNwpZvJLieDXBBW5VI/edit#gid=0
Restart the Aurus service in services.msc!