For Australian retailers running points, cards or both

Loyalty and Gift Card Integration: Money Customers Can Spend Anywhere

A points balance and a gift card balance are not marketing features. They are amounts your business owes, redeemable instantly at any till or checkout, by a customer who is entirely certain what the number should be. Which is why loyalty integration is judged by a standard that most other integrations are not: it has to be right every single time, at the counter, in front of someone.

The problems are consistent across networks: balances that differ between the shop and the website, a card redeemed twice because a till was offline, points awarded on a purchase that was later refunded, and a liability figure in the accounts that nobody trusts. This page covers what has to be integrated, how Australian gift card rules constrain the design, and where the fraud actually happens.

Book a Loyalty Integration Call (03) 9003 0111

Realistic ROI

One balance authority

Or you will have two answers

Every channel asks the same system; nothing keeps its own running total

3 years minimum

Expiry on most gift cards sold to consumers

An Australian Consumer Law requirement, with limited exceptions, since late 2019

Offline is a design case

Not an exception to handle later

Tills lose connectivity, and the rules for what they may do must be decided in advance

Weeks 4 to 10

For a first integrated balance across channels

Longer in networks with separate entities settling card redemptions between them

Four Things That Decide Whether a Loyalty Integration Holds Up

Points and cards fail in public, at a counter, with a queue behind. These four decisions are why.

One system owns the balance, everything else asks

The most common cause of a wrong balance is two systems each keeping their own running total and syncing periodically. Between syncs they disagree, and the customer discovers it. The correct shape is that one system is authoritative for both points and stored value, and every channel queries it in real time rather than caching a number. That system can be the point of sale, the loyalty platform or the ERP, but there has to be exactly one, and it should be chosen for availability rather than for feature list.

Gift cards are regulated, not just configured

Gift cards supplied to consumers in Australia must generally be redeemable for at least three years from supply, must display the expiry date or state that there is none, and post supply fees are restricted. Some cards are excluded, such as those given as part of a customer loyalty or promotion scheme or those for goods available for a limited period. That is a design constraint rather than a marketing preference, so the expiry logic and what is printed on the card need to be settled with reference to the actual rules and, where there is doubt, with advice.

The liability has to reconcile to the ledger

Unredeemed gift card value and unredeemed points are obligations, and they belong in the accounts as such rather than as a report in the loyalty platform that finance has never reconciled. The integration should post the movements, issuance, redemption, expiry and adjustment, so the balance in the ledger can be tied back to the sum of outstanding balances. Where those two numbers have never been reconciled, the first reconciliation is usually the most valuable output of the entire project.

Refunds and reversals are where programmes leak

A customer earns points on a purchase, then returns it. Pays partly with a gift card, then gets a refund. Redeems points against an order that is later cancelled. Each of these needs a defined reversal path, and each is a route to accumulating value that was never earned if the path does not exist. Design the reversals at the same time as the earn rules, not after someone works out that returning a large order twice is profitable.

What Has to Be Integrated

Six areas. The first two are what customers notice, the last two are what finance notices.

Real time

Balance lookup everywhere

The counter, the website, the app, the call centre and the customer’s own account page all ask the same authoritative system and all get the same number at the same moment. Response time matters here in a way it does not elsewhere, because this query sits in the middle of a transaction with a person waiting, so a slow answer is treated by staff as a broken system and worked around.

Consistent logic

Earn and redemption rules

What earns points, at what rate, on which categories, and how that interacts with discounts, promotions and gift card payment. These rules belong in one place and are applied identically online and in store. When the rules are configured separately in the point of sale and the ecommerce platform they diverge within a season, and the first indication is a customer proving that the same basket earned differently in two channels.

Agreed limits

Offline and degraded operation

Tills lose connectivity. The design has to state what a till may do without a live balance: refuse redemption, allow up to a capped amount, or queue the transaction for later posting with the risk that accepts. Every option is defensible and the wrong approach is not choosing, because staff will improvise and the improvisation is where double redemption happens.

Closed loops

Reversals and adjustments

Returns reverse the points they generated. Refunds against a gift card payment return value to that card rather than to cash, which is both the correct commercial position and a significant fraud control. Cancelled orders release redeemed points. Manual adjustments are possible but logged, attributed and reportable, because an unlogged adjustment capability is an internal fraud waiting to be discovered.

To the ledger

Liability and reporting

Issuance, redemption, expiry and adjustment posted so the outstanding liability in the accounts reconciles to the sum of live balances, with breakage recognised on a basis your accountant has agreed rather than whenever someone runs a clean up. This is also the data that tells you whether the programme is actually changing behaviour or simply discounting to people who would have bought anyway.

