Guest-Facing Notification for Security Deposit Re-Authorization (requested internally 11+ years ago, still not built)

When a security deposit hold re-authorizes mid-stay or near release (because the guest's card issuer's hold window expires before OwnerRez's configured Released date), the account owner gets an automatic email notification — but the guest gets nothing. The guest has no idea a new authorization just hit their card, and the predictable result is a confused, frustrated guest reaching out asking why they've been "charged again," even though nothing about their reservation has changed.

This isn't a new observation. In the thread "Email notification when security deposit reauthorization fails" from 11 years ago, OwnerRez staff (Michelle J) acknowledged the gap directly: "We can't guarantee that reauthorizations will always work for this reason. I know that's frustrating. We've looked into different alternatives in the past but always come up short. We are considering adding an email notification that wi—" (reply cuts off there). That was 2015. It's 2026, and there is still no guest-facing notification for re-authorization — success or failure.

The request, in order of preference:

1. Automatically send guests a parallel notification whenever the account owner is notified of a re-authorization — no extra setup required. If the system already knows the event happened (it clearly does, since it emails the owner), the guest should be told too, framed appropriately (e.g., "this is a routine hold refresh, not a new charge").
2. At minimum, expose "Security Deposit Re-authorized" as a selectable status/event in the Triggers system, so hosts and PMs can build our own guest-facing message for it manually. This is a fallback, not a replacement for #1 — individual accounts shouldn't have to remember to configure this correctly for guests to be protected from confusion.

This becomes a bigger problem the more hosts scale into longer average stays and larger portfolios — the total span between hold placement and release grows, which increases the odds of hitting a re-auth. If you manage multiple properties or see more 7+ night stays, you've probably already run into this.

If you've dealt with this too, an upvote here helps get it prioritized.

Hi Corey,

Thanks for sharing this idea with the community! Feature requests with more support tend to move up our list faster, so if there's anyone else who'd want this too, point them to this thread and encourage an upvote.

I understand the arguments for and against publicizing the renewal of security deposit holds that have expired. On the one hand, you are drawing unnecessary attention to a transaction that most guests don't notice. On the other, you explain what is happening to the ones who do notice. Hopefully, the forum community can weigh in and give us an idea of which side to lean towards. 

However, I must highlight one correction. Failed re-authorizations do already result in a notification to the guest - along with a demand for a new card.

Thanks!

[Another topic was closed as a duplicate of this topic (Adding security deposit reauthorization event to the available trigger events)]