Skip to main content

​
Implemented in the development environment

The configured dev backend supports consumer sign-in and joining, browser memberships and QR identity, merchant setup, stamps/redemption, referral rewards, saved branding, member and outlet reporting, published listings, team access and multiple brands. Production rollout and authenticated end-to-end verification are separate.

​
Additional gates and known boundaries

​
Final reward: Reset / No reset

The merchant choice for what happens after the final reward is claimed is implemented. Reset restarts at the first active reward with zero stamps; No reset completes the card and blocks further stamps and stamp-reward claims after the final redemption. Reaching the goal alone does not complete the card. Completed cards remain complete after later configuration changes. Owners and Managers can also pause reward collection when stock runs out without stopping stamp earning or extending existing reward deadlines.

​
Slide approval and timed reward QRs

The counter approval tutorial and customer claim tutorial describe the development implementation: four-checkpoint sliding, a non-drag alternative, optional sounds, single-use reward QRs valid for up to 10 minutes, and earned-reward deadlines. Production requires a coordinated backend and consumer/merchant rollout. These guides do not establish that the updated flow is already live. The account menu, animated dashboard, stamp cards and phone screens on public pages are demonstrations. Entering details in a signup preview is not a saved profile, opening a sample card is not joining, and a notification illustration does not mean a push message was sent. Activities and Live view are implemented in app code: searchable audit history and a store globe with checks every 15 seconds while visible. This is not an instant stream or customer-location tracker. Demo feeds are static; authenticated deployment verification is separate. For an account-specific problem, use Help. Do not share an Owner’s login or assume a successful preview is a saved transaction.

​
Branding and hosting

The product is Kardy, using getkardy.com as its chosen public domain. The merchant workspace uses merchants.getkardy.com; documentation is intended for docs.getkardy.com. These configured destinations do not establish that DNS, hosting, auth redirects or email delivery have been activated. Kardy’s logo pairs the outlined wordmark with a slightly enlarged card mascot on its right. Merchant, Network and Documentation labels retain their divider and small, spaced lettering. The main site background stays white, with pink and violet accents. Merchant-owned logos and card colours stay separate from Kardy’s branding.