Why some cards can’t be saved using the Cloudbeds Payments terminal

In some cases, a guest’s card cannot be saved when it is tapped or inserted on the Cloudbeds Payments terminal, even though the same card can be saved when entered manually in the system.

This behavior is expected and is driven by bank and card security requirements.

Why this happens

• Card networks and banks apply different rules depending on how a card is captured.
• When a card is typed into Cloudbeds, it is treated as an online card entry.
  Many banks allow cards to be saved this way without requiring a payment.
• When a card is used on the terminal, it is treated as an in-person transaction.
  Some banks require a payment or verification before allowing the card to be stored.
• Because in-person rules are stricter, the Cloudbeds Payments terminal may block attempts to save a card without a payment.

Why the same card can work one way but not the other

Even though it is the same card, banks apply different security rules for online entry versus in-person terminal use.

As a result:

• A card may save successfully when entered manually
• The same card may not save when tapped or inserted on the Cloudbeds Payments terminal

This is a bank-level security requirement, not a system error.

Cards most commonly affected

• Debit cards
• Prepaid cards
• Some European-issued cards
• Cards with stricter issuer security policies

Credit cards are more likely to work, but success is not guaranteed.

What works best

To successfully save a card:

• Save the card as part of an actual payment on the Cloudbeds Payments terminal, or
• Enter the card manually in the system when appropriate

Both options allow the bank to approve the card before it is stored.

Explanation for your guests

Some banks don’t allow cards to be saved unless there’s a payment or verification first.
That’s why this card couldn’t be saved on the terminal today.
We can save it during your next payment, or enter it another way if needed.