No POS change
Ready first
KYPStamping sidecar terminal
Run QR earning and redemption beside any checkout from a phone, tablet, or browser.
Start beside the register without replacing it. Move to a direct API, signed webhooks, or an approved POS adapter when the business is ready. The loyalty ledger and customer experience stay the same.
The product does not force a small merchant into an enterprise integration project. Each path reaches the same customer, program, redemption, and ledger model.
Ready first
Run QR earning and redemption beside any checkout from a phone, tablet, or browser.
Developer path
Send customers, sales, refunds, voids, rewards, and redemption commands through /api/v1.
Event path
Receive provider events and deliver loyalty changes with traceable retry and replay behavior.
Partner path
Map provider-specific formats at the boundary so reward logic never depends on one vendor.
Messaging runs on named providers, not a black box. Every plan includes a monthly allowance per channel; past it you pay the add-on rate. Consent, quiet hours, and frequency caps apply on every channel including the free ones.
KYPStamping wallet
Delivered inside the customer's KYPStamping wallet. No provider fee, fair-use policy applies.
Firebase Cloud Messaging
Firebase charges nothing to deliver; the rate covers orchestration, scheduling, and abuse prevention.
Amazon SES
Covers domain reputation, suppression lists, complaint handling, templates, and delivery logs.
Semaphore
Carrier cost is roughly ₱0.56 ex-VAT per segment. The margin covers multipart messages, provider failover, and payment fees.
Your own provider account
Priced as pass-through rather than an unlimited promise, because the provider bills per conversation.
A loyalty balance is a promise. The integration layer must explain every change, reject accidental duplicates, and recover without asking staff to guess.
Planned quickstart
POST /api/v1/transactions
Authorization: Bearer sk_test_••••••••
Idempotency-Key: sale_sc_10482
X-Merchant-ID: mrc_sweet_crumbs
{
"external_transaction_id": "SC-10482",
"customer_phone": "+639171234567",
"branch_id": "br_legazpi",
"amount": 48500,
"currency": "PHP"
}Scoped credentials
Keys can be limited by branch and action.
Signed events
Timestamped HMAC blocks replay outside the allowed window.
Duplicate-safe
The same idempotency key returns the original result.
Retry evidence
Every attempt keeps status, latency, and request context.
The sidecar stores a signed local queue, shows pending status, then reconciles safely when connectivity returns.
The worker retries with backoff, records each attempt, and exposes a manual replay after the destination recovers.
An owner rotates or revokes the scoped key while unaffected terminals continue using their own credentials.
The ledger appends a reversal tied to the original sale instead of silently rewriting the customer balance.
The demo shows how provider adapters will be configured. It does not represent a commercial partnership or live connection before provider approval.
No. Businesses can begin with the KYPStamping sidecar counter flow, then add a direct API or supported provider adapter when it creates enough operational value.
The frontend demonstrates the intended adapter setup. A production connection still depends on documented provider APIs, authorization, commercial approval, and conformance testing.
The planned FastAPI contract requires idempotency keys for transaction and redemption commands, stable event IDs for webhooks, and duplicate-safe worker processing.
Explore the complete credential and webhook setup in the business demo, or tell us which checkout tools your merchants already use.