The answer depends on whether you buy or build the platform, how rewards are funded and how much operational work remains with your team. A useful budget separates implementation, subscription, customer value and internal ownership.
A realistic loyalty budget includes implementation, recurring platform fees, reward or customer-value funding and internal resource. Businesses often compare supplier subscriptions while leaving their own product, engineering, finance, support and marketing costs outside the model.
That produces an incomplete decision. The right comparison is the total cost of launching and operating the programme over an agreed period, normally at least 12 to 24 months.
Choose gift card purchasing, a hosted white-label rewards programme or rewards embedded through an API. The right scope depends on your audience, customer proposition and technical requirements. Your tailored proposal sets out fees, funding, commission and commitments before you decide.
Pricing can change and Enterprise requirements vary, so use the live Spendstream pricing page as the authoritative source before making a budget decision.
The platform fee does not necessarily include the economic value given to each customer. A programme may fund discounts, cashback, entries, points or another benefit from merchant commission, from the client’s own budget or through a mixture of both.
Where customer value is taken from merchant commission, that value is applied before the remaining Net Commission is shared under the agreed Spendstream plan. The amount available varies by merchant, category and transaction.
White-label reduces the amount of client-side product and engineering work because Spendstream provides the customer interface and maintains the platform. The client still needs resource for branding, legal and commercial review, access decisions, testing, launch communications and ongoing programme ownership.
For many businesses, this creates a more predictable cost than an internal build. The subscription should still be assessed alongside the internal time required to launch and promote the proposition.
API fees cover access to Spendstream’s reward infrastructure, but the client funds its own customer-facing build. That can include discovery, UX design, front-end and back-end development, wallet logic, analytics, accessibility, security review, QA and continuing maintenance.
The cost depends on the existing product and the number of journeys required. Developers should review the API documentation before estimating effort.
A full internal build adds supplier sourcing, contracts, integrations, balance management, merchant updates, fulfilment operations, affiliate tracking, reconciliation and support tooling to the customer-interface project. It can be appropriate where loyalty is strategically central, but it should not be treated as a one-off software project.
The build-versus-white-label guide sets out those responsibilities in more detail.
Build a first-year budget from your tailored proposal: add any setup fee, recurring fees for the agreed period, expected usage or payment charges, customer reward funding and internal costs. Compare API and hosted delivery using the same audience, feature scope and time horizon.
The same business should then add its own programme manager, legal and compliance time, technical work, marketing, customer support and any reward value funded outside merchant commission. This is an illustration, not a forecast of revenue or return.
Qualifying activity may generate commission. Any end-user reward, client commission share and Spendstream share are defined in your agreed commercial arrangement. Model this separately from fixed fees, and allow for validation, reversals and the timing of supplier or affiliate payments.
Revenue depends on eligible active customers, transaction frequency, average order value, merchant rates and reward design. Do not use a best-case adoption assumption to justify fixed programme costs.
Ask whether the quoted price includes merchant access, the customer interface, integrations, reporting, fulfilment, reconciliation, support, fraud controls, catalogue updates and ongoing product improvements. Clarify implementation scope and any usage or transaction charges.
A cheaper subscription may create a more expensive total programme if the client must fund missing technology and operations. Conversely, a managed service only represents value when the organisation has a clear audience and a credible plan to drive use.
| Cost or arrangement | What to confirm |
|---|---|
| Implementation | Branding, integration, configuration and any one-off fee |
| Recurring and usage fees | Subscription, transaction or usage charges and the agreed commitment |
| Purchasing and payments | Prepaid funding or an agreed managed end-user payment journey; payment costs |
| Rewards and commission | End-user value, client share, qualification and settlement rules |
| Operations and support | Reporting, reconciliation, maintenance and support responsibilities |
Compare like-for-like scope and include your internal costs. Find your starting solution or request a tailored proposal. Applicable fees are quoted excluding VAT.
Use the solution finder to identify a starting point, then request a tailored proposal. Your proposal sets out applicable fees, funding, commission and commitments before you decide.
Not automatically. Customer value may be funded from merchant commission, the client budget or a combination, depending on the programme.
White-label normally requires less client-side product and engineering work, while API delivery gives your team control of the customer experience. Compare the quoted fees and your internal launch and ongoing costs for each route.
Yes, eligible activity can generate commission, but the outcome depends on adoption, transaction behaviour, rates and customer-value design.
Internal product time, technical maintenance, marketing, customer support, finance reconciliation and the opportunity cost of engineering resource are commonly omitted.
A bespoke build gives your business complete control, but the visible interface is only a small part of a functioning rewards product. Compare the full technology, supplier and operational workload before deciding.
Give customers useful savings across everyday spending through one managed platform. Spendstream combines digital gift cards, cashback and affiliate offers, delivered through a fully branded white-label service or embedded using our API.
Both routes can provide access to the same underlying Spendstream reward infrastructure. The real decision is who builds and maintains the customer experience, how quickly you need to launch and how much control your product team needs.
Book a 30-minute founder demo to see the white-label and API routes.
