Transactions, Sales and Refunds | Retail

What this section covers

Five articles covering the full post-sale lifecycle in Retail Core  from looking up a transaction to processing a refund, and from controlling how payments are captured to keeping customers informed about their orders.

Before You Start

• ✅ You have an active Retail Core account with Administration access to configure cancellation options, refund reasons, and operational settings.
• ✅ For Transaction History: at least Reporter access is sufficient to search and view transactions.
• ✅ At least one device is activated and has processed transactions before you use the transaction search.
• ✅ For SMS notifications: an active SMS provider integration must be configured for your account. Contact Nayax support if you are unsure whether this is enabled.

Transaction History

The transaction history search lets you look up any sale across your entire estate. Filter by date range, terminal, product, payment method, or transaction amount to find exactly what you need whether you are reconciling an end-of-day discrepancy or investigating a customer query.

Returns and Cancellations

Before staff can cancel a sale or process a refund at the terminal, you need to set up the reasons they can select. This gives you visibility into why transactions are being reversed and ensures every cancellation or refund is traceable in your reporting.

Cancellation options are the reasons your staff or system can select when a sale is voided before completion. Create options that reflect real scenarios at your terminals - for example "Customer changed mind", "Item out of stock", or "Incorrect item scanned".

Refund reasons are the options staff select when reversing a completed sale. Meaningful refund reasons - for example "Damaged product", "Wrong item", or "Customer dissatisfied" make it easier to spot patterns and address operational issues before they affect more customers.

Operational Settings

Two administration settings that directly affect how transactions flow and how customers are informed. Enable these when your workflow requires payment to be captured immediately on order confirmation, or when you want to notify customers by SMS when their order is ready.

When enabled, payment is captured at the moment the order is confirmed rather than at a later stage in the workflow. Use this for self-checkout and unattended scenarios where the terminal should not hold a pre-authorisation open.

When enabled, Retail Core sends an SMS to the customer when their order is ready for collection. This is particularly useful for food service and hospitality operators running a prepare-then-collect workflow, reducing counter congestion and improving the customer experience.