Across the network

Multi entity settlement

In a franchise or multi entity group, a card sold by one entity and redeemed at another creates a genuine debt between two separate businesses. That settlement has to be calculated and recorded, not assumed to wash out. It is the single most common reason gift card programmes are limited to the store of purchase, which customers find baffling and which costs the network sales.

Loyalty and Stored Value Before and After

Task	Traditional	Integrated Programme	Notes
Customer asks for their balance	Different answer in store and online	One authoritative balance everywhere	The single most damaging failure, because the customer sees it happen.
Earning on an online order	Uploaded in a nightly batch	Applied at the time of purchase	Delayed earning generates support contacts and undermines the programme’s point.
Redeeming across channels	Points usable in one channel only	Usable wherever the customer shops	Usually the change that lifts programme engagement most in multichannel retailers.
Till loses connectivity	Staff improvise at the counter	Defined degraded mode with a cap	Any policy is better than none. Improvisation is where double redemption occurs.
Return of a points earning sale	Points quietly retained	Earned points reversed automatically	Closes an obvious loop that erodes both margin and programme credibility.
Refund of a gift card purchase	Refunded to cash at the counter	Returned to the original card	Correct commercially and a meaningful fraud control against card based schemes.
Reporting the liability	A platform report finance distrusts	Movements posted and reconciled	The first reconciliation frequently uncovers years of accumulated drift.
Card sold at one store, used at another	Blocked, or settled by argument	Redeemed anywhere, settled automatically	Only possible once the inter entity commercial rule is actually agreed.

Where Loyalty and Gift Card Programmes Go Wrong

Two systems each keeping a balance

The moment the point of sale and the ecommerce platform each maintain their own running total and reconcile periodically, you have guaranteed that some customer will see two different numbers. Choose one authoritative system, have every channel query it live, and accept the availability requirement that comes with that choice. If the authoritative system cannot answer quickly and reliably enough for a counter transaction, that is a reason to change the system rather than to start caching balances.

Expiry rules set by marketing preference

Gift cards supplied to consumers in Australia must generally be redeemable for at least three years, must show the expiry date or state that there is none, and are restricted in the fees that may be charged after supply. There are exclusions, including certain promotional and loyalty scheme cards, and the boundaries matter. Configure expiry from the applicable rules rather than from a campaign plan, keep the printed and digital wording consistent with what the system enforces, and take advice where a card type sits near an exclusion.

Unlimited manual adjustment

Every loyalty system needs a way to correct a genuine error at the counter, and that same capability is the most direct route to internal fraud in the entire retail stack. Cap the adjustment a staff member may make unsupervised, require a reason code, log the operator, and put a weekly exception report of adjustments in front of someone who does not work on the counter. This is a control that costs almost nothing and is conspicuously absent from most implementations.

Gift card numbers that can be guessed or tested

Sequential or short card numbers can be enumerated, and a balance check endpoint with no rate limiting lets someone test thousands of candidates until they find a funded card. Use long random numbers, require a separate verification value for online redemption, rate limit and monitor balance enquiries, and alert on patterns of failed checks from one source. Activation at the point of sale rather than at printing also prevents stolen inactive stock from carrying value.

Breakage recognised when convenient

Unredeemed value is a liability until it is genuinely extinguished, and recognising it as income because a balance has been quiet for a while is an accounting judgement rather than a housekeeping task. Agree the basis with your accountant, apply it consistently through the integration, and keep the underlying balances intact so the position can be reconstructed. Expiry that is applied by the system must also match what the customer was told and what the law permits.

Programme data collected without a clear purpose

Loyalty programmes accumulate detailed purchase histories, and under the Privacy Act 1988 and the Australian Privacy Principles that information should be collected for a stated purpose and used consistently with what members were told when they joined. Terms that were written for a single store programme frequently do not support the network wide analysis and marketing that an integrated programme makes possible. Check the wording before the capability exists rather than after.

How Yes AI Approaches Loyalty Integration

Balance authority decided first

We work out which system should own points and stored value based on availability, response time and where the money is ultimately accounted for, then design every channel to ask it rather than cache it. This one decision prevents most of the failures the programme would otherwise have.

Built, hosted and monitored by us

The integration runs on a managed cloud automation layer we operate, with alerting on failed balance lookups, unposted redemptions and any divergence between channel activity and the ledger, so drift is caught in days rather than at year end.

Fraud controls built in, not bolted on

Adjustment caps with reason codes and operator logging, rate limited balance enquiries, refunds returned to the original tender, and exception reports that go to someone away from the counter.

Honest advice on programme design

