Sending a guest a payment link is simple, but matching that payment back to the right reservation reliably takes a routine, and this covers how to build one that doesn't rely on memory.
Payment links are a common way for small properties to collect a deposit or full payment without taking card details directly, but the reconciliation step — matching each payment back to the correct reservation — is where mistakes creep in if it's left informal. A guest paying and a reservation being marked paid should be the same event, not two records that drift apart.
A payment link is generated, sent to the guest, and paid — but unless that payment is immediately matched back to the specific reservation it belongs to, the two records live in separate places: your payment provider's dashboard and your PMS. For one or two bookings a day, a person can hold that mapping in their head. At any real volume, it becomes a place where a payment gets logged against the wrong reservation, or a reservation sits unmarked despite being paid.
The risk isn't usually a lost payment — providers keep their own records — it's a reservation showing as unpaid when it isn't, which can affect how it's treated at check-in or in a cancellation policy.
Every payment link sent should carry a clear reference to the reservation it's for, ideally the reservation ID itself, rather than just a guest name that could match more than one booking. The person generating the link and the person confirming it was paid should be checking the same reference, not relying on recognizing the guest's name or the amount alone.
Generate payment links from inside the reservation itself where possible, so the reference travels with it automatically rather than being typed in separately each time. Reconcile at a fixed point each day — end of shift is usually practical — rather than whenever someone remembers, and check the payment provider's list against reservations marked paid in your PMS for that same window.
Activity history records who marked a reservation as paid and when, across 39 action types kept for 400 days, which turns reconciliation from a trust exercise into something you can actually check back on if a status looks wrong. Staff permissions let you limit who can mark a reservation as paid at all, so the responsibility sits with a specific role rather than whoever is at the desk. You can see how reservation status and payment tracking work together on the public demo at try.primehostpartners.com without signing up.