Payments for every guest experience, not just bookings.
Manage reservation prepayments and card holds, or create standalone payment requests from the dedicated Rezervem Pay mobile and web apps. Sell eligible Experience products, share links or QR codes, and use a supported merchant virtual POS.
A reservation's value is clear before the guest arrives.
When you plan a special evening, a limited menu or a large table, uncertainty is expensive.
- 01Will the guest actually show up?
- 02How and where will we take the payment?
- 03Which reservation does this payment belong to?
- 04When is a refund due, and to whom?
Rezervem Pay answers these questions in one place. Payment stops being a separate task and becomes part of preparing for service.
Turn a reservation from a promise into a commitment.
Not every reservation needs the same financial safeguard. Choose between charging a prepayment and temporarily placing a hold on a card for eligible busy periods, groups and special menus. Explain the amount and cancellation terms.
Set the right amount for each booking.
Define eligible deposit or prepayment amounts using rules based on day, meal period, area, party size or selected offering. The pricing engine is enabled per restaurant; applicable rules and legacy fallback are verified during setup.
One booking. Different cards. Shared responsibility.
For eligible group bookings, the total prepayment can be divided by seats so guests pay their share with separate cards. Track collected and outstanding shares; a partial payment is not a fully paid booking. This is an opt-in prepayment flow, not split card authorization or universal split checkout.
Standalone payments from the Pay mobile app and web dashboard.
Rezervem Pay has its own mobile app and web dashboard, separate from Manager. Create a request for an amount or eligible product, share its link or QR code, and track the actual payment result. A paid request can be associated with a booking later where supported; sending the link does not mean funds were collected.
Sell the experience, not just an amount.
Choose eligible products and variants from Rezervem Experience—such as a tasting menu, spa treatment or special service—and create a payment request with the product, quantity and price attached. Share the request by link or QR; payment and fulfilment are tracked separately.
Your virtual POS, with your existing bank relationship.
Rezervem Pay acts as a payment gateway, routing supported transactions to configured virtual POS connections. Use an eligible existing bank's POS or a supported platform option. Transaction types, currencies, refunds and fees depend on provider setup.
The payment gateway does not replace your bank agreement.
Post each payment to the right place at the register.
When the supported Oracle Simphony integration is enabled, an eligible payment received through Pay can be posted as a prepayment to the staff-selected open check. Safeguards help prevent duplicate posting; availability depends on the venue and check status.
Clear rules, without straining the relationship.
Explain cancellation and no-show terms before any payment. A no-show status is not proof that funds were captured. Review the provider's actual authorization, capture, cancellation or refund status.
See every payment with its status and source.
Review completed charges, pending requests, card holds and refunds separately. Read reservation-linked transactions alongside Manager and independent Pay requests by their own payment status.
Requested. Paid. Recorded.
With a reservation or on its own, every payment follows the same order.
Prepayments, card holds and your own merchant POS.
Understand the issue, choose a suitable payment method, and review the Manager + Pay workflow.
Your questions, answered.
Yes, with supported bank or payment-provider virtual POS integrations. Transaction support, currencies, refunds and fees depend on the restaurant's settings.
Yes. Payments are taken independently of reservations; send them by link, QR or WhatsApp, and link them to a reservation later if you choose.
Prepayment is charged before the visit; an authorization hold temporarily reserves funds but is not yet sales revenue. Capture and release depend on card and provider rules.
Yes. A payment taken with Pay is posted as a prepayment to the open Simphony check the staff selects. The integration is optional.
Yes. Rezervem Pay has a dedicated mobile application and web dashboard separate from Manager for creating requests, sharing payment links or QR codes, tracking results and eligible refunds.
The terms disclosed to guests and the provider's final transaction results determine whether a charge, release or refund is possible. Booking status alone is not proof of payment.
Yes. Pay supports independent payment requests by link, QR or WhatsApp. An independent request may be linked to a reservation later when needed.
Eligible restaurant-specific pricing rules can calculate an amount based on date, shift, time, area, guest count or transaction type. Setup and feature activation must be verified.
In eligible bookings with the split prepayment feature enabled, guests can pay their share separately. Partial payment is not the same as a fully funded booking; this does not imply split authorizations or all payment requests.
Eligible Experience catalog items and variants may be included in a payment request, with the order and payment statuses tracked separately.
The current physical POS provider catalog marks Pavo as coming soon. Confirm availability and integration scope for your venue before relying on a device workflow.
Pay guides.
Step-by-step guides about Pay.
Articles on Pay.
Recent articles about Pay.
Less uncertainty. More secure evenings.
Let's look together at how Rezervem Pay brings your payment processes together.