The Shared Wallet Concept.

The core insight: Customers sign up once (or join as a guest if enabled) and can collect loyalty programs from any participating business on the same installation. Each business sees only their own data. This is shared infrastructure, not a public directory.

The Problem with Traditional Loyalty Platforms

Most loyalty software forces a choice:

Option A: Isolated installations. Each business gets their own separate system. Customers create new accounts everywhere they go. Setup costs multiply with every client.

Option B: Public directories. Businesses appear in a searchable listing. Looks empty with three entries. Creates unwanted brand associations. Competitors refuse to participate. Cold-start problem kills adoption.

Both options have clear limitations. Reward Loyalty takes a third approach.

How the Shared Wallet Works

One Account, Many Programs

When a customer signs up at any participating business, they create a single account. That account works everywhere:

• Coffee shop gives them a stamp card
• Gym next door has a points program
• Restaurant downtown uses the same system

The customer signs in once (email OTP by default; password optional). Their wallet can contain cards from every business they've visited, with no separate accounts per business.

Complete Partner Isolation

Each business, called a Partner, operates in total isolation:

When a partner logs into the Partner Dashboard, they see their own data within the platform's interface. The platform carries the branding of whoever operates the installation: your logo, your domain. The data is theirs: their cards, their customers, their transactions. No indication that anyone else exists.

The server enforces this isolation (tenant scoping + authorization checks), not the UI alone. Partners cannot access each other's data.

Why This Matters

The shared wallet solves problems that kill other loyalty solutions:

No cold-start problem. There's no directory to look empty. Each business is pitched as their own system—because from their perspective, it is.

No brand conflicts. A fine dining restaurant and a fast-food chain can use the same installation. Neither sees the other. Neither needs to approve the association.

Reduced signup friction across businesses. If a customer already has an account on your installation, they won't need to create a new account when they later discover another participating business.

One installation, unlimited partners. You manage one server, one database, one update process. Your clients each get a complete loyalty solution.

Two Levels of Branding

Branding splits into two layers, and each serves a different audience.

Platform Branding (Yours)

The installation owner (you, the script purchaser) controls the platform's look and feel:

• Logo in the header
• Platform name and domain

This is customizable without touching code. When partners log in, they see your platform. When customers use the app, they see your brand.

Card Branding (Theirs)

Each partner brands their own loyalty cards:

• Card images and backgrounds
• Reward descriptions and terms
• Business name and contact info
• QR codes and promotional materials

A partner can have multiple cards, each with different designs. A coffee shop might have a stamp card with one look and a points-based loyalty card with another.

The Result

Platform operators build a cohesive product identity. Partners customize what matters to their customers: the cards themselves.

The Agency Advantage

If you're selling loyalty programs to multiple clients, this architecture is what makes the business model work.

The Pitch That Converts

You approach a high-end restaurant. You show them:

• A professional partner dashboard with your platform branding
• Their loyalty cards featuring their logo, colors, and design
• Their customers, their analytics, their control
• No mention of anyone else

They see a premium loyalty solution. They agree to a monthly fee.

Next week, you approach a local gym. Same pitch, same platform interface, different login, different cards with the gym's branding.

Both businesses are on your single installation. Both log into the same platform (with your branding), but each sees their own data and manages their own branded cards. The platform is yours; the loyalty programs are theirs.

If instead you showed that restaurant a public directory containing a kebab stand and an auto repair shop, they would decline. No one wants to be entry three on a sparse directory, associated with businesses that don't match their market position.

The Math Works

Consider the traditional model:

• 10 clients × separate installations = 10 servers to maintain, 10 updates to apply, 10 databases to backup, 10 SSL certificates to renew

Now consider the shared wallet:

• 10 clients × one installation = 1 server, 1 update, 1 database, 1 SSL certificate
• Same monthly revenue, fraction of the overhead

With an Extended License, you can run unlimited partners on a single installation. The Partner Permissions system lets you control exactly what features each partner can access.

The Customer Experience

