Connection Guide

Follow is one of the many payment processing providers we connect with through our Payment Gateway Feature. 

Step 1. Sign up for Authorize.Net account (if you do not have one)

If you do not have an account already, you will need to sign up for one. Since signing up with a Payment Gateway involves financial details and contract negotiations, we cannot legally create an account for you.  If you already have Authorize.Net account - go to step 2.

In order to register Authorize.Net account go to, and click 'Sign up'. Follow the instruction provided by gateway

Step 2. Obtain API Login ID and Transaction Key

To connect account, you will need both your API Login and Transaction Key. This is not the normal credentials you use to login to your account, but the credentials for connecting the two systems together through the API.

Here are the instructions for finding the API login and transaction key from They are included below, but can also be found here.

  1. Log into the Merchant Interface at Click Account from the main toolbar.
  2. Click Settings from the menu on the left.
  3. Click API Credentials and Key from the Security Settings section.

4. On this page you will find your API Login ID
5. In order to obtain Transaction Key - under Create New Transaction Key, enter the answer to your Secret Question, click Obtain: 'New Transaction Key', and click Submit

NOTE: 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.
Step 3. Connect Authorize.Net in myfrontdesk

In order to connect Authorize.Net to myfrontdesk you need to have payment processing functionality enabled (extra paid feature). Please contact us at to receive more information and request enabling payment processing functionality.

1. Login to myfrontdesk and go to Payment Options page
2. Scroll down to 'Connect Payment Gateway' section and activate the option
3. Select Authorize.Net as your gateway
4. Enter your Authorize.Net API Login
5. Enter your Authorize.Net Transaction Key (this is not your email)
6. Click 'Connect Gateway'

Step 4. Specific Authorize.Net settings
1) Turn off Test Mode in Authorize.Net

In order to start processing real charges in myfrontdesk through Authorize.Net, you'll want to make sure that the Test Mode in is turned OFF and the account is set to LIVE. To take your account out of Test Mode, please follow these steps:

  1. Log into the Merchant Interface at Click Account from the main toolbar.
  2. Click Settings in the main menu on the left.
  3. Click Test Mode under the Security Settings section.
  4. Drag the toggle to Live. The interface will confirm that the Test Mode settings have been successfully applied and the account is now in Live Mode.
2) Recommended setup of Fraud Detection Suite (disabling AVS Settings)

We recommend to disable AVS/certain Fraud Detection rules which allows to process the credit cards through myfrontdesk 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 myfrontdesk, which means that you won't be able to process them through myfrontdesk unless billing address is entered manually.

See instructions below to disable AVS in Authorize.Net:

1. Log into the Merchant Interface at > Click Tools >Select Fraud Detection Suite > go to Setup Wizard


2. 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:

3) What should I do if I want to have AVS enabled on Authorize.Net?

If you want to use AVS (address verification system inside gateway) - gateway will require that the credit card which needs to be charged includes all the needed billing address fields.


1) for future direct bookings/mybookings you can make billing address mandatory: guests booking through mybookings will have to fill in their billing address;

2)  for OTA reservations: myfrontdesk can't control whether your guests booking through OTA will send their billing address with credit card details. Sometimes making billing address required field on OTA can be controlled on Extranet but as a rule OTAs do not  billing address to myfrontdesk and do not collect this data, only the main credit card info (cardholder name, card number, card type, CVV).

If you have AVS enabled but the credit card will be imported from the channel without billing address - you won't be able to charge the card through myfrontdesk.

For reservations which do not have billing address entered or were imported without billing address - you will need to edit credit card inside myfrontdesk entering billing address manually;

As a solution you may disable AVS in Authorize.Net to process the credit cards without billing address (see section above)

How Processes Refunds does not allow refunding a transaction on the same day that it was charged. Further explanation below from's knowledge base:

Around midnight, takes all of the transactions that occurred during that day and submits them to the bank for settlement. After this process, the transaction is considered "settled," and only once a transaction has been settled can you issue a refund/credit.

This is an policy and is not something that can be changed from within the Cloudbeds platform.


Error Message - transactionKey' element is invalid

Problem: the transaction failed due to error message: transactionKey' element is invalid - The value XXXXX is invalid according to its datatype 'String' - The actual length is greater than the MaxLength value

8CSpTH2n1SymcxFMB1roYlkz0 (857×448) - Google Chrome

It usually happens when you have an email entered instead of the actual transaction key.

Solution:  follow the above connection guide fully to get the transaction key / credentials requires

Error Message: Transactions of this market type cannot be processed on this system
Slack | kb_requests | Cloudbeds | 84 new items

Problem: This error occurs when the market type is incorrect on side (for example when the market place was set up as Lodging/Retail as shown below)

For further information please check this article from support center.

Gian Zuliani's Personal Meeting Room - Zoom - Google Chrome

Solution: Please contact support team to set up your 'Market Type' correctly. You will need to ensure that your account is set up as e-commerce.


Can I connect one Account to several Cloudbeds properties?

Yes, you can connect one account to various Cloudbeds Properties using the same API Login and Transaction Key

Have more questions? Contact Support


Powered by Zendesk