REZERVEM PAY · STANDALONE PAYMENT MANAGEMENT
Pay

Keep your virtual POS. Manage payments on mobile.

Use an eligible existing merchant virtual POS with Rezervem Pay. Create standalone links and QR requests from the dedicated business mobile app or web dashboard, and manage reservation prepayments, card holds and eligible Experience product collections.

WHO IT'S FOR Restaurants Hotels Spa and Experiences
Reduce the cost of empty tables On high-demand days, secure reservations with a pre-payment or pre-authorization.
Payments don't have to wait for a reservation A group dinner, a down payment or a private event: the payment is taken on its own.
Start without changing banks Connect your own virtual POS or use Rezervem's infrastructure.

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.

  1. 01Will the guest actually show up?
  2. 02How and where will we take the payment?
  3. 03Which reservation does this payment belong to?
  4. 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.

PRE-PAYMENT AND PRE-AUTHORIZATION

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.

Prepayment Collect the specified amount before the visit.
Authorization hold Temporarily reserve funds on the card, without creating a sale.
Selective rules Determine eligible dates, meal periods, party sizes and areas.
RULE-BASED PRICING

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.

Date and service Different eligible rules for peak and quiet services.
Party and area Per-guest, per-booking or area-based logic.
Clear amount Show the applicable charge and terms before payment.
SPLIT PREPAYMENTS

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.

Separate cards Each participant pays for their selected seats.
Real progress Follow collected and outstanding amounts.
Controlled completion Booking payment completes when its target is reached.
LINK, QR AND WHATSAPP

Create payment requests in the Pay mobile app or web dashboard.

Rezervem Pay has a separate business mobile app and web dashboard, independent of Manager. Authorised staff choose a venue, payer, amount or eligible Experience item, create a payment request and share its link or QR. Pending and paid requests are tracked, with edits, cancellations, refunds or booking links available when role and payment status permit. Guests pay through mobile web and do not install the business app.

Pay business mobile app Create requests and track payment results on the floor.
Link or QR Guests pay on their mobile web browser.
Web dashboard Manage venue and merchant POS setup.
Reservation link Associate eligible paid requests with bookings.
EXPERIENCE PRODUCT SALES

Select an Experience item; collect with Pay.

Rezervem Experience defines eligible tasting menus, cakes, spa services or add-ons with variants, prices and sale conditions. Staff can select an eligible item and quantity in Pay's business mobile app or web dashboard and issue a link or QR payment request. Order, confirmed collection, venue balance, fulfilment and redemption remain separate records.

Catalog items Product, variant, quantity and price stay identifiable.
Link or QR The guest opens a dedicated payment page.
After payment Check order status, voucher or fulfilment where applicable.
PAYMENT GATEWAY

Your virtual POS, with your existing bank relationship.

Rezervem Pay is gateway technology for routing eligible payments to configured bank or payment-provider virtual POS connections. Existing merchant accounts or supported platform options may be used. Merchant POS onboarding and approval happen through web setup, not the mobile app. Fees, currencies, refunds and settlement depend on provider agreements.

Your own POS Connect a supported bank or payment service provider.
Platform POS option Evaluate the configured payment option.
Payment records Track the selected POS and transaction result.
Physical terminals on the roadmap Pavo is currently marked coming soon in the physical POS provider catalog.

The payment gateway does not replace your bank agreement.

ORACLE SIMPHONY

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.

Posted to an open check Prepayment to the open check the staff selects.
No re-entry at the register The same payment is not entered twice.
Optional For venues that use Simphony.
CANCELLATIONS AND REFUNDS

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.

Transparent terms Cancellation rules are shown to the guest before payment.
No-Show charges Charge the pre-authorization for a no-show guest, according to your rules.
Refunds from the record Start the refund from the related reservation.
TRACKING AND REPORTING

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.

Payment status Paid, pending, failed.
Pay mobile and web Track standalone requests, payments and refunds.
End-of-day summary Collections, pre-authorizations and refunds together.
THE JOURNEY OF A PAYMENT

Requested. Paid. Recorded.

With a reservation or on its own, every payment follows the same order.

01 Request A reservation, standalone amount or eligible Experience item via link or QR.
02 Payment The guest pays on the same payment page, with their bank's verification.
03 Link If you choose, the payment is linked to a reservation.
04 Record Track payment in Pay mobile/web; associate it with a booking or eligible Simphony check if supported.
FREQUENTLY ASKED QUESTIONS

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. Authorised staff can create Pay requests, share links or QR codes, track results and manage permitted actions in the dedicated business mobile app. Guests pay in mobile web; merchant POS onboarding belongs to web setup.

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.

Yes, if the Experience item, venue, sales channel and provider are eligible. Create the item-backed request on Pay mobile or web; check order and collection 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.

GUIDES

Pay guides.