The shared wallet creates value for every participant.

Zero-Friction Engagement

A customer signs up at a coffee shop. Standard process: email, verification code, done. They start collecting stamps.

A month later, they visit a gym that uses the same platform. They see a QR code at the counter and scan it.

If they're already signed in on that device, they go straight to the gym's loyalty program.

If they're not signed in, they can sign in (or sign up) with an email OTP code, or use guest/anonymous mode if that installation has it enabled.

Either way, it's one account for the platform. The gym becomes another card in the same wallet.

The Practical “Network Effect”

Reward Loyalty doesn't pool points across businesses. It does reduce signup friction:

• Customers keep one wallet and can add many business programs to it
• Businesses benefit when customers already have an account on the same installation

Exact overlap depends on geography and customer behavior, so we avoid publishing fixed “recognition rate” percentages.

What Customers See

The Member Dashboard shows customers all their collected cards in one place:

• My Cards — Every loyalty card, stamp card, and voucher they've collected
• Points balances — Tracked separately for each business
• Available rewards — What they can redeem where
• Transaction history — Full activity log

Customers never see which businesses share infrastructure. They experience a unified wallet that works everywhere.

Why No Directory?

Some users ask: "Why can't customers search for participating businesses? Why no public listing?"

Reward Loyalty doesn't include a public directory. The absence is a design choice, and it protects your sales pitch.

The Empty Directory Problem

A directory with three listings looks worse than no directory at all. It signals:

• "This platform is new/struggling"
• "Nobody important uses this"
• "Should I really trust my customer data here?"

You need critical mass before a listing adds value. Reaching critical mass is nearly impossible when early entries make you look amateur.

Brand Association Risk

Businesses protect their image carefully. A luxury spa doesn't want to appear alongside a discount oil change shop. A vegan restaurant doesn't want to be listed next to a steakhouse.

With partner isolation, you can onboard any business without asking permission from existing partners. Nobody needs to approve who else uses the platform.

But You Can Curate a Homepage

This doesn't mean partners must remain invisible to customers. With the Smart Wallet homepage layout, you can selectively feature partners:

• Admin grants permission — You decide which partners can publish to the homepage
• Partners choose what to show — Those with permission decide which programs to display
• You control associations — Only partners you've approved appear together

The difference from a directory:

You get partner isolation by default for clean sales pitches, with the option to showcase a curated network when it benefits the customer experience.

Partners Still Prefer Isolation by Default

Agencies selling to multiple clients tell us they prefer the current model. Their clients don't want to know who else uses the system. The invisibility is a feature.

When you've curated high-quality partners who complement each other, the homepage becomes a strength, showing customers the network value of one account across multiple businesses.

How Customers Find Businesses

Without a central directory, how do customers discover that a business participates?

The same way loyalty has always worked: the business tells them.

• QR code at the counter
• Sign by the register
• Link in their email footer
• Widget on their website (Shopify widget available)
• Card in the receipt

When a customer scans that QR code:

1. If they're already signed in on that device → instant access
2. If they're new (or signed out) → quick signup/login via OTP (or guest mode, if enabled)
3. Either way → connected to that business's loyalty program

Each business promotes their own program to their own customers. They don't rely on platform discovery. They own their customer relationships.

Use Cases This Architecture Enables

Agency / Marketing Consultancy

Sell loyalty programs as a managed service. Each client gets a Partner account. You maintain the installation and charge monthly fees.

How it works:

• One Extended License installation
• Create a partner for each client
• Set permissions and limits per partner
• Bill clients through your existing invoicing process

Why the shared wallet helps: Clients in the same area share customers. If a customer already joined one client on your installation, they won't need to create a second account to join another client's program.

Multi-Brand Business

Run several brands that shouldn't cross-promote. Different price points, different target markets, different identities.

How it works:

• One installation
• One partner per brand
• Separate logins, separate dashboards
• Customers can use one account across brands (if they discover them independently)

