The deposit desk

Damage protection, without the booking friction.

Pick one for each property: a small one-time waiver fee, or a refundable hold on the guest's card. Both include background screening before arrival, and the guest finishes it in the app with their other check-in steps.

Try the AI Book a walkthrough

From the booking to the damage

Two ways to protect a property against guest damage, and you pick one for each. Scroll to follow a stay: the choice, how the waiver and the hold each work, the screening that comes with both, what you do if something is damaged, and how the guest finishes it in the app.

Step 1 of 6 · Choose

Two ways to protect a property, and you pick one for each

A damage waiver charges the guest a small one-time fee. A deposit hold places a refundable authorization on their card. You choose one per property, so different properties can take different approaches.

What's on screen

The damage waiver
The deposit hold
One choice per property

Under the hood

Both paths include background screening, and both finish inside the guest app with the other check-in steps.

Step 2 of 6 · Waiver

A small fee instead of a large sum frozen on the card

With a waiver, the guest pays a one-time fee and nothing is frozen on their card. There is much less friction at booking, guests complete it more often than a deposit, and the property is still protected.

What's on screen

A one-time fee at checkout
No large sum frozen
Less friction at booking

Under the hood

Claims on a waiver go through the waiver provider. Linkbase does not manage them.

Step 3 of 6 · Hold

The money is held, not taken, and only when the stay is close

A deposit hold is an authorization, never a charge. It is placed automatically close to the stay, so the guest's credit is not tied up for months. A small card-validation charge at booking confirms the card is real.

What's on screen

A card checked at booking
A hold placed close to the stay
Held, not charged

Under the hood

Because the card is checked up front, a dead card surfaces at booking instead of the night before check-in. The deposit itself never moves unless you act.

Step 4 of 6 · Screening

Screening comes with both, and goes deeper for longer stays

Both paths register the guest and the reservation for background screening before arrival. Short stays get waiver-level screening, and longer stays get the fuller screen-and-protect tier, since extended stays carry more exposure. You get a clear signal, not raw data.

What's on screen

A guest registered before arrival
Depth that scales with the stay
Approved, flagged or rejected

Under the hood

This is background screening. Government ID verification and signed documents are separate requirements, described under Screening & forms.

Step 5 of 6 · Capture

If something is damaged, you capture the hold

On the hold path, you capture the authorization from your dashboard, all of it or just part. There is no paperwork and no third party to wait on. If nothing is claimed, the hold is released automatically when it expires.

What's on screen

A hold waiting on your decision
Capture all, or just part
Released if nothing is claimed

Under the hood

Money only moves when you act. Waiver claims are handled by the provider, not inside Linkbase.

Step 6 of 6 · Guest app

One more step in the guest app, with no emails to chase

The guest completes the waiver or the hold in the guest app, alongside their other check-in steps. Until it is done, they stay on the steps page instead of their stay details.

What's on screen

Check-in steps in one place
The guest paying or authorizing
Stay details opening once done

Under the hood

One flow in one place, so there is no separate email or link to chase.

Step 1 of 6 · Choose

Two ways to protect a property, and you pick one for each

What's on screen

The damage waiver
The deposit hold
One choice per property

Under the hood

Both paths include background screening, and both finish inside the guest app with the other check-in steps.

What it handles

Each of these used to be a task on someone's list. Here's what runs it now.

Large deposits that scare off bookings
Protection
A small one-time waiver fee instead of a frozen sum.
Holds placed months too early
Protection
The authorization is placed automatically, close to the stay.
A dead card the night before
Protection
A small card-validation charge at booking surfaces it early.
Guests nobody looked at
Protection
Background screening before arrival, deeper for longer stays.
Recovering after damage
Protection
Capture all or part of the hold from your dashboard.
Chasing guests to complete it
Protection
A step in the guest app, with stay details held back until it is done.

Under the hood

How it actually works

1
You pick one for each property
Choose a damage waiver or a deposit hold per property. Both register the guest and the reservation for background screening before arrival.
2
The guest finishes it in the app
It sits alongside the other check-in steps. Until it is done, the guest stays on the steps page instead of their stay details.
3
A hold is an authorization, not a charge
On the hold path the money is held on the guest's card and never moved unless you act. It is placed close to the stay, and released automatically when the hold expires if nothing is claimed.
4
Screening scales with the stay
Short stays get waiver-level screening and longer stays get the fuller tier. You see a clear approved, flagged or rejected signal, not raw data.

Connects to

Works with what you run

Your existing tools stay where they are. Linkbase connects to them instead of asking you to move.

See every integration →

Guest portal
Your PMS

The jobs next to this one

Screening & formsID checks, agreements and forms, trackedRead more→Guest appOne branded guest link for their whole stayRead more→

See it on a real conversation

The live demo runs the same AI on a sample booking. Ask it what your guests ask you.

Try the AI Book a walkthrough

Damage protection, without the booking friction.

From the booking to the damage

Two ways to protect a property, and you pick one for each

What it handles

Large deposits that scare off bookings

Holds placed months too early

A dead card the night before

Guests nobody looked at

Recovering after damage

Chasing guests to complete it

How it actually works

You pick one for each property

The guest finishes it in the app

A hold is an authorization, not a charge

Screening scales with the stay

Works with what you run

The jobs next to this one

See it on a real conversation