Open Devdocs VS Walletfy

Walletfy's answer:

Walletfy started from a simple observation: paper loyalty cards get lost, damaged, or forgotten, and most small businesses have no real CRM to know which customers are coming back, which are slipping away, and when to act. Instead of building another app nobody installs, the idea was to use the wallet apps already on every smartphone — Apple Wallet and Google Wallet — as the front-end, and build a lightweight CRM behind it that any local business could set up in minutes, without hiring a marketing team or learning complex software.

Walletfy's answer:

Walletfy turns physical loyalty stamp cards into digital cards that live directly inside Apple Wallet and Google Wallet — no app download required. But the real differentiator is the CRM layer behind it: every scan feeds customer data into a dashboard that automatically segments customers as new, active, loyal, VIP, at-risk, or churned. From there, businesses get automated win-back campaigns, birthday messages, location-based proximity notifications, and marketing tools — all without needing a marketing team or separate CRM software. For larger operations, Walletfy Club scales the same engine to retail chains and large-scale events, with flexible pricing per card and per location.

Walletfy's answer:

Most loyalty card tools either require customers to download a separate app (which most never do) or only digitize the card without giving the business any real customer intelligence. Walletfy is built as a CRM first, loyalty card second: it automatically tracks customer behavior, segments them by engagement level, flags who's at risk of churning, and triggers automated campaigns to bring them back — all powered by data collected every time the wallet card is scanned. It also scales beyond single-location small businesses through Wallet Club, serving multi-branch retail chains and one-time large events with usage-based pricing.

Walletfy's answer:

Walletfy serves two segments. The core product targets small and medium-sized local businesses with recurring customers — coffee shops, barbershops, nail salons, beauty centers, padel clubs, and similar retail or service businesses — that want CRM-level customer insight without the cost or complexity of traditional CRM software. On top of that, Wallet Club serves larger operations: retail chains with multiple branches, conferences, weddings, and large-scale events that need to issue thousands of digital cards at once, with custom pricing per card and per branch.

Walletfy's answer:

Node.js, Express, and TypeScript power the backend, with PostgreSQL as the database via Prisma ORM. The frontend dashboard is built with React and TypeScript. Wallet passes are generated using Apple PassKit and Google Wallet APIs, with Apple Push Notification service (APNs) for real-time pass updates. Payments are processed through Payphone, and the infrastructure runs on DigitalOcean with PM2 for process management.

Walletfy's answer:

Walletfy is currently working with small and medium-sized businesses across Ecuador, including coffee shops, barbershops, and beauty salons. As an early-stage platform, customer case studies will be published as the user base grows.