Platform overview

Loyalife lets businesses design and operate loyalty programs without writing backend logic from scratch. You configure who earns what, when, and how — through a rule engine, tier system, and engagement tools — and Loyalife handles the processing, storage, and communication.

​

Who uses Loyalife

Three types of users interact with the platform:

​

Platform modules

​

How a loyalty transaction flows

When a member makes a purchase, Loyalife processes it end-to-end:

1. Transaction received — your system sends a transaction event to Loyalife via API or file upload.
2. Fraud check — if the transaction amount or pattern exceeds a configured threshold, the transaction is held in a pending state for admin review. Approved transactions continue; rejected ones are cancelled with no points movement.
3. Rule Engine evaluation — the engine evaluates all active earning rules against the transaction attributes (amount, MCC, date, member attributes).
4. Points calculated — matching rules determine how many points or what cashback percentage applies. Caps and limits are enforced.
5. Tier check — the member’s updated balance is checked against tier thresholds. Upgrades or downgrades are applied if criteria are met.
6. Member ledger updated — a typed entry (e.g., Credit By Accrual) is written to the points ledger. The member’s balance and statement are updated.
7. Communication sent — an SMS, email, or push notification can be triggered to inform the member of their earned reward.

​

Key concepts

Rule groups organise related earning rules. A rule group can be linked to a specific member segment, ensuring the right logic applies to the right audience. Segments define who a rule or campaign targets. Segments can be dynamic (auto-updating as members meet criteria) or frozen (point-in-time snapshot). Tiers are status levels members attain by accumulating qualifying points or spend. Each tier can have different earning multipliers and benefits. Campaigns are time-limited promotions layered on top of baseline earning rules. A campaign targets a specific segment during a defined window and awards bonus points, cashback, or multipliers — without permanently changing the underlying rule logic. Campaigns can be broadcast (manually scheduled) or triggered (fired automatically by a member event). Channel partners are retailers, distributors, or field agents who interact with Loyalife through a dedicated partner app rather than the admin portal. They earn rewards for sales activity — submitting invoices and warranty claims — rather than for purchases as end members do. Programs with channel partners have a separate approval workflow for claim verification. Points ledger records every credit and debit event on a member’s account as a typed entry — for example, Credit By Accrual, Debit By Redemption, or Credit By Bonus. The ledger type identifies exactly what generated each movement, making it possible to filter, reconcile, and audit activity by source. See Transaction categories for the full reference. Fraud prevention allows programs to define point and transaction thresholds that hold suspicious activity in a pending state before points are posted. Administrators review flagged transactions and approve or reject them. Rejected transactions are cancelled without any points movement. Maker-Checker workflow governs sensitive admin actions — a maker submits a change and a checker must approve it before it takes effect. This applies to member status changes, manual point adjustments, rule activation, and more. Audit trail records every configuration change and user action with a timestamp, actor, and before/after values.