Custom Payment Gateway - Authorize.net

Xola can configure your account to process credit card payments using Authorize.net. However, the Xola team will need some items from you to get everything setup. Some information you should be aware of when choosing to configure Authorize.net:

Xola supports two types of Authorize.Net integration:

  • Advanced Integration Method (AIM): This is the most common gateway format and does not support saving of credit cards. Due to this you cannot collect payment at later date or disable auto-accept
  • Customer Information Manager (CIM): This is an additional free service provided by Authorize.Net that allows you to save credit card & billing information.

Xola highly recommends signing up for the CIM service.

Here are the steps that you'll need to take to integrate your Authorize.net account with your Xola account:

QUICK & DIRTY
    1. Send your API Login ID and Transaction Key to us in a password protected document.

      An API Login ID & Transaction Key is required to connect Xola with your Authorize.Net gateway. These details are only used to connect Xola to the Authorize.Net Payment Gateway for transaction processing. To locate these items in your Authorize.net account:

      • Log into the Merchant Interface at https://account.authorize.net/ -- or, if logged in already, click the Home tab near the top of your screen.
      • Click Settings under Account in the main menu on the left.
      • Click API Login ID and Transaction Key in the Security Settings section.
      • Your API Login ID is displayed on the page if one has been generated already. If not, enter the Secret Answer to the Secret Question for your user account. The API Login ID and the Transaction Key (see below) will then be generated.

      Need more help? Learn what an API Login Id / Transaction Key is, and how to create on in Authorize with this link, or find out more information with this help center section.

      Important: Never send the API Login ID and Transaction Key via plain text in an email. Alway make sure to send this sort of financial information in a password protected document, and then the document's password in an additional email. Your security is our priority.

    2. Disable AVS.

      The Address Verification Service (AVS) is a standard credit card verification feature supported by Authorize.Net that compares the billing address provided by a traveler for a credit card transaction with the billing address on file for the cardholder at the credit card issuing bank. This feature is enabled by default on all accounts.

      Xola recommends that you disable the Address Verification Service within your Authorize.Net account.

      To disable AVS:

        • Click Settings under Account in the main menu on the left.
        • Click Address Verification Service under Security Settings.
        • Under "General AVS Responses" uncheck all checkboxes under "Reject".
        • Under "Address and ZIP Code Responses" uncheck all checkboxes under "Reject".

       

      If you have the Authorize.net Fraud Detection suite, then you will have the Enhanced Address Verification Service (AVS) Handling Filter. If so you should follow these steps:

      • Under "General AVS Responses" click the radio boxes under "Allow" for all options.
      • Under "Address and ZIP Code Responses" click the radio boxes under "Allow" for all options.
      • At the top of the page if you have a "Enable filter" checkbox, uncheck it.

       

      Just to be doubly sure, all radio boxes under "Allow" should be checked and none under decline should be checked. Exactly as it is below.

    3. Why Disable AVS?

      There are four key reasons to disable the AVS filter:

      • To streamline the booking process, Xola does not collect billing information (street, city, state, zip code) for every credit card booking. Because this information is ommitted, if AVS is enabled, your credit card processor may reject bookings and you may see a high rate of card declines. This is likely to happen if your Xola booking workflow requires you to collect credit card details upon booking creation and charge the card at a later date.
      • If you use a USB or mobile swipe device, Xola will send the data on the magnetic strip of the credit card to Authorize.net. These transactions will count as a "Card Present" transaction. To view benefits of card present transactions you should read this article from Authorize.net.
      • Authorize.Net's default AVS settings also prevents you from accepting cards issued by banks from outside of the US and those banks that do not support AVS. Disabling the filter will allow you to accept these international credit cards too.
      • Visa, MasterCard, Discover Gift cards often don't have an address associated with them (especially if the user hasn't registered their gift cards first). So if your customer uses one of these gift cards they will get blocked by the AVS service. Turning off AVS will allow you to accept gift cards as well.

Useful reference:



Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments