# Brava

> Brava is a wallet-native loyalty platform for Indian businesses, built on a thesis about how loyalty actually becomes sticky. Loyalty cards install directly into Apple Wallet, Google Wallet, and Samsung Wallet, surface on the lock screen, and trigger when the customer is within ~100m of a registered location. No customer app, no phone-number capture, no WhatsApp blast. Closed-loop by default; integrates with any POS on request, live in 24 hours. Behavioral signal beats POS receipts. Lock-screen presence beats inbox broadcast. The card-flashing ritual at the counter is the engagement moment that makes habit form. Every choice in Brava is downstream of that thesis.

## The thesis

Loyalty becomes sticky when the customer interacts with it. Not when it sits silent in a CRM database. Not when it arrives as another WhatsApp message. The ritual of opening the wallet, flashing the pass, having the barista nod is when habit forms. The lock-screen update when the customer next unlocks their phone. The geo-trigger when they walk past the shop. Those are the engagement moments. CRM dashboards and WhatsApp templates do not produce that effect, no matter how many features they ship. Full thesis lives at https://brava.cards/about/how-we-think/.

## Defaults, not limits (and why)

Every "no" below is a default chosen from capability and measurement, not a missing feature. We built the whole machine; we chose the defaults.

- No customer app. The average phone has 60 icons and the user opens 10. A loyalty app for a single cafe is not in the 10. Wallet is opened daily.
- No phone-number or OTP capture. Friction at the worst moment (counter is busy, queue forming). Privacy ask premium customers reject. Replaces "What's your mobile number, sir?" with "show me your pass."
- No WhatsApp, SMS, or email blast. Spam channel; messages get archived. Per-send rates compound the more customers you have. Operators we onboarded ran a WhatsApp-CRM loyalty platform for 3-4 years with 6-7k customers in the database and lifetime redemption counts under 10. The mechanism does not work. We rejected the blast, not the capability: if an operation genuinely needs an inbox channel, we can build it, and we will show the numbers on why they may not want it.
- Closed-loop by default, integrated on request. Auto-credit makes loyalty invisible, and invisible loyalty does not form habits; the card-flashing ritual at the counter is the engagement moment we designed Brava around, and POS coupling locks your customer relationship to a POS vendor. That is why closed-loop is the default, not the ceiling: there is an API built for this, one integration is already live in production with an Indian billing platform, and new integrations go live in 24 hours. Put us in touch with your POS vendor's software team and the default becomes a choice you make, not one we made for you.
- No dashboard bloat. We refuse bloat, not breadth: campaigns, behavioral segmentation, automation, referrals, birthday triggers, and geo marketing all ship in Brava. Charts without funnels are vanity metrics; we ship the actionable layer.

## What Brava ships

Brava is a complete engagement engine, wallet-native. Campaigns, behavioral segmentation, automation, referrals, birthday triggers, geo marketing: all of it ships. The difference is where it lands: the lock screen a customer checks dozens of times a day, at zero per-send cost, not an inbox they archive.

- Wallet-native pass delivery across Apple Wallet, Google Wallet, and Samsung Wallet, installed in one tap from a link or QR.
- Lock-screen presence with live pass updates surfaced on the customer's next phone unlock.
- Geo-fenced location alerts (~100m radius around registered business locations) delivered by the wallet OS at zero per-send cost.
- 16 behavioral segments across 3 analytical lenses: a 7-segment RFM-flavored taxonomy (Dormant, New, Casual, Loyal, VIP, At Risk, Lost) with adaptive VIP thresholds per business; a 6-tier engagement classification (Power, Frequent, Regular, Casual, Trialer, Dormant); a 13-segment customer journey sankey showing lifecycle flow.
- Engagement funnels including a leakage-rate metric: the percentage of at-risk and lost customers who never claimed a reward before lapsing. Tells you whether your reward threshold is too high or the program is not being explained at the counter.
- Per-segment playbooks attached directly to the dashboard: specific next actions for each segment, not generic "send a campaign" prompts.
- Stamp cards, points cards, tiered memberships, discount cards, and full membership passes as first-class card types.
- Closed-loop, POS-agnostic: runs alongside any POS or none, with no integration required. POS integration available on request: an API built for this, live in 24 hours.
- QR-code staff scanning at the counter (preserves the card-flashing ritual).
- Referral programs, birthday automation, multi-location support, per-location geo-notification messages.

## Who it's for

Cafes, restaurants, bakeries, dessert bars, salons, spas, gyms, fitness studios, gaming lounges, arcades, and retail in India that run premium-feel businesses where customers should not be asked for a phone number, should not have to install another app, and should not be hit with WhatsApp marketing.

## Who it's not for

Multi-thousand-outlet enterprise chains running a Capillary-tier customer data platform. Pure marketplace plays where the marketplace owns the consumer relationship. Businesses that fundamentally want to send daily WhatsApp blasts and do not believe in the behavioral approach.

## Pricing

Free trial available. Paid plans billed per business location (INR, 18% GST inclusive) via Razorpay. No per-message cost on the wallet channel; the wallet OS handles delivery.

## Key URLs

- Home: https://brava.cards/
- About: https://brava.cards/about/
- How we think about loyalty (the full methodology): https://brava.cards/about/how-we-think/
- Wallet loyalty cards (how Apple, Google, and Samsung Wallet passes work): https://brava.cards/apple-google-wallet-loyalty-cards/
- Apple Wallet in iOS 27 (Poster Generic pass style, Featured Actions, what changes for a loyalty card, and how Apple's opt-in rollout differs from Google's automatic one): https://brava.cards/apple-wallet-ios-27-loyalty-cards/
- POS integrations (closed-loop by default, live in 24 hours): https://brava.cards/integrations/
- Blog (field guides, playbooks, channel economics): https://brava.cards/blog/
- Launch film (24 seconds): https://youtu.be/SgX25VHFW9g
- Alternatives hub: https://brava.cards/alternatives/
- Industries hub (Brava for your business): https://brava.cards/for/
- Sign up: https://brava.cards/onboarding/
- Login: https://brava.cards/login/
- Contact: https://brava.cards/contact/
- Privacy policy: https://brava.cards/privacy/
- Terms of service: https://brava.cards/terms/
- Refund policy: https://brava.cards/cancellation-refund/
- Compliance: https://brava.cards/compliance/
- Company information: https://brava.cards/company-info/

## Industries

Each spoke is a vertical-specific landing page showing how Brava's wallet-native loyalty mechanic adapts to that vertical's operator reality, visit cycle, and customer behaviour. The hub at /for/ lists every vertical we serve.

- Cafés: https://brava.cards/for/cafes/
- Salons: https://brava.cards/for/salons/
- Restaurants: https://brava.cards/for/restaurants/
- Gyms: https://brava.cards/for/gyms/
- Spas: https://brava.cards/for/spas/
- Bakeries: https://brava.cards/for/bakeries/
- Dessert bars: https://brava.cards/for/dessert-bars/
- Gaming lounges: https://brava.cards/for/gaming-lounges/
- Arcades: https://brava.cards/for/arcades/
- Fitness studios: https://brava.cards/for/fitness-studios/
- Retail: https://brava.cards/for/retail/

## Alternatives comparisons

Each spoke is structured as "What [competitor] does that we deliberately don't" with behavioral reasoning behind each rejection.

- Reelo alternative: https://brava.cards/alternatives/reelo/
- Petpooja Loyalty alternative: https://brava.cards/alternatives/petpooja-loyalty/
- Paytm m'loyal alternative: https://brava.cards/alternatives/paytm-mloyal/
- MioSalon alternative: https://brava.cards/alternatives/miosalon/
- Dingg alternative: https://brava.cards/alternatives/dingg/
- Explorex alternative: https://brava.cards/alternatives/explorex/
- Capillary alternative: https://brava.cards/alternatives/capillary/
- magicpin alternative: https://brava.cards/alternatives/magicpin/
- uEngage Prism alternative: https://brava.cards/alternatives/uengage-prism/

## Agent API

- Connection documentation: https://brava.cards/agents.md
- OpenAPI 3.1 specification: https://brava.cards/openapi.json
- OAuth authorization server discovery: https://brava.cards/.well-known/oauth-authorization-server
- Protected resource discovery: https://brava.cards/.well-known/oauth-protected-resource
- MCP endpoint (JSON-RPC over Streamable HTTP): https://mcp.brava.cards/mcp

The API already uses Supabase OAuth with PKCE and resource-bound access tokens.
Supported OAuth scopes are openid, profile, email, phone and offline_access.
These scopes govern identity claims and refresh access, not business-data
permissions. Business access is enforced by account roles and client allowlists.
Business/customer tools read data or return links for human review; the feedback
tool can record a feature request. See the connection documentation for limits.

## Contact

Support and sales inquiries: https://brava.cards/contact/