Skip to main content

How to set up automatic pre-authorisations on bookings

Pre-authorisations block a security amount on the guest's card around check-in instead of charging it. Configure per sales term, choose fixed amount or percentage. AmenitizPay only, not on OTA virtual cards.

Overview

Pre-authorisations let you block an amount on a guest's credit card around check-in time as a security deposit — for example, against accidental damages or unpaid extras. The amount isn't charged: it's reserved on the card and released automatically if you don't capture it. You set up pre-authorisations per sales term, so different rate plans can have different rules.


Before you start

  • Pre-authorisations only work on cards processed through AmenitizPay. Bookings paid by bank transfer or logged offline are out of scope.

  • They can't be used on virtual credit cards issued by OTAs (Booking.com, Expedia, etc.) — only on real cards from your booking engine or direct charges.

  • A pre-auth is placed automatically on the guest's arrival date. It holds for up to 30 days, with a minimum of 7 days, subject to the card's compatibility with the feature. Once released, the amount can no longer be captured.

  • Pre-auths are configured per sales term — set them on every term where you want the safety net.


Step 1 — Open the sales term

  1. In the sidebar, go to Booking engineSales Terms.

  2. Click the sales term you want to add a pre-authorisation to. (Create one first if you don't have any.)


Step 2 — Enable and configure the pre-authorisation

  1. Find the Automated pre-authorisations section.

  2. Set Do you want to enable pre-authorisations? to Yes.

  3. Choose the Pre-authorisation type:

    • Fixed amount — a set amount (e.g. €150) regardless of booking total.

    • Percentage — a share of the booking total (e.g. 20%).

  4. Enter the Pre-authorisation amount.

  5. Click Save. Pre-auths will now fire automatically for every new booking on this sales term.

💡 Tip

All AmenitizPay transactions are encrypted and PCI-compliant, so the guest's card details stay protected during the hold.


FAQs

When is the hold placed on the guest's card?

Automatically on the guest's arrival date. Amenitiz attempts the hold on that day; if the card doesn't support pre-auth, you'll see a warning on the booking.


How long does the hold last?

Up to 30 days, with a minimum of 7 days. The exact duration depends on the card type and issuer. Once the hold is released, you can't capture the amount — you'd need a fresh charge.


How do I actually charge the pre-authorised amount if there's damage?

Capture it before the hold expires. Open the booking, find the pre-authorisation entry under AmenitizPay, and choose to capture the full or a partial amount. If you do nothing, the hold releases automatically.


Does this work for Booking.com / Airbnb / Expedia bookings?

Not for OTA bookings paid with a virtual credit card — those cards only carry the booking total and can't be pre-authorised. For OTA bookings paid by the guest's real card (rare), pre-auths apply normally.


A pre-authorisation didn't go through. Why?

Three common reasons: (1) the card doesn't support pre-auth (some prepaid or virtual cards), (2) the booking is an OTA reservation paid with a virtual card, or (3) the card has insufficient available balance. Check the AmenitizPay panel on the booking for the specific error.

Did this answer your question?