Points and rewards engine: build your own or use an API-first platform
Resources · Guide
A points and rewards engine is the system that applies earning rules, keeps each member's balance, validates redemptions and connects to the POS, the app and the CRM. You can build it in-house or use an API-first, white-label SaaS loyalty platform that already has those pieces and integrates through an API.
- RulesEarning and caps
- BalancesDouble-entry ledger
- RedemptionSingle-use QR coupon
The member
- ExpirationBy lot
- API and webhooksREST and MCP
- White-label SDKYour app and web
- 0 msPurchase arrives
- ~150 msRule applied, balance updated
- AfterWebhook to the CRM
Customer impact · SKY Plus case
SKY Plus, SKY Airline’s program, runs on Qurable: points, missions, three tiers and partners on a single platform.
SKY Plus is one of our cases: we also run programs in retail, fuel, restaurants and banking.
- 1.7M+Active membersIn the SKY Plus program
- 70+Integrated partnersHotels, dining and airport services
- 210KFlights a monthProcessed by the platform
- 50KDaily transactionsWith program partners
Key takeaways
- A points engine in production is rules, balances with accounting, secure redemption, integrations and maintenance.
- An API-first, white-label platform brings those pieces and keeps your brand in front.
- With Qurable, a program reaches production in 1 to 3 months.
Two paths
Build the engine or use a platform.
A points engine looks like a balance table and a few rules. In production it is also accounting, secure redemption, traffic peaks, integrations and maintenance. The question is how much of that your team wants to build and run.
| In-house engine | API-first platform | |
|---|---|---|
| Time to production | A development, testing and audit project before the first member | 1 to 3 months to production, with the Qurable team |
| Rules | Every new rule is a development task and a deploy | Configured from the console or through the API, with priorities and caps |
| Balances and accounting | You design the ledger, expirations and reconciliation | Double-entry ledger with lots, expirations and real-time liability |
| Redemption and fraud | Coupons, reversals and POS validation still to build | Single-use QR coupon, dynamic QR every 30 s, reversals and holds |
| Integrations | Every connection is coded by hand | REST API, signed webhooks, white-label SDK and MCP server |
| Brand and data | Full control of the code | Your brand in your app and web; runs in Qurable's cloud or yours |
| Maintenance | A dedicated in-house team, forever | The platform keeps evolving; your team focuses on the experience |
The pieces
What a points engine has to solve.
Four groups of pieces every engine needs in production, whether you build it or not. They also work as a checklist to evaluate a platform.
Earning rules
How many points each purchase earns by amount, product, channel or store, with priorities and caps.
Tiers and missions
Tiers calculated on your own base, missions and games with prizes and attempt caps.
One effects engine
Rules, journeys, missions and trivia trigger the same effects: points, coupon, badge, email, WhatsApp or webhook.
Double-entry ledger
Every movement is an entry: nothing is edited, everything can be explained and reconciled.
Lots and expirations
Every credit is a lot with issue and expiry dates; redemptions consume lots FIFO, FEFO or LIFO.
Available, held and issued balance
With real-time liability by currency, country and store for finance.
Identification at the till
Members identify with a QR code that changes every 30 seconds or with an Apple or Google Wallet pass.
Single-use coupon
Each redemption creates a QR coupon that is validated once at the point of sale.
Reversals and holds
Full or partial authorize and capture, full and partial reversals, and release of expired holds.
REST API
Everything the console does can be done through the API: members, rules, balances, redemptions and reports.
Signed webhooks
Every program event goes out in real time to your CRM, data warehouse or marketing stack.
White-label SDK
Components for your app and web, with your brand: members never see Qurable.
MCP server
AI agents operate the program with the same permissions and approvals as a user.
Hidden costs
What you don't see when you build your own engine.
The first version usually works. The problems show up with volume, with finance and with the first rule change.
| Problem | What it takes |
|---|---|
| Finance can't explain the points liability | One entry per movement and real-time liability that reconciles with the books. |
| Traffic peaks on key dates | An engine proven at volume: Qurable processed 17.3 million journeys on a peak day. |
| If the engine doesn't respond, the till gets stuck | The program never blocks the sale, and earning is queued. |
| Account takeover and duplicate redemptions | Dynamic QR, single-use coupons and account claim with a one-time passcode (OTP). |
| Changing expiration affects points already issued | Versioned rules: the change applies to new points and issued points keep what was promised. |
| Marketing depends on developers for every campaign | A console where the program team configures rules, campaigns and redemptions without code. |
What to ask for
What to ask an API-first platform.
If you use a platform instead of building, these questions separate a real API from a console with an API.
A complete, documented API
Everything in the console available through the API, with signed webhooks for every event.
Real white-label
SDK and components with your brand for app and web; members don't see the vendor.
Access for AI agents
An MCP server with the same permissions and approvals as a user.
An auditable ledger
Double entry, lots with expiry dates and liability that finance can reconcile.
Where it runs
SaaS with a shared or dedicated tenant, or in your company's cloud, on any provider and region.
Your future exit
Daily export of members, balances and movements to your data warehouse.
With Qurable
An API-first, white-label points engine.
Qurable comes with the engine's pieces already built: rules, balances in a double-entry ledger, redemption and expirations. It integrates through a REST API, webhooks and MCP, carries your brand with an SDK for your app and web, and runs on any cloud.
Rules and program
Earning, tiers, missions, games and redemption, configurable from the console or through the API.
See Engagement & LoyaltyBalances with accounting
Double-entry ledger with lots, expirations, reversals and real-time liability.
See the points ledgerAt checkout
The benefit is decided inside the authorization, in about 150 ms, and the sale is never blocked.
See loyalty at POS and checkoutYour brand, your cloud
White-label SDK for your app and web; SaaS or in your own cloud, on any provider and region.
See the platform
Questions
What teams ask before building a points engine.
For product, engineering and loyalty teams deciding whether to build or use a platform.
It's the system that applies a loyalty program's earning rules, keeps each member's balance, validates reward redemptions and connects to the POS, the app and the CRM. It can be built in-house or be a loyalty platform that integrates through an API.
Building it means solving earning rules, balances with accounting, expirations, redemption, fraud prevention and integrations, and maintaining all of it over time. An API-first platform like Qurable already has those pieces, integrates through a REST API, webhooks and MCP, and carries your brand with a white-label SDK. With the Qurable team, a program reaches production in 1 to 3 months.
Everything you can do in the console you can also do through the API: create members, define rules, check balances, redeem and read reports. At Qurable that includes a REST API, signed webhooks for every program event and an MCP server for AI agents.
It's a platform that runs behind your brand: members use your app or website and never see the vendor. Qurable offers white-label SDKs and components for front ends, and companies like Pomelo and Credit Union Travel offer rewards to their customers with Qurable behind them.
Yes. Qurable is used as SaaS with a shared or dedicated tenant, or deployed in your company's cloud. It runs in containers, on any cloud provider and region.
With the Qurable team, the program reaches production in 1 to 3 months. Rules, balances, redemption and integrations already exist: the work is configuring them for your program and connecting your systems.
Last reviewed
Further reading
Keep reading before you decide.
The pages that show each piece of the engine in detail.
- ModulePoints program
Rules, tiers, missions, games and redemption.
- ModulePoints ledger
Lots, expirations, reconciliation and the liability of every point.
- ResourceLoyalty RFI, RFP and RFQ checklist
The questions to evaluate platforms.
- ResourceLoyalty migration
How to move a running program without losing balances.
- PlatformThe loyalty and engagement platform
Five modules that share the same profile, rules and ledger.
Are you about to build your own points engine?
In a 45-minute technical session we show you the API, the ledger and the white-label SDK applied to your program.