Cloudbeds Payments - Error messages

There could be a few errors while migrating from one payment processor to Cloudbeds Payments. Check the article below for more information on the possible errors and the ways to solve them.
If you transaction was decline refer to this article: Decline Codes.

Errors: "Gateway Not Supported" and "Token Not Found"

The errors Gateway Not Supported and Token Not Found can both be seen when processing a payment from guest's credit card or when viewing the Payment Processing Report

One of these errors may occur because the system has not yet recognized that Cloudbeds Payments is enabled.

How to fix the error

Log out of myfrontdesk and log back in on all computers where Cloudbeds is being used. This will allow the system to refresh and recognize that Cloudbeds Payments is now enabled.

Once you are logged in,  you can try the payment again. If error continues to occur, please reach out to support@cloudbeds.com

Error "Default gateway is not configured"

This error can occur when the credit card details were received while being connected to another payment gateway, and now you are attempting to charge this credit card through Cloudbeds.

The error can be seen when processing a payment from guest's credit card or when viewing the Payment Processing Report

How to fix it

There are 2 options:

  1. Enable your previous payment gateway account to still take Payments so that all reservations (including this one), that have the credit cards tokenized through Stripe, can be processed by them;
  2. Delete the credit card details and then insert those again so that the system can charge the credit cards using the Cloudbeds Payments' gateway.
Was this article helpful?
0 out of 1 found this helpful

Comments

0 comments

Please sign in to leave a comment.