Loyalty, points & rewards
Evidence for that status: The rewards ledger is serving production traffic today, with an idempotent, versioned credit path. See the case study. Read the case study →
What it does
The ledger
Issuance, expiry and transfer, with a balance finance can recognise and reconcile.
Redemption
Catalogue, partner redemption and the settlement between the parties who honoured it.
Programme operations
Campaign configuration, member service tooling, and adjustment with an audit trail.
White-labelled, and not
Yours
- Brand, domain and the member-facing interface
- Earn, expiry and redemption rules
- Catalogue and partner configuration
- The support relationship with your members
Not white-labelled
- Partner commercial agreements
- The accounting treatment of the outstanding balance
- Payment processing relationships
Integration surface
REST for earn, burn and balance, built idempotent for point of sale; webhooks on member and balance events; a nightly export the finance system reconciles against.
Who operates what
The licensee owns the programme, its economics and its member relationships. We own the software. The expiry policy and the balance treatment are the licensee’s to sign off with their finance function — the platform implements what is decided.
- Deployment
- Your cloud · ours · hybrid
- Ledger
- On-chain or off-chain, configured
- Licensing
- Annual + volume
- Support
- Tiered; SLA in contract
Publication gate: capability claims on this page are verified against the running software before publication. Lineage: Lineage pending inventory.
Reference deployment
A rewards ledger that reconciles, by construction — A points-and-rewards ledger built so that a repeated request cannot double-credit a balance — with the idempotency key derived from the event that caused it, never from a timestamp.
Request a technical evaluation
Engineers on both sides, against your requirements. If the software does not do what you need, this is where you find out.