Give customers a clear reason to come back.
Malta Rewards is a proposed rewards app and system where customers can see how to earn and use rewards, while participating businesses manage the rules, transaction records and settlement behind them.
A rewards scheme people can understand and staff can manage.
01
Make the next visit worth considering
Customers could see which rewards they are working towards and what they can use next. A clear offer gives them a reason to consider returning; the pilot would check whether that changes visits or purchasing behaviour.
02
Give staff a clear answer at the counter
Visible eligibility, balances and redemption rules could reduce guesswork when a customer asks to use a reward. Staff would have an agreed way to check the transaction and explain a declined or adjusted reward.
03
Keep reward costs and adjustments visible
Linked earning, redemption and reversal records would help businesses understand what they funded, what was used and what needs reconciling. A shared scheme would need equally clear responsibilities between participating businesses.
The pilot would test whether clear rules and dependable records make rewards easier to use. Repeat visits, customer value and operating effort would be measured rather than assumed.
Simple customer access. Clear records behind each reward.
Start with an agreed reward model and a limited pilot. Customer access and staff controls should explain the same rules throughout the transaction.
Earn and use a reward
Open the customer view
The customer opens the Malta Rewards app or an agreed mobile customer view. They see the businesses actually participating in the pilot, available offers and their own reward history. Access requirements would be defined before joining.
See the rules before purchasing
The offer explains eligible purchases, how rewards are calculated, limits and any expiry. Staff confirm an eligible transaction before an award is recorded; an unverified purchase does not become a confirmed reward.
Confirm a redemption
The customer chooses an eligible reward and staff confirm its use. The customer sees the actual result and updated balance. The design would need controls for repeated requests, failed confirmations and a reward already used.
See corrections in the history
A return, cancelled purchase or mistaken award is handled as a linked adjustment under the agreed rules. The history explains what changed instead of silently removing the original record.
Run and reconcile the scheme
Agree what the business is offering
Choose the earning and redemption rules, who funds the reward, where it can be used and which staff may approve adjustments. A single-business scheme and a shared scheme would have different responsibilities.
Record confirmed activity
Staff use an agreed screen or a supported system connection to record awards and redemptions. Transaction references and access controls would support checks without assuming compatibility with every till or payment system.
Reconcile participating businesses
Review the reward records against the underlying transactions. Where businesses share a scheme, an agreed settlement statement would show who funded and honoured each reward, adjustments and any amount still disputed.
Resolve returns and differences
An assigned person reviews unmatched activity, cancellations and correction requests. Approval and reversal steps would preserve a history and produce an updated statement for the businesses involved.
Choose a scheme that fits the participating businesses.
Participation, commercial terms and responsibility for rewards would be agreed with each business. Publishing this concept does not establish a merchant network.
01
Start within one business
Test rewards earned and redeemed with one business. This keeps the first rules, funding decisions and staff responsibilities within a single operation while customer and transaction controls are assessed.
02
Explore a shared pilot
If several businesses choose to participate, define exactly where rewards can be earned and used. Agree funding, settlement timing, adjustments and disputed transactions before enabling activity between them.
03
Choose how transactions are confirmed
Use a staff screen for a limited pilot, or assess a supported connection to an existing system. Manual verification and reconciliation effort must be counted when assessing the scheme's practical value.
Test the rules before widening participation.
Agree a limited set of offers, participants and transaction types. Establish how reward costs, customer behaviour and staff work will be compared with the current approach.
- 1
Define the scheme and its responsibilities
Review the existing customer experience and any current reward process. Agree earning, redemption, expiry, returns, funding and settlement rules, plus who can resolve a customer or business query.
- 2
Run a controlled customer pilot
Test customer access, staff approvals, duplicate requests and correction scenarios. Invite an agreed group to use the offers and record actual activity, support work and customer feedback.
- 3
Reconcile and review the outcome
Compare reward records with confirmed transactions and settle any differences. Review usage, observed repeat visits, reward costs and staff effort before deciding whether to change the rules or extend participation.
What we would measure together
- Customer access, completed enrolments and reasons people choose not to participate.
- Confirmed earning and redemption activity against the agreed eligibility rules.
- Observed repeat visits, with comparison limits and other influences recorded.
- Reward costs, settlement differences and the time needed to resolve them.
- Duplicate attempts, reversals, disputed rewards and correction outcomes.
- Staff handling time, customer support requests and clarity of the rules.
Before you decide.
Where would customers earn and use rewards?
That depends on the agreed pilot. The customer view would list only businesses and offers actually participating, with the rules for each. There is no confirmed merchant network or promise that rewards can be used across businesses at this stage.
Who would pay for a reward or settle with another business?
The businesses would agree the funding and settlement model before taking part. Records would distinguish who issued, funded and honoured the reward. Shared participation would require an agreed statement, adjustment and dispute process; the app does not by itself guarantee payment or reimbursement.
What happens after a return or mistaken transaction?
The rules would define when an award or redemption is reversed and who may approve it. A correction should link to the original transaction and be visible in the customer and business histories. These scenarios would be tested before broader use.
Would customers have to install an app?
Malta Rewards is proposed as an app and rewards system. The pilot would choose whether customer access starts through an app, a mobile browser view or both. Account requirements, recovery and an assisted staff process would be defined around the transactions being tested.
Would joining also sign customers up for promotions?
Rewards access and optional promotions would be separate choices. The proposed flow would record any promotional preference distinctly and provide a way to change it. Joining a rewards scheme or expressing interest on this registry would not be treated as consent to promotional messages.
Is Malta Rewards available now, and what would it cost?
This page proposes a pilot. Participating businesses, reward terms, customer access, operating responsibilities and pricing still need to be agreed. Expressing interest does not purchase a service, fund a reward balance or guarantee that the scheme will launch.
Project scope
Malta Rewards is a proposed customer rewards app and operating system for businesses that choose to participate. The scope would connect customer access, clear earning and redemption rules, staff transaction approval, linked reversals, participating-merchant reconciliation and an agreed settlement process. A pilot would establish how rewards are funded, what customer information is needed, who resolves differences and how optional promotions are kept separate from using the scheme. The choice of offers, participating businesses, system connections and commercial terms remains to be agreed.
- Stage
- Proposed pilot
- Project by
- Coding Reality
- Scope and pricing
- The reward model, who funds each benefit, transaction controls, participating businesses, customer access and any system connections would be agreed before a pilot. Setup, operating charges and reward costs need separate scoping. No merchant network, launch date or financial return is promised.
What would make rewards useful for your customers?
Share how you would want to earn, offer or manage rewards. Your interest can help shape the first Malta Rewards pilot without committing you to participate.
Let’s talk about your business.
Ask a question, explore a pilot or tell us what would help. Expressing interest creates no order or payment obligation.
Prefer to contact us directly?
These links open your email or messaging app. Nothing is sent until you choose to send it.
Talk to us directly.
The online form is not open yet. Use a contact link to ask about this project.
See what a pilot would involve