Ops Console
Business, risk and compliance teams configure and run the entire programme.
Points earned the moment the purchase happens.
A bank-grade loyalty platform with real-time accrual, a no-code rule engine, three ways to redeem and a complete audit trail — built to sit alongside your core banking and channel systems, not replace them.
One backend · Three purpose-built front ends · Four integration paths
Customer Portal
White-label, mobile-first app for balances, rewards and redemption.
Open APIs
For the bank's own mobile app, POS network and core banking feed.
Architecture
One platform behind every channel
Every screen, API and report reads from the same services and the same business logic. The balance a customer sees can never drift from what a service agent or the bank's own core system sees.
Front ends
Ops Console · 7 roles
Customer Portal · SSO
Bank Channels · POS & APIs
One backend
Rule Engine
Points Ledger
Redemption
Merchants
Customer 360
Maker-Checker
Audit & Fraud
Analytics
Direct stream
CSV batch
Your own broker
Channel APIs
Four integration paths — same downstream result. The rule engine and the ledger never know which path a transaction arrived by.
Real-time by default
Transactions are evaluated against active rules in seconds, not on a nightly batch cycle.
Configured, not coded
Business users author rules, tiers, campaigns and field mappings without engineering involvement.
Compliance-first
Append-only ledger, maker-checker and full audit trail are foundational, not bolted on.
The core differentiator
Points are earned the moment a transaction happens
Transactions stream in and are evaluated against every active rule in seconds. Customers see their reward while the purchase is still fresh — the single biggest driver of programme engagement.
Visual, no-code rule builder
Two interchangeable authoring modes — a condition-tree editor and a drag-and-drop canvas — designed for business users rather than engineers.
Simulation before go-live
Test any rule against sample transaction data and see exactly what it would award before a single customer is affected.
Configurable earn caps
Per transaction, per day, per month or lifetime per customer — enforced correctly even when several rules match the same transaction.
Maker-checker on every change
Each rule is drafted, reviewed and approved by a second person before it takes effect. Full audit trail, no exceptions.
What a rule can express
Conditions
Product and sub-product such as card tier, transaction and channel type, amount, customer segment, loyalty tier, time of week or month, customer tenure, days since last transaction, and cumulative spend across a rolling or calendar-month window.
Calculations
Flat points per transaction, points per riyal spent, tiered slabs that reward higher spend, and promotional multipliers.
Governance
Draft, review and approve, with old-value and new-value differences retained for audit.
Why it matters
Batch loyalty programmes lose the moment
When points post overnight, the reward is disconnected from the purchase that earned it. Real-time accrual closes that gap — and makes time-boxed campaigns, streaks and instant multipliers possible in the first place.
Personalisation
Reward the right customers, not every customer
Blanket earn rates are expensive and rarely change behaviour. Tiers and segments let the bank concentrate reward spend where it actually moves the needle.
Tier management
Configurable tiers with automatic movement up and down, driven by customer behaviour and evaluated by the same engine that awards points.
Customer segmentation
Segments defined from behavioural and profile attributes; rules and campaigns can target any segment directly.
Campaign insights
See which rules and segments are genuinely driving lift, rather than assuming.
Campaign insights dashboard
Three views on one screen, built to answer the question every programme owner is asked.
Campaign performance by rule
Which specific rule produced the accrual, and what it cost in points liability.
Segment versus platform average
Whether a targeted segment is genuinely outperforming the customer base as a whole.
Tier movement trends
Whether customers are climbing tiers, stalling, or quietly falling back down.
Attribution that holds up
Because targeting, earning and reporting all run through the same rule definition, a campaign's results are attributable to the exact rule that produced them.
In practice
A campaign is a rule with an audience
There is no reconciliation between a marketing tool and the points system, because there is only one system.
Everywhere the customer is
One rewards catalogue, three ways to redeem
Points only feel valuable when they are easy to spend. The platform supports catalogue vouchers, direct payment at a merchant till, and cash-back straight onto the customer's own card or account — from a single catalogue and a single balance.
Voucher catalogue
Merchant-branded vouchers, browsable and redeemable from the customer app — or by a service agent acting on the customer's behalf.
Pay with points at POS
Redeem points directly against a purchase amount at a partner merchant's till, OTP-secured, with no catalogue item required.
Cash-back
The customer converts points to cash-back credited onto their own card or account, settled through the bank's existing process.
Merchant network management
- Full merchant onboarding and lifecycle management from the Ops Console — or via the merchant self-service portal for brands who prefer to manage their own inventory
- Merchant mobile app for on-the-go campaign visibility, QR-based POS activation and redemption confirmation
- Voucher inventory handled either way — auto-generated codes, or merchant-supplied code and PIN files
- Voucher aggregator marketplace: connect third-party aggregators to extend the catalogue beyond the bank's direct merchant network
- Per-merchant, per-month settlement reporting produced for finance reconciliation
- VAT treatment on voucher issuance and redemption reflected in the reporting finance already works with
Gamification and engagement
Spin & Win
A configurable, weighted prize wheel with a daily spin allowance in the customer app. Prizes are points, credited to the ledger like any other accrual.
Personalised targets
Challenges generated from a customer's own transaction patterns — a spend target on categories they already use — with bonus points on completion.
Promotions
Admin-managed banner campaigns on the customer home screen, so the bank can merchandise offers and new partners without a product release.
White-label app
A complete customer app, ready to brand
Launched by single sign-on from the bank's own mobile or web banking, so the customer never re-authenticates and never feels handed off to a third party. Arabic-first, with right-to-left layout throughout.
Points balance
12,450 pts
≈ SAR 311 · Gold member
Weekend 2× points
Grocery purchase+250
Dining voucher−2,500
Bill payment bonus+500
Rewards catalogue
Vouchers
Filter by merchant or category
Dining credit5,000 pts
Retail voucher2,500 pts
Ride credit2,000 pts
Cinema tickets4,500 pts
Pay with points
At the till
OTP-secured redemption
One-time code4 8 1 2 9 6
Expires in2:00
AmountSAR 125
Points used5,000
What the customer gets
A home screen with balance and currency-equivalent estimate, earned, spent and expiring summary, recent activity and active promotions. A voucher catalogue they can filter, redeem from and revisit with the original code and PIN. A partner directory of every pay-with-points merchant. And an account view with profile, points-expiry schedule and notification preferences.
Notifications
Full multi-channel notification delivery: in-app feed, WhatsApp, SMS, email and push. One-time codes, points-credited confirmations, redemption receipts and two-stage expiry warnings are sent on each relevant event — the cadence regulators expect and customers respond to.
One source of truth
The balance can never drift
Every customer screen reads from the same services and business logic as the Ops Console and the bank's own APIs, so a customer, a service agent and the core system always see the same number.
Built for a regulated industry
Every financial action is reversible, reviewable and attributable
Points are a liability on the bank's balance sheet. The platform treats them that way — with the same controls a core banking system would be held to, and the evidence trail an internal audit or a SAMA examiner will ask for.
Append-only ledger
Every point earned, spent or adjusted is a permanent, immutable record. Nothing is ever overwritten, so any balance can be reconstructed from history.
Maker-checker everywhere
Rule changes, manual adjustments, voucher and merchant approvals and conversion-rate changes all require a second approver — enforced at the database level, not just in the interface.
Full audit trail
Every staff action and every access to profile data is logged, searchable, and viewable as an old-value and new-value difference directly from the Ops Console.
Fraud and risk controls
Automatic flagging of unusual redemption velocity, a compliance review queue, and the ability to suspend a customer's earning or redemption immediately.
Role-based access control
Roles are fully configurable — defined, scoped and combined to match the bank's own operating model, with separation of duties enforced by design. This configuration is a working starting point.
Business user
Rule approver
Compliance officer
Customer service agent
System administrator
User access admin
Channel integration accounts
Points expiry governance
Configurable expiry policy, plus a two-stage advance-warning notification to customers before points lapse — the pattern regulators expect, and the one that avoids complaints.
Data protection
Customer data handling designed against PDPL: lawful basis for profile and behavioural data, retention limits, access logging on every profile view, and deletion that propagates rather than leaving orphaned records in the ledger.
Visibility
Programme health at a glance, with the detail underneath
An executive view for the people accountable for the programme, and a full reporting suite — every figure attributable — for the people who have to reconcile it. The executive dashboard covers outstanding points liability, active and newly enrolled customers, accrual and redemption trends, and tier distribution, filterable across 7, 30 and 90-day windows.
| Report | What it answers |
|---|---|
| Accrual summary | What was earned, by rule, over any period |
| Redemption | What was spent, through which channel and against which merchant |
| Manual adjustments | Every hand-made change, with the agent and the approver named |
| Points expiry | What lapsed, when, and what was warned in advance |
| Spin & Win | Prize distribution and points issued through the wheel |
| Fraud flags | What was flagged, who reviewed it, and how it was resolved |
| Merchant settlement | Gross, commission and net payable per merchant per month, reconciliation-ready |
Attribution
Every number traces back to a person or a rule
Each report drills down to the specific rule, agent or reviewer responsible — what turns a report from a management summary into an audit artefact. All reports are filterable and CSV-exportable.
Meets the bank where it is
No integration path is mandatory
Four independent ways for transactions to reach the platform, all producing exactly the same downstream result. The rule engine and the ledger never know which path a transaction arrived by.
-
Direct streaming feed
The platform's own topic, where the bank integrates its core banking system directly into a real-time stream.
-
CSV batch upload
Where no real-time feed exists. Upload a file and receive a per-row accepted and rejected reconciliation file back, with a reason against every rejected row.
-
The bank's own message broker
Rather than requiring the bank to publish onto the platform's topic, the platform connects out to a broker the bank already owns and exposes.
- Encrypted, admin-managed connection credentials over SASL and TLS
- A business-user-configurable field-mapping tool — no code required to translate the bank's message format into the platform's internal shape
- A live mapping preview, plus a dead-letter and replay queue, so a malformed message is never silently lost — it is captured, reviewable, and re-processable once the mapping is corrected
-
Mobile app and core-system APIs
Signup, status check, redemption and cash-back endpoints for the bank's own channel apps, authenticated through a dedicated OAuth2 client-credentials mechanism entirely separate from staff login.
Also included
Customer profile sync
The same batch and API pattern carries KYC status, contact details and profile updates from core banking into the platform, so customer data stays aligned without manual re-keying.
Engineering posture
Security and concurrency, verified under load
A loyalty ledger under concurrent load is where correctness bugs hide: two approvals racing on the same rule, the same voucher redeemed twice, an OTP used in parallel. These are treated as design requirements and proven under adversarial and load testing rather than assumed in code review.
Encrypted credential storage
AES-256-GCM for every external connection secret held by the platform.
Rate limiting on every endpoint
With tighter limits applied to authentication and credential-exchange routes.
Hardened HTTP surface
CORS locked to known origins and standard security headers applied on every response.
Export injection protection
Formula injection neutralised on every field of every CSV export.
Concurrency-hardened
Race conditions closed at the database, not the application
Load testing surfaces race conditions in maker-checker approval, OTP redemption and duplicate voucher redemption. Each is closed with atomic, database-enforced guarantees rather than application-level checks that fail under contention.
Observability from day one
Structured logging, error tracking and Prometheus-compatible metrics — vendor-neutral, so it works with whatever log, metrics and error stack the bank already runs.
Independent dependency health checks
Database, cache and message broker are each checked separately, so a partial outage is immediately diagnosable rather than a mystery.
Deployment & operations
Containerised, built to run inside the bank's infrastructure
Three deployable services
Containerised backend, Ops Console and Customer Portal, each with its own production build.
A dedicated deployment
One backend serves both web apps and every API surface, deployed for the bank alone — no shared tenancy, and data stays inside the bank's chosen environment.
CI on every change
Automated unit tests, end-to-end browser tests and build verification run on every change.
Six things that rarely come together
Real-time, not batch
Points post in seconds, not overnight.
No-code configuration
Business users own the programme, not engineering.
Meets the bank where it is
Four integration paths, including the bank's own broker with zero-code field mapping.
Compliance-first architecture
Append-only ledger, maker-checker, full audit trail — foundational, not bolted on.
One platform, every channel
Web, mobile SSO, in-store POS and bank APIs share the same rules, balances and history.
Proven under load
Concurrency and security issues found and closed through real adversarial and load testing.
Questions
Answered plainly
Does the platform replace our core banking system?
No. It sits alongside core banking and channel systems and consumes transactions from them. The core remains the system of record for accounts and balances; the platform is the system of record for points, rules and redemption.
Why does real-time accrual matter rather than overnight batch?
When points post overnight, the reward is disconnected from the purchase that earned it, which weakens the behavioural link the programme depends on. Real-time accrual also makes time-boxed campaigns, streaks and instant multipliers possible at all — none of those work on a nightly cycle.
Can business teams change earn rules without engineering?
Yes. Rules are authored in a no-code builder, simulated against sample transaction data before go-live, and promoted through maker-checker approval with old-value and new-value differences retained for audit. A campaign is a rule with an audience, so targeting, earning and reporting all reference the same definition.
How do customers redeem points?
Three ways from a single catalogue and a single balance: merchant-branded vouchers redeemed in the app, pay-with-points directly against a purchase at a partner till secured by OTP, and cash-back converted onto the customer's own card or account through the bank's existing settlement process.
How is the points liability controlled?
Points sit on the balance sheet, so the platform applies core-banking-grade controls: an append-only ledger where nothing is overwritten and any balance can be reconstructed from history, maker-checker enforced at the database level rather than only in the interface, and a full audit trail of every staff action and profile access.
What if we have no real-time feed from core banking?
Four independent integration paths exist and none is mandatory: a direct streaming feed, CSV batch upload with per-row reconciliation, connecting outward to a broker the bank already owns with business-user field mapping, and channel APIs. All four produce the same downstream result.
Does it support Arabic and Saudi regulatory requirements?
The customer application and operations console are built Arabic-first with right-to-left layout. Customer data handling is designed against PDPL, points-expiry policy includes advance customer warning, and voucher and settlement reporting is produced in a form finance and compliance teams can reconcile, including for VAT treatment.
Next step
See it running against your own programme rules
A working session of about ninety minutes is usually enough to configure a live earn rule, run it against sample transactions, and walk the resulting ledger entry, approval trail and report — using your products, your tiers and your terminology.