Solution · Service providers
Operate hosted loyalty access for client businesses.
The service provider owns and operates one licensed installation, then gives client businesses scoped access. Hosting, billing, onboarding, security, and support stay with that provider.
- Buyer
- Hosted service provider
- Client purchase
- Scoped service access
- Operator duty
- Infrastructure through support
Short answer
Productize access to an installation you operate.
This model fits a service provider that packages hosted access to one Reward Loyalty installation for separate client businesses. The provider buys the license, owns the installation, hosts and maintains it, configures registration and a billing provider when needed, defines permissions, onboards businesses, trains client leads, and supplies first-line support. Each client configures or approves its programs, trains staff, supports its customers, and accesses only its business relationship and program records. Administrators retain installation-wide access, while the member controls global account and privacy actions; controller and processor roles belong in the client contract. The service is hosted by the buyer, not by Reward Loyalty, and the license does not permit source redistribution or a sublicense of the application.
Decision criteria
Build the service boundary before the signup flow.
Self-registration and billing controls can support a hosted offer. They do not supply infrastructure, customer acquisition, onboarding, support, or a service-level commitment.
Service shape
Choose a repeatable hosted offer with clear eligibility, configuration, access, onboarding, support, change, suspension, export, and exit rules.
Acquisition path
Use operator-created accounts, self-registration, manual billing, or a configured payment provider only when that path matches the commercial and support model.
License and capacity
Operate client access within one licensed installation. Plan a separate installation and license when isolation, geography, ownership, or a client contract requires another production deployment.
Buyer fit
Choose it when hosted access is the productized service.
The provider needs a technical operation and a client-success function, not just a sales channel.
Fits a repeatable tenant offer
Client businesses share a supportable signup, configuration, permission, billing, training, and exit path that the provider can describe without custom consulting each time.
Fits an operator with production ownership
The provider can run hosting, email, backups, monitoring, security, updates, payment-provider configuration, incidents, and customer support.
Choose the reseller model for high-touch delivery
The reseller Solution fits a managed engagement where the operator configures and runs much of the client program. This page owns productized hosted access and account administration.
Choose the agency model for bespoke delivery
The agency Solution fits broader strategy, design, integration, and client-service projects that do not reduce to one repeatable hosted-access offer.
Choose managed SaaS when operation is unwanted
A vendor-operated platform fits better when the buyer does not want to own infrastructure, releases, billing integration, first-line support, or service incidents.
Service model
Separate software controls from the service you must build.
A tenant signup screen is one part of a commercial hosted operation.
Access and plans
The provider defines which businesses may register, which permissions apply, how trials or approvals work, and what happens when access changes. Plan contents and defaults must come from current configuration, not static sales copy.
Billing provider
The provider may configure the maintained manual or online billing paths that fit its market. It owns payment-provider accounts, credentials, taxes, invoices, disputes, reconciliation, and customer communication.
Client service
The provider writes onboarding, training, support hours, incident communication, change requests, data handling, offboarding, and any service-level terms in its own customer agreement.
License boundary
Clients buy hosted access and operating service. A separate installation requires its own license, and clients do not receive rights to publish, share, resell, sublicense, or redistribute the application source.
Responsibility
Make the provider accountable for the shared service.
The client should know which team owns every step from signup to recovery.
Service provider
Buys the license, owns the installation and commercial offer, configures tenant access and billing, operates production, trains client leads, and supplies first-line support.
Client business
Approves program economics and terms, configures or requests programs, assigns and trains staff, fulfils rewards, and answers customer questions about its business offer.
Customer data
The provider and each client define controller and processor roles, access, consent, retention, export, deletion, subprocessors, incidents, and what happens to records when the client leaves.
Product support
The provider reproduces and diagnoses application issues before using the maintained product-support route. Its client support promise and infrastructure response remain outside product support.
Implementation
Prove the full account lifecycle before marketing the service.
Provisioning is not complete until suspension, export, and exit also work.
-
1
Design the offer and contract
Define the buyer, included configuration, permissions, billing path, support, data roles, acceptable use, change policy, cancellation, export, deletion, and separate-installation cases.
-
2
Prepare and brand production
Configure infrastructure, domain, mail, scheduled work, storage, backups, monitoring, security, update procedure, installation identity, business branding rules, and source-change ownership.
-
3
Configure account administration
Set registration and approval behavior, current plans and permissions, billing-provider settings, notification routes, operator roles, and the support path clients will see.
-
4
Run the lifecycle test
Create a client, configure a program, assign staff, process customer activity, change access, test payment failure, export scoped data, resolve support, close the client, restore a backup, and rehearse an update.
Day-to-day operation
Operate the service as a product with named queues.
Routine account work and production work need different owners and evidence.
Client lead
Manages approved business settings, programs, staff, customers, content, reports, and support tickets within the permissions the provider grants.
Client staff and customers
Staff performs supported service actions and escalates business exceptions to the client lead. Customers use the wallet and contact the business or provider through the published route.
Service operation
The provider handles onboarding, account state, billing reconciliation, permissions, plan changes, support, incidents, client communication, and offboarding across the tenant base.
Technical operation
The provider monitors hosting, mail, queues, storage, backups, integrations, security, and releases. It tests role isolation and client workflows before every material change.
Buying checklist
Inspect the operation behind the hosted-service headline.
A viable service needs evidence for both the client experience and the provider workload.
Tenant and permission model
Inspect administrator, manager, partner, staff, and member access; client isolation; exports; support; billing state; suspension; and tenant exit with representative accounts.
Brand and white-label scope
White-label relevance: Central to the buying decision. Map installation identity, client business branding, wallet presentation, public URLs, domains, email identity, templates, locale presentation, and any source changes. Do not assume every surface changes through settings.
Commercial and license model
Read the maintained terms for one-installation rights, source modification, separate installations, support scope, and redistribution restrictions. Put the hosted-service promise in the provider contract.
Source-owned case
Choose source-owned software when deployment control, service continuity, inspectable tenant boundaries, and owned brand or integration changes justify operating production. Choose vendor-managed SaaS when those benefits do not justify the service team.
Complete operating cost
Use maintained pricing for the license, then add infrastructure, mail, backups, monitoring, security, payment fees, onboarding, support, account management, integration, source work, incidents, and updates.
Product and operating limits
Sell hosted access without redistributing the application.
- Reward Loyalty is not the managed host, merchant acquirer, billing operator, implementation team, training provider, first-line support desk, or service-level guarantor for the provider’s clients.
- SaaS administration controls do not create a market offer, tax process, client contract, support organization, automated implementation, or integration catalogue.
- One licensed installation can serve separate businesses under the maintained terms. A separate production installation needs a separate license, and source redistribution remains restricted.
- Brand settings cover defined installation and business surfaces. Deeper removal, domain behavior, or product changes can require scoped source work that the provider must maintain.
Implementation guides
Use current documentation for changing details.
Requirements, interfaces, settings, limits, and release behavior belong in the maintained product documentation.