Last Updated: Mar 22, 2017

Transactional Apps like the Shop, Payments, Registraitons, and Donation apps require a Merchant processor to be set-up in order for you to process credit card transactions. This article outlines the set-up for using the Authorize.net CIM Merchant option. CIM stands for Customer Information Manager. The CIM API allows us to save users and create payment profiles in Authorize.net which can be referenced for future transactions. This allows us to use the security code on the initial transaction to enforce proper transaction security, and then reference a payemnt profile within Authorize.net for future transactions.

To use Authorize.net CIM, you will need an Authorize.net account connected to a merchant provider. It is important to note that not all merchant providers will work correctly with the CIM API which allows your site to process recurring donations. For instance, we know that Intuit merchant accounts are not compatible with CIM because they require the security code to be passed to them all the time.

If you are looking for a merchant provider, or want to save some money on your credit card processing, we can connect you with merchant providers that we know work with our system or Authorize.net and offer some of the best rates available to non-profits. Contact us for more informaiton.

Authorize.net CIM Set-up

1. Sign-up for the Customer Information Manager (CIM).
   The CIM is not available by default within Authorize.net. 
2. Turn Card Code Required off on the Payment Form settings
   • Go to Account > Payment Form > Form Fields
   • Make sure that Card Code is NOT checked and click the Save button
     
      
3. Obtain your Transaction Key
   • Go to Account > API Login ID and Transaction Key
   • If you already have generated a Key, you can use that one. You should have saved the key and the Login ID will be displayed
   • If you need to generate a new key:
     • You will need to know the Secret Answer to the Secret Question
     • If you do not know this information, you will need to contact Authorize.Net, InfiPlex will not be able to assist you with this.
     • A new Key is generated by Authorize.Net when you click Submit. There is an option to “Disable Old Transaction Key”, but we advise that you DO NOT Disable the Old Transaction Key. Any system using the OLD key will need to be updated within 24 hours.
     • Clicking Submit will reveal the new Transaction Key. Copy the Transaction Key and save it somewhere safe.
4. Password-Required Mode
   • The Password-Required mode is also located under the Security Settings area on the Settings page. It must be enabled for ALL Transactions.
5. Set the Direct Response
   • On the Settings page under Transaction Format Settings, look for the Direct Response link”. Make sure that Delimited Response is set to YES and the Default Field Separator is set to comma (,).
6. Test Mode
   • New accounts will be initially set-up in test mode. Transactions that are submitted while Test Mod is ON are NOT actually processed. You will need to Turn Test Mode OFF when you are ready to go live with your website/merchant account.
7. Log into your InfiPlex website
   and go to the Admin Tools(wrench icon) > System Merchant Settings area.
   • Select the Authorize.net CIM merchant option
   • Enter your API Login ID into the Merchant ID field
   • Enter your Transaction Key into the Merchant Key field
   • Click SAVE to save the settings
     
      
   • REQUIRED STEP: You will then go to the specific Apps that need to have the System Merchant installed. Each App, like the Shop or Donation application, have a Settings > Merchant settings area where you will be able to change the default setting of "none" to "System Merchant".

Testing

Once you have everything set-up you can make a purchase or a donation to make sure that everything works correctly. You will see the final thank you page, receive your confirmation email, and be able to view the transaction in the App's transaction report on both your website and Authorize.net.