Step-by-step guides about Pay.

01Restaurant no-show prevention: an operations checklistUse confirmations, clear cancellation routes, arrival records and selective payment safeguards to reduce no-shows.MANAGER · GUIDE → 02How to plan restaurant tables and service capacityMap physical tables to the digital floor, set service durations and test the actual reservation capacity.MANAGER · GUIDE → 03How to set up a table plan for dinner servicePlan dinner service by section, table combinations and realistic seating durations; use the waitlist and review capacity after each service.RESTAURANT → 04How to set restaurant prepayment rules by day, meal, area and party sizePlan deposits or pre-authorizations around specific service conditions, then test the configured guest experience.MANAGER · GUIDE → 05Prepayment or card hold: what to use and whenUnderstand prepayments versus card pre-authorizations, which bookings may need them, and how to explain terms to guests.RESTAURANT → 06How to prepare a tasting-menu evening for salePlan tasting-menu choices, booking capacity, service preparation and payment as separate steps before inviting guests.RESTAURANT → 07How AI Concierge Books with Rezervem ManagerFollow a guest's phone or chat request from the first question to a verified reservation in Manager, including approval, payment and staff handover.AI CONCIERGE · RESTAURANT RESERVATIONS → 08How to manage prepayments, card holds and no-showsA practical guide to payment policy, guest communication, reservation status, prepayments, card holds and end-of-day reconciliation.REZERVEM MANAGER · PRACTICAL GUIDE → 09How to coordinate tasting menus, guest choices and table reservationsA practical restaurant guide to keeping tasting-menu orders, individual menu preferences, table capacity and payment records aligned before service.REZERVEM MANAGER & EXPERIENCE GUIDE → 10Hotel Folios, Deposits and Room Charges: A Reconciliation GuideUnderstand how room charges, deposits, payments and external POS checks appear in a hotel folio without double counting sales.HOTEL → 11Oracle Simphony Cloud Integration: Go-Live ChecklistA practical checklist for STSG2 access, revenue-center mapping, check opening, confirmed spend, menu sync and prepayments.RESTAURANT → 12How to Check Oracle Simphony Versions, Licensing and API AccessA practical checklist for Simphony releases, STS Gen2 provisioning, API accounts and location permissions.SIMPHONY CLOUD · INTEGRATION →
BLOG

Articles on Pay.

Recent articles about Pay.

01What should a restaurant do when a year-end company dinner request comes in?Before saying yes on the phone, pin down headcount, menu, prepayment and invoice details together. Here is a step-by-step flow for company dinner requests.Nov 11, 2026 → 02How long should you hold a table for a late guest?There is no single waiting time for a late guest: set the policy first, then reflect it on the floor plan and the record. Here is how to decide before service starts.Nov 9, 2026 → 03Oracle Simphony Cloud and Open APIs: How the Integration Ecosystem WorksExplore Simphony Cloud's open API architecture, STS Gen2 integration workflows, licensing and independent solution providers.SIMPHONY CLOUD · INTEGRATION → 04How Simphony Cloud Service Models Affect API AccessUnderstand the distinction between the cloud service model, account administration and API entitlement in Simphony.SIMPHONY CLOUD · INTEGRATION → 05Simphony STS Gen2 vs BI API vs Configuration APILearn how Simphony STS Gen2, Business Intelligence and Configuration APIs support different use cases.SIMPHONY CLOUD · INTEGRATION → 06How Restaurants Can Reduce POS Integration Vendor Lock-InEvaluate API access, portability, contracts and third-party integration options before your POS becomes a constraint.SIMPHONY CLOUD · INTEGRATION → 07What Oracle Simphony Integration Partner Validation MeansUnderstand Oracle's integration partner programme, STS Gen2 validation and the steps needed at each venue.SIMPHONY CLOUD · INTEGRATION → 08Mapping Oracle Simphony Revenue Centres Across Hotel RestaurantsPlan location, revenue-centre and reservation mapping across multiple Simphony hotel dining outlets.SIMPHONY CLOUD · PRACTICAL GUIDE → 09What Is a Digital Hotel Guest Experience Platform?Understand how a hotel guest platform connects dining, room services and payments to separate operational systems.GUESTS → 10Hotel Pre-Check-In vs Online Check-InPre-check-in prepares the guest's arrival; online check-in and official PMS status may require separate verification and legal steps.GUESTS → 11Hotel Upselling: Catalogue, Orders and PaymentsAn upsell becomes a real hotel sale only when eligibility, price, order, payment and delivery are recorded separately.REVENUE → 12Hotel Room Service QR Orders and Stay VerificationDistinguish room service QR ordering, guest eligibility, service locations, payment and PMS room folio posting.GASTRONOMY →

Less uncertainty. More secure evenings.

Let's look together at how Rezervem Pay brings your payment processes together.