Authorize.net - Connection Guide

Authorize.net is one of the processing providers we connect with through our Payment Gateway feature. This guide will walk you through the process connecting Authorize.net to your Cloudbeds PMS.

3D Secure 2.0 is NOT supported by Cloudbeds for Authorize.net. 3D Secure 2.0 is part of the Strong Customer Authentication (SCA) that is required within the European Economic Area (EEA) and the United Kingdom.

Sign up

If you don't have an Authorize.net account yet, sign up for one: https://www.authorize.net/

If you already have Authorize.Net account, proceed to the next step.

Payment Processing: Accept Payments Anywhere | Authorize.Net - Google Chrome
Obtain API login ID and transaction key

You will need both your Authorize.net API Login and Transaction Key. This is not the credentials you use to login to your account, but the credentials for connecting the gateway to Cloudbeds PMS through the API. Check out Authorize.net article here or follow the instructions below.

Follow the instructions below to find the Authorize.net API login and transaction key from Authorize.net.

  1. Log into the Merchant Interface at https://account.authorize.net. Click Account from the main toolbar.
  2. Click Settings from the menu on the left.
  3. Click API Credentials and Key under Security Settings section.
  1. On this page you will find your API Login ID.
  2. In order to obtain Transaction Key — under Create New Transaction Key, enter the answer to your Secret Question and click Obtain: New Transaction Key.
  3. Click Submit.

Authorize.net only displays a given Transaction Key when it is first generated. If you generate a new Transaction Key, any software or code using the previous Transaction Key will need to be updated with the new Transaction Key to avoid errors.

Transaction key notes:

  • If the Disable Old Transaction Key box is not checked, the old Transaction Key will automatically expire in 24 hours.
  • When the box is checked, the old Transaction Key will expire immediately. If you have current software installations, do not check this box unless you need to immediately cease all payment processing through your software setup. By not checking the box, the old Transaction Key would remain valid for 24 hours, giving you time to update your software to use the new Transaction Key.
  • Be sure to store the Transaction Key in a very safe place. Once it has been generated, it will not be viewable again. Do not share it with anyone, as it is used to protect your transactions.
  • For Server Integration Method (SIM), the Transaction Key is also used to create a unique transaction fingerprint. Using the Transaction Key and a few pieces of information specific to the transaction, a script on the merchant's Web server uses a complex mathematical algorithm to generate a document fingerprint. This fingerprint is submitted along with the transaction information to the gateway.
  • Before accepting the transaction, the gateway will use the Transaction Key and the transaction's data to recreate the unique transaction fingerprint. If the fingerprint generated by the gateway matches the fingerprint submitted with the transaction by the merchant, the transaction is accepted for authorization. If the fingerprints do not match, the origin of the transaction cannot be authenticated, and the transaction is rejected.
  • For other APIs such as the Advanced Integration Method (AIM), Card Present (CP), Automated Recurring Billing (ARB) and Customer Information Manager (CIM), the Transaction Key is encrypted along with all other transaction data when it is sent to Authorize.Net, and is directly used to authenticate requests submitted to the gateway. If a request cannot be authenticated using the Transaction Key , the request is rejected.
  • You may generate a new Transaction Key as often as you wish.
Connect Authorize.Net to Cloudbeds PMS

With the credentials in hand, enable the payment gateway inside Cloudbeds PMS. Follow the step-by-step here: Payment Processing Setup

Specific Authorize.Net settings

1. Turn off Test Mode in Authorize.Net

To start processing real charges on Cloudbeds PMS through Authorize.Net, you need to make sure that the Test Mode in Authorize.net is turned OFF and the account is set to LIVE.

To take your account out of Test Mode, follow these steps:

  1. Log into the Merchant Interface at https://account.authorize.net. Click Account from the main toolbar.
  2. Click Settings.
  3. Click Test Mode under the Security Settings section.
  4. Drag the toggle to Live.

The interface will confirm that the Test Mode setting has been successfully turned off and the account is now in Live Mode.

2. Recommended Setup of Fraud Detection Suite (Disabling AVS Settings)

We recommend disabling AVS/certain Fraud Detection rules to allow processing the credit cards through Cloudbeds PMS even if they have no billing address filled in.

This is recommended as most of the channels/OTAs do not send credit card details with billing address to Cloudbeds PMS, which means that you will not be able to process them through Cloudbeds PMS unless billing address is entered manually.

See below how to disable AVS in Authorize.Net:

  1. Log into the Merchant Interface and click Tools.
  2. Select Fraud Detection Suite.
  3. Go to Setup Wizard.

 

  1. Once you are in Setup Wizard, you will be asked to setup specific fraud detection settings. The screenshots below show the recommended settings for each option:
What should I do if I want to have the AVS enabled on Authorize.Net?

If you want to use AVS (Address Verification System) inside the gateway, the gateway will require that the credit card which needs to be charged includes all the needed billing address fields.

SOLUTIONS:

  1. For future direct bookings (Email, Phone, Walk-in, Cloudbeds Booking Engine), you can make billing address mandatory: guests booking directly will have to fill in their billing address;
  1. For OTA reservations: Cloudbeds PMS can't control whether your guests who book through OTA will send their billing address with credit card details.
    • You might be able to make the billing address as a required field on the OTA Extranet, but as a rule, OTAs do not send billing address to Cloudbeds PMS — and the PMS does not collect this data, only the main credit card info (cardholder name, card number, card type, CVV).

When the AVS is enabled, you won't be able to charge the card through Cloudbeds PMS if the credit card is imported from the channel without the billing address.

For reservations which do not have billing address entered or were imported without billing address, you must edit the credit card inside Cloudbeds PMS and enter the billing address manually

Was this article helpful?
1 out of 2 found this helpful

Comments

0 comments

Please sign in to leave a comment.