Connection Guide

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

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.

How do I obtain my 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.

To obtain the Transaction Key:

  1. Log into the Merchant Interface at
  2. Click Account from the main toolbar.
  3. Click Settings from the menu on the left.
  4. Click API Login ID and Transaction Key from the General Security Settings section.
  5. Under Create New Transaction Key, enter the answer to your Secret Question.
  6. When obtaining a new Transaction Key, you may choose to immediately disable the old Transaction Key by clicking on the box titled, Disable Old Transaction Key.
    • 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.
  7. Click Submit.

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.

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.

Other Settings:

1. AVS-  If you do not have billing address details set as a requirement for your Cloudbeds account, you will need to also disable AVS (billing address information) as a requirement inside of

Here's how to do that:

  1. Log into the Merchant Interface at
  2. Click Account from the main toolbar.
  3. Select Settings.
  4. Click Address Verification Service in the Security Settings section.
  5. Uncheck the box(es) next to the AVS codes for which the payment gateway should reject transactions.
  6. Click Submit.

2. Test Mode:

One of the great things about the Cloudbeds Payment Gateway Feature's design is that the testing process is pretty much the same no matter which payment processing provider you have. Take a look at this quick tutorial video here:

With that said, you'll want to make sure that the Test Mode in is turned OFF and the account is set to LIVE.

For security reasons, all new Authorize.Net accounts are in Test Mode. When an account is in Test Mode, transactions may be submitted that will not be authorized or charged to the account numbers provided in the transactions. When your account is in Test Mode, each page in the Merchant Interface will display an orange banner stating:

Your account is in TEST MODE - To update click here

Email receipts generated by Authorize.Net will also indicate whether they were submitted in Test Mode.

While in Test Mode, transactions will not be saved to the database or be viewable in search results or reports.

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

  1. Log into the Merchant Interface at
  2. Click Account from the main toolbar.
  3. Click Settings in the main menu on the left.
  4. Click Test Mode under the Security Settings section.
  5. 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.

3. 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.

Have more questions? Submit a Ticket


Powered by Zendesk