No POS change
Ready first
Counter flow beside your register
Run QR earning and redemption beside any checkout from a phone, tablet, or browser.
POS-agnostic by design
Keep loyalty portable when checkout tools change.
Start beside the register without replacing it. Move to a direct API, signed webhooks, or an approved POS adapter when the business is ready — they arrive with the Grow plan. The loyalty ledger and customer experience stay the same.
Choose the lightest path
Integrate at your own pace.
The product does not force a small merchant into an enterprise integration project. Each path reaches the same customer, program, redemption, and ledger model.
Grow · sandbox planned
Developer path
Versioned REST API
Send customers, sales, refunds, voids, rewards, and redemption commands through /api/v1.
Grow · signing planned
Event path
Signed webhooks
Receive register events and deliver loyalty changes with traceable retry and replay behavior.
Grow · by approval
Partner path
Isolated POS adapters
Map provider-specific formats at the boundary so reward logic never depends on one vendor.
Delivery channels
Five ways to reach a customer, each priced in the open.
The in-app inbox and push are included on every plan. Campaign email carries an allowance on the paid tiers; SMS is bought as credits on every tier. Whatever the channel, you see what a send will cost before it goes. Consent, quiet hours and frequency caps apply everywhere, including the channels that cost nothing.
In-app inbox
Lands in the customer's wallet, where their card already is. Nothing to install and nothing to pay.
- Included
- Unlimited on every plan
- Add-on rate
- No charge
Push notifications
Reaches a customer who has closed the wallet, so a reminder arrives while there is still time to act on it.
- Included
- 1,000 → 200,000 per month
- Add-on rate
- ₱8 per 1,000
Messaging apps
Viber and WhatsApp, chosen automatically per customer. Cheaper than SMS and better looking, and most people read them sooner. Being connected and not live yet; when it opens the composer will try them before SMS.
- Included
- Not live yet — pay as you send when it opens
- Add-on rate
- From ₱0.42 per message
SMS
The one channel that works on any phone, with no app and no data. Used when nothing cheaper will reach them.
- Included
- Add-on credits, on every plan
- Add-on rate
- ₱0.95 per 160-character segment
Sign-in codes, reward notices and data exports always send, on every plan, and never touch the allowance. The allowance is for campaigns, and only the paid tiers carry one.
- Included
- 1,000 → 10,000 campaigns per month
- Add-on rate
- Add-on bundles
A contract built for recovery
Safe when networks and providers are not.
A loyalty balance is a promise. The integration layer must explain every change, reject accidental duplicates, and recover without asking staff to guess.
Credentials scoped to the whole account, one merchant, one branch, or one terminal
One-time secrets with rotation and revocation
Duplicate-safe sales and redemptions, by idempotency key
Reserve, commit, and cancel redemption states
Immutable adjustments, refunds, and reversals (planned)
Planned quickstart
Record a Philippine sale
POST /api/v1/transactions
Authorization: Bearer sk_live_••••••••
Idempotency-Key: sale_sc_10482
{
"memberCode": "2966093052778",
"branchId": "branch_legazpi",
"amountCentavos": 48500,
"items": 1,
"externalReference": "SC-10482"
}Scoped credentials
Keys can be limited by branch and action.
Signed events
Planned: every event signed with a timestamp, so a copied event cannot be replayed later.
Duplicate-safe
The same idempotency key returns the original result.
Retry evidence
Every attempt keeps status, latency, and request context.
Operational guarantees, with Grow
The fallback is part of the product.
The internet drops
The counter app stores a signed local queue, shows pending status, then reconciles safely when connectivity returns.
A webhook endpoint fails
The worker retries with backoff, records each attempt, and exposes a manual replay after the destination recovers.
A credential may be exposed
An owner rotates or revokes the scoped key while unaffected terminals continue using their own credentials.
A sale is refunded
The ledger appends a reversal tied to the original sale instead of silently rewriting the customer balance.
Clear claims
Preview the setup. Connect any register.
The counter flow works today, on any register, with no integration at all. The API, webhooks and POS adapters below arrive with the Grow plan — and most shops are running a healthy program long before they need them.
Do we need to replace our POS?
No. Begin with the counter flow that runs beside your register, then add a direct connection — an API your register calls, or a webhook, which is your register telling us about each sale as it happens — when it creates enough operational value.
Which POS systems are supported?
KYP Rewards does not maintain per-vendor integrations. Any register that can post sale webhooks, expose a read API, or export sale files connects through one shared event contract, so support does not depend on a vendor partnership.
How are duplicate sales prevented?
Every sale and redemption carries an idempotency key — a unique tag for that one event — so if the same sale is sent twice by accident we recognize it and return the first result, not a second stamp. Every webhook carries a stable event ID for the same reason.
Start with KYP Rewards
Start beside the POS. Integrate when it pays.
Start with the counter flow beside the register you own. Tell us which checkout you use and we will tell you straight whether connecting it is worth your time.