Payments and deposits

Request deposits. Send links. Track payments.

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.

Payments

Active

Request invoices and payment links, keep providers connected, and decide when Elyx collects money.

Request payment
Providers
Order handling
Defaults
Policies
3/3 ready PayPal active Card links enabled

Recent payment requests

12 of 12 payment links shown.

Refresh

€50,000.00

Grill Lab Events

waiting

private hire deposit

€3,000.00

Femi Lawal

waiting

Saturday group booking

€500.00

Maya Collins

waiting

catering balance

What Elyx offers

Deposits, checkout links and recovery in one workflow.

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.

Tables, events, groups

Booking deposits

Set when deposits are needed, request them automatically, and mark the booking paid when the guest completes checkout.

SMS, email, hosted checkout

Payment links

Send a checkout link from a call, booking, order or staff action using the details already captured.

Direct orders

Website and app checkout

Take direct collection, delivery and repeat orders through the branded online ordering flow, then return checkout status to Elyx.

Table payments

Table QR and NFC pay

Let guests open the right table payment or order flow from a QR code or NFC tag, with table context already attached.

On the floor

Tap to Pay

Take a contactless payment on supported floor devices or terminals and keep the payment outcome tied to the guest, table and order.

Failed, expired, unpaid

Recovery queue

Track unpaid deposits, failed links, expired checkouts and no-show risk so the team knows which payment needs follow-up.

Merchant-owned payments

Provider connections

Use configured rails such as Stripe, Mollie or PayPal where available, with the restaurant staying paid through its own provider account.

Audit trail

Receipts and exceptions

Payment outcomes update the booking, order and Operator record. Refunds and exceptions stay controlled by rule.

How it works

From payment request to booking or order update.

Elyx keeps the rule, checkout link, status, reminder and receipt on the booking or order instead of leaving them inside a provider dashboard.

01

Set the rule

Choose when Elyx should request a deposit or payment: party size, channel, order type, service, value or manual approval.

02

Take or send payment

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.

03

Watch the status

Paid, failed and expired events flow back into the restaurant record instead of sitting inside a provider dashboard.

04

Follow up

If the payment is not completed, Elyx prepares the reminder, resend, callback or owner approval with the reason attached.

Provider rails

Payments stay connected to the restaurant account.

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.

StripeStripe DirectMolliePayPalTap to PayTable QR and NFCOnline ordering checkoutHosted checkoutPayment webhooksSMS deliveryOperator receipts

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

Recovery

Follow up before the booking or order is missed.

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.

Unpaid deposits

See which bookings still need a deposit before service.

Failed or expired links

Resend, cancel or hand off the next move without losing the payment history.

No-show and refund exceptions

Keep sensitive cases inside owner rules and Operator approvals.

Payments + Operator

Recover unpaid deposits and failed payment links.

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