Why the shared wallet helps: Your brands stay distinct while customers benefit from account portability. Someone shopping at your premium boutique can use the same login at your outlet store without you explicitly connecting the brands.

Franchise Network

Corporate provides the loyalty infrastructure. Franchisees manage their own programs.

How it works:

• Corporate controls the installation
• Each franchisee gets a partner account
• Networks group franchisees by region
• Standard loyalty card templates with local customization

Why the shared wallet helps: A customer who visits any franchise location can use the same account everywhere. Same wallet, one login, with balances tracked per location and program.

Business Association / Shopping District

Provide loyalty as a member benefit. Shopping centers, downtown associations, cooperative groups.

How it works:

• Association operates the installation
• Member businesses get partner accounts
• Optional shared branding ("Downtown Rewards")
• Billing through existing membership dues

Why the shared wallet helps: Customers shopping the district create one account and can add many member-business cards to one wallet. The association can demonstrate this convenience to attract new members.

White-Label SaaS Provider

Offer "your own" loyalty platform to clients who never know about Reward Loyalty.

How it works:

• Your branding on the platform itself (customize branding)
• Your domain, your identity
• Partners create their own branded loyalty cards within your platform
• Build billing on top (though see our notes on this)

Why the shared wallet helps: Customers see a unified experience across all your clients. Partners each manage their own branded cards. You benefit from reduced signup friction across your client network.

Technical Foundation

The shared wallet is possible because of how Reward Loyalty handles data:

Multi-Tenant Architecture

Every piece of partner data is scoped:

graph LR
    A["Partner"] --> B["Clubs"]
    B --> C["Cards"]
    C --> D["Transactions"]
    B --> E["Staff"]
    A -. "relationship,\nnot ownership" .-> F["Members"]

When a partner queries data, they only receive records linked to their account. The database contains all customers, but each partner sees only their own customers' interactions.

Member Relationships, Not Ownership

Customers ("Members") exist at the platform level, not the partner level. When a customer collects a card from a business, a relationship is created:

• Customer exists in system
• Customer collects Card A from Partner A
• Customer collects Card B from Partner B
• Partner A sees customer with Card A data only
• Partner B sees customer with Card B data only
• Customer sees both cards in their wallet

Neither partner "owns" the customer. They each have a relationship with that customer for their specific loyalty program.

Privacy by Design

• Partners cannot enumerate customers they don't have relationships with
• Transaction history is scoped to the viewing partner
• Analytics aggregate only the partner's own data

See User Roles for the complete permission structure.

Common Questions

"Can partners share customers or run cross-promotions?"

Not by default. The isolation protects partners from unwanted associations. If you want to enable specific cross-promotions between partners, you'd need custom development. This isn't a built-in feature.

"What if two partners have the same customer?"

Both partners see that customer in their customer list, but each sees data relevant to their own loyalty program. Partner A sees their transactions and points balance. Partner B sees different data. Neither knows the customer visits the other.

"Can I see all customers across the installation?"

Administrators can. Partners cannot. The Admin dashboard provides platform-wide analytics and customer data. Individual partners only see their slice.

"Is this the same as multi-tenancy?"

Yes. The shared wallet is our application of multi-tenant architecture to loyalty programs. Each partner is a tenant with isolated data access sharing common infrastructure.

"What about GDPR and data privacy?"

Customer data belongs to the platform, with access controlled by relationships. When a customer deletes their account, their data is removed from all partner relationships. Individual partners can remove their relationship with a customer without affecting other partners.

Summary

The shared wallet is the architecture that makes Reward Loyalty work for agencies, franchises, associations, and anyone serving multiple businesses.

Next Steps

• Who Is This For? , business models and monetization strategies
• Homepage Layout , choose Smart Wallet, Showcase, or Portal presentation
• Platform Branding , customize your installation's look and feel
• User Roles Explained , understanding partners, staff, and customers
• Partner Permissions , controlling what each partner can access
• Networks & Organization , grouping partners for management
• Try the Demo , see partner isolation in action