Hotel card deposits: authorisation, capture and release
Card deposits in Austrian hotels: distinguish authorisation, capture, release and refunds, then test the payment workflow and reception handover.
- Bahram Davoodi

A card hold for a hotel deposit is not yet a final charge. Pre-authorisation reserves an amount; only subsequent capture turns it into a payment. If nothing is captured, the issue is cancellation or release of the hold. A refund, by contrast, concerns money already charged. Hotels in Austria should explain this distinction clearly before arrival.
Four operations with different consequences
Operation | Meaning for the hotel | What to tell the guest |
|---|---|---|
Pre-authorisation | An amount is reserved | No final payment yet |
Adjustment | The reserved amount changes, where supported | Explain the new hold amount |
Capture | All or part of the authorised amount is charged | State the amount actually charged |
Cancellation or refund | Cancel an unused hold or return a payment | Explicitly distinguish these operations |
Technical requirements depend on the payment provider, card scheme, issuer and actual integration. Pre-authorisation documentation describes these limitations and differing validity periods. Acceptance of a card therefore does not automatically imply support for every deposit function. This provider source also establishes no particular integration with Lonio.
Example: €300 reserved, €240 paid
A fictional hotel reserves €300 on a guest's card for an agreed purpose. At checkout, €240 is actually payable. If the configured workflow supports the appropriate adjustment and capture, €240 is charged and the unused hold is cancelled or released.
The remaining €60 is not a refund if it was never captured. A hold may nevertheless remain visible temporarily on the guest's statement. Do not promise release within a fixed number of hours. Processing by the provider and bank affects when the amount appears available again.
If €300 was instead charged first and €60 subsequently returned, the payment history is different. The documents must reflect that difference. Both cases may produce a net €240, but they do not use the same operation. Refund documentation likewise distinguishes returning captured funds from cancelling an uncaptured payment.
Test before the first live use
Check at least these points with the payment provider and your configuration:
- Which cards and terminals support the intended deposit workflow?
- How long is authorisation valid, and what happens during longer stays?
- Can amounts be increased, reduced and partially captured?
- How are successful, rejected and pending operations displayed?
- Which reference connects the hold, charge, invoice and stay?
- Who may capture or cancel, and who checks the result?
Sending a request is not confirmation of success. If the status is unclear, check the existing operation before charging again. This prevents duplicate payments. Retain only payment references needed for the process; card details do not belong in freely accessible booking notes.
Explain the process at reception
State the purpose, amount and planned settlement point. “We will reserve €300; final settlement follows confirmation of your charges” is clearer than “We will debit the deposit” if you are only authorising it.
If the guest ultimately pays another way, cancel the original hold through the intended procedure. For alleged damage or later extras, the technical ability to charge a card does not replace checking contractual entitlement. Verify the service, documentation and consent before collecting an amount.
Connect booking, invoice and payment
Lonio offers reservations, digital invoices and accounting as connected business areas. Availability of pre-authorisation, adjustment and release in your specific payment connection requires separate confirmation and testing. General card acceptance does not prove this capability.
Define how open holds are handed over between shifts. At day-end, completed stays should not retain an unresolved deposit status. A list containing booking number, payment reference, amount, status and responsible person is more useful than simply noting “card on file”.
Frequently asked questions
Is a card hold already revenue?
It is not initially a final payment. Assess the tax treatment of the underlying service separately.
Can every credit card support a deposit hold?
No universal promise is possible. The card, provider, merchant configuration and specific function must work together.
When will the guest see the release?
This depends on provider and bank processing. Confirm the operation you completed and its reference without promising an unsupported fixed deadline.


