AIM credit card information

AIM no longer comes into contact with cardholder data. This means that AIM is considered ‘Out of Scope’ and PA-DSS (Payment Application Data Security Standard) no longer applies. Please be aware that merchants still need to operate their business in a PCI compliant manner regardless of the POS application.

Tri-Technical Systems does not sell any EMV hardware devices. All EMV hardware can be obtained directly from your processing partner.

 

 Processor System Type
 		Status  
OpenEdge Hosted When processing a credit card transaction you will be in an OpenEdge hosted page inside the AIM software. Keyed entires do not require a hardware device. Autopays do not require a hardware device. Existing credit card swipes will continue to work. However, existing card swipes are not EMV compatible. The VeriFone debit pin pads will not be supported on this platform. The new hardware devices are the Ingenico iSC250 (signature capture) and the Ingenico iPP320 (no signature capture). Both hardware devices support Swipe, Key Entry, Debit, EMV and NFC capabilities like Apple Pay®, Google Wallet® and others. Integration supports tokenization for autopays. Retailers in Canada can use the OpenEdge solution.
EMV Flyer
Get Ready for EMV
  
TSYS Merchant Solutions

 Hardware TSYS Merchant Solutions is a new processing partner option introduced in v11. TSYS Merchant Solutions is a hardware based system with the exception that autopays can be run on a computer that does not have a hardware device. All non-autopay transactions must be run on a computer that has a hardware device. The hardware device is PAX s300 (signature capture) which supports Swipe, Key Entry, Debit, EMV and NFC capabilities like Apple Pay®, Google Wallet® and others. You can also use the ID Tech SecureKey M130 Keypad with MagStripe device on back office and remote computers to take swipe or keyed transactions. Integration supports tokenization for autopays.
Signup		  
Vantiv Integrated Payments Hardware All transactions must be done on a terminal that has a hardware device. Existing credit card hardware will no longer work. The new hardware device is Verifone VX 805 (no signature capture) which supports Swipe, Key Entry, Debit, EMV and NFC capabilities like Apple Pay®, Google Wallet® and others. Integration supports tokenization for autopays. Autopay transactions must be run on a computer with a hardware device.
Hardware Promo
Special Offer
Signup
  
Sterling Unknown At this time Sterling does not have an out of scope solution that is EMV ready. Integration does not support tokenization for autopays.  
XCharge Legacy
 Existing hardware should continue to work. We have been informed that Xcharge customers will be moved to the OpenEdge Host Pay solution at some point in the future. Integration does not support tokenization for autopays.  
VeriFone PCCharge Hardware As of May 1 2015 PCCharge can no longer be ordered.

 

 

 

Active-e Shopping Cart 

1.0   
 If you use C2B for Online Rentals, Payments, Lessons, Service Tickets, or Tee Times etc. you MUST complete this section.

If you use an active-e shopping cart and process the credit cards in AIM you MUST complete this section.

If you use an active-e shopping cart and process the cards with one of the cart supported gateways and you do not use C2B you can skip this section. 

If you do not have an active-e shopping cart you can skip this section.
2.0   
 Before proceeding, you must be on the latest version of the Storefront Shopping Cart. Contact sales to schedule a consultation. You can find out more about the Active-e Shopping Cart Upgrade process and latest version here. http://activee.vortx.com/
3.0  Make sure you are on the latest update of AIM.
 
4.0  Set up certain App Config entries on your shopping cart, depending on your credit card provider. Note that to use the shopping cart and C2B you must have an account with one of the following payment services:

OpenEdge - Follow these instructions during the initial upgrade.
1 Set aeCCType to L
2 Set aeCCMID to the merchant ID token provided by OpenEdge
3 After you save the App Config entries click the Refresh Store button at the top of the aesys page.

OpenEdge - Follow these instructions after OpenEdge has moved you to the EMV platform.
1 Set aeCCType to O
2 Set aeCCMID to the X Web ID provided by OpenEdge
3 Set aeCCDeviceID to the Terminal ID provided by OpenEdge
4 Set aeCCTransactionKey to your Auth Key provided by OpenEdge
5 After you save the App Config entries click the Refresh Store button at the top of the aesys page.

TSYS
1 Set aeCCType to T
2 Set aeCCMID to the merchant ID provided by TSYS
3 Set AeCCUserName to the appropriate TSYS User ID
4 Set AeCCPassword to the appropriate TSYS User Password.
5 Set AeCCDeviceID to the Device ID provided by TSYS
6 After you save the App Config entries click the Refresh Store button at the top of the aesys page.

Vantiv
1 Set aeCCType to M
2 Set aeCCMID to the merchant ID provided by Vantiv
3 Set aeCCLane to the appropriate Lane ID
4 Set AeCCPassword to the web services password provided by Vantiv
5 After you save the App Config entries click the Refresh Store button at the top of the aesys page.
5.0  If you use one of the carts integrated payment gateways, the credit card/token will no longer be brought into AIM. If you do not use one of the carts gateways, the credit card will be turned into a token during the carts checkout process and the token will be stored in AIM so that you can charge the card/token in AIM. Since the cart now creates the token during the checkout process, you will still get the credit card token into AIM even of the customer elects not to store the card in the shopping cart.
 

 

AIM v12

 If you are using integrated credit card processing in AIM

1.0   
 Open menu option Maintenance>Ledger >Credit Card Payment Categories.
2.0   
 Enter a ‘Credit Card Payment Default Desc’. This is what appears as the payment method to initiate an integrated card transaction. Since the hardware devices are consumer facing you will not know what card brand the customer is using until after they swipe/dip/tap their card. To initiate a card transaction you will select the description that you enter in ‘Credit Card Payment Desc’ as the payment method.
3.0 Enter the corresponding category number for each of the card brands that you accept. Do this for Payments, Returns and Auto Pays if applicable. Once a card transaction is complete the generic ‘Credit Card Payment Desc’ will be replaced with the appropriate category based on this setup screen. Click the Save button.
4.0 In previous versions of AIM you probably had two versions of each credit card payment method. You probably had one called Visa that initiated a credit card transaction. And you probably had another one called Previously Authorized Visa that you used if the transaction had already been approved by some other means or to record autopay transactions. During the upgrade the payment methods that were setup to initiate credit card transactions have been changed to ‘Regular Payment’ methods. So now you most likely have two ‘Regular Payment’ Visa payment methods. We do not recommend that you delete one of them since that will cause reports and history to no longer be associated with a payment method. We recommend that you run the Merge Payment Method program that can be found under menu option Maintenance>Ledger>Utilities. This program will merge two payment categories and remove the old one.
5.0 On the credit card tab of each workstation record in AIM select the appropriate POS and Auto/Web Pay Gateways.
6.0 Please train your staff to use the correct payment method to accept credit card payments. To help with this we have automatically setup system variable CreditCardPaymentCatWarning to give a warning if an employee selects a credit card payment category that does not initiate a credit card transaction. You can also set up security levels on these payment categories so that a manager has to override if an employee tries to select one.