Booking deposits
Set when deposits are needed, request them automatically, and mark the booking paid when the guest completes checkout.
Elyx connects bookings, calls, branded online ordering, QR and NFC table flows, Tap to Pay and guest history to the payment step. It requests deposits, sends checkout links, tracks payment status and brings failed payments back to Operator.
Request invoices and payment links, keep providers connected, and decide when Elyx collects money.
12 of 12 payment links shown.
€50,000.00
Grill Lab Events
private hire deposit
€3,000.00
Femi Lawal
Saturday group booking
€500.00
Maya Collins
catering balance
Elyx handles the steps around the payment: when to request it, how to send it, whether it was paid, and what to do when it fails.
Set when deposits are needed, request them automatically, and mark the booking paid when the guest completes checkout.
Send a checkout link from a call, booking, order or staff action using the details already captured.
Take direct collection, delivery and repeat orders through the branded online ordering flow, then return checkout status to Elyx.
Let guests open the right table payment or order flow from a QR code or NFC tag, with table context already attached.
Take a contactless payment on supported floor devices or terminals and keep the payment outcome tied to the guest, table and order.
Track unpaid deposits, failed links, expired checkouts and no-show risk so the team knows which payment needs follow-up.
Use configured rails such as Stripe, Mollie or PayPal where available, with the restaurant staying paid through its own provider account.
Payment outcomes update the booking, order and Operator record. Refunds and exceptions stay controlled by rule.
Elyx keeps the rule, checkout link, status, reminder and receipt on the booking or order instead of leaving them inside a provider dashboard.
Choose when Elyx should request a deposit or payment: party size, channel, order type, service, value or manual approval.
Elyx can send the hosted checkout link, support table QR/NFC payment, or keep an in-person Tap to Pay outcome attached to the same record.
Paid, failed and expired events flow back into the restaurant record instead of sitting inside a provider dashboard.
If the payment is not completed, Elyx prepares the reminder, resend, callback or owner approval with the reason attached.
Elyx sits around the payment workflow: provider setup, hosted checkout, delivery of the link, status tracking, recovery prompts and receipts. The restaurant remains the merchant.
Provider setup
The restaurant gets paid by its own account.
Provider
Stripe, Mollie or PayPal when configured
Checkout
Hosted link with booking or order context
In person
Tap to Pay or terminal outcome attached to the order
Outcome
Paid, failed or expired status returns to Elyx
Before service starts.
A failed payment link, missing deposit or no-show risk is easier to act on while the booking, order or call details are still available.
See which bookings still need a deposit before service.
Resend, cancel or hand off the next move without losing the payment history.
Keep sensitive cases inside owner rules and Operator approvals.
Start with deposits, payment links, order checkout and failed-payment recovery. Then connect the payment status back to bookings, guests, orders and Operator receipts.
Deposit requests
Payment recovery
Receipts in Operator