Plenty of Australian retailers do not need a dedicated loyalty platform, and some programmes are discounting loyal customers who would have returned regardless. We will tell you when the integration is the answer and when the programme design is the actual problem.

From Two Balances to One

Five steps. A single balance across channels is normally live between weeks four and ten.

Audit balances and reconcile

Compare what each system believes, quantify the divergence, and reconcile outstanding gift card and points liability against the ledger. This step alone frequently pays for the project.

Choose the authority and the rules

One system owns points and stored value, with earn, redemption, tier and interaction rules written down once and applied identically in every channel.

Decide degraded and reversal behaviour

What an offline till may do, how returns reverse earned points, how refunds against gift cards behave, and what manual adjustment is permitted, by whom and with what logging.

Build, test at the counter

Built against official interfaces and tested with real staff at real tills including deliberate connectivity failures, because a loyalty integration that has only been tested in an office has not been tested.

Post to the ledger and monitor

Issuance, redemption, expiry and adjustment posted so liability reconciles continuously, exception reporting turned on, and multi entity settlement enabled where the network needs it.

FAQ

Which system should hold the loyalty balance?

Whichever one can answer a balance query quickly and reliably during a counter transaction, and which is closest to where the value is ultimately accounted for. In many Australian multichannel retailers that is the point of sale, because it must keep working when other systems are slow, but a dedicated loyalty platform or the ERP can be equally correct. The requirement that does not bend is that there is exactly one authority and every other channel asks it. Two systems each maintaining a balance will disagree, and the customer will be the one who notices.

What are the rules on gift card expiry in Australia?

Since late 2019, gift cards supplied to consumers must generally be redeemable for at least three years from the date of supply, the expiry date must be shown on the card or it must state that there is no expiry, and post supply fees are restricted. A number of card types are excluded from the rules, including cards supplied as part of a customer loyalty or promotion scheme, cards for goods or services available for a limited period, and certain other categories. Because those exclusions determine what your system must enforce, this is worth confirming against the current guidance and, where a card type is near the boundary, with advice. The point for the integration is that expiry logic is a compliance setting rather than a marketing one.

What should happen when a till goes offline?

Whatever you decided in advance. The three workable options are to refuse redemption entirely until connectivity returns, to allow redemption up to a capped value and accept the risk of a small amount of double spending, or to queue the transaction for posting later with a reconciliation step. Which one suits depends on your average transaction value and how often connectivity actually fails. What does not work is leaving it undefined, because staff faced with a customer and a queue will find a way through, and the improvised way through is usually the one that lets the same card be spent twice.

How should gift card liability appear in our accounts?

Unredeemed value is money you owe, so it generally sits as a liability until it is redeemed or properly extinguished, with revenue recognised on redemption rather than on sale. The integration’s job is to post the movements, issuance, redemption, expiry and adjustment, so that the ledger balance can be reconciled against the sum of live card balances at any time. Breakage, meaning the portion never expected to be redeemed, is an accounting judgement that should be agreed with your accountant and then applied consistently, not decided by whoever runs a periodic clean up.

How do gift cards work across a franchise or multi entity network?

They work well once the commercial question is settled and badly before it is. A card sold by one entity and redeemed at another creates a real obligation between two separate businesses, so the network needs an agreed settlement mechanism, typically a periodic transfer calculated from the redemption data. Once that exists, the integration can calculate and record it automatically and cards become usable across the network. Where it does not exist, groups usually restrict cards to the store of purchase, which customers find confusing and which quietly costs the network sales it would otherwise have made.

What are the main fraud risks and how do we reduce them?

The common ones are enumeration of card numbers through an unprotected balance check, redemption of cards stolen before activation, refunds of gift card purchases taken in cash, and unlimited manual adjustments by staff. The corresponding controls are long random card numbers with a separate verification value online, rate limited and monitored balance enquiries, activation at the point of sale rather than at printing, refunds returned to the original tender, and adjustment caps with reason codes and operator logging reviewed by someone who does not work at the counter. None of these are expensive and all of them are commonly missing.

Is a loyalty programme worth integrating at all?

Sometimes the honest answer is no, or not yet. A programme that awards a discount to customers who were returning anyway is a margin reduction wearing a marketing badge, and integrating it more tightly simply makes the discount more efficient. The question worth answering first is whether the programme changes behaviour: do members shop more often, spend more per visit, or return sooner than comparable non members. If the data cannot answer that, fixing the measurement is a better first project than extending the redemption. We would rather say that early than build something well that should not have been built.

One Balance, Everywhere, That Reconciles

Book a call. We audit your current balances against the ledger, tell you where the drift is, and give you a priced plan. The reconciliation is yours either way.