About Rewardfinity

One developer, in Ontario, Canada

Rewardfinity is operated by Anhad Singh, a sole proprietor based in Etobicoke, Ontario, Canada, who also builds it. That is the whole company. Email info@rewardfinity.com or use the contact page. It is worth stating plainly, because the size of the team behind a piece of software changes what you should expect from it, and most vendors leave you to guess.

What it means in practice, in the direction that helps you: there is no sales process. Nothing is gated behind a demo call, there is no onboarding fee, and no one will phone you for having read the pricing page. Support goes to the person who wrote the code, so an answer about behaviour is usually the actual behaviour rather than a summary of it.

In the direction that does not help you, said just as plainly: there is no overnight phone line and no account manager. If your business needs a contracted response time, that is a real requirement and this is not the tool that meets it. Deciding that here costs a few minutes. Deciding it three months in costs a migration.

Why it exists

Most loyalty software is priced and shaped for chains, then sold down to independents with the chain features removed and the chain price only partly removed. The result is a tool a single café uses perhaps a fifth of.

Rewardfinity is shaped the other way around. The assumption is one to a few locations, a counter with a queue at it, and an owner who will configure this themselves on a Tuesday evening rather than schedule an implementation. That assumption is why a customer loyalty program here is something you can have running the same day, and why the settings that matter are the ones a small shop actually changes: the stamp threshold, the earn rate, the minimum spend.

It is also why the staff incentive half exists. Whether a loyalty program works at a counter business is decided by whether someone at the till mentions it during a queue. That is real work, it is invisible in every dashboard, and most loyalty tools recommend running a staff competition while shipping nothing to run one with. Counter actions here are attributed per staff member and convert into a staff-facing reward on an allowance the owner sets.

What ships today, and what does not

This table is the most useful thing on the page. Vendor sites tend to describe planned work in the present tense, which is how you end up buying a roadmap. Every row below is running today, gated behind credentials you supply, or not built — and it says which.

Three rows are the ones most likely to be misread. Google Wallet presentation is a configured path. Apple Wallet cards and updates are available for standalone web programs after program setup. Members must add their card to Apple Wallet. Shopify access is not enabled. Lifecycle automations preserve web push and signed webhook events, and queue consented Resend email plus Twilio SMS or WhatsApp through the first-party dispatcher. Provider submission occurs only when the corresponding operator-enabled provider path is configured. Provider acceptance is recorded separately from delivery, and delivery is claimed only from the provider status evidence available for that channel. Gift-card payouts also record correctly but do not fulfil themselves; a payout sits pending for a human to complete.

To see how this lines up against other tools rather than in isolation, the comparison pages do that directly, and the Shopify integration is documented separately.

How it is priced

Three plan names, and today they mean two different things. A new web workspace starts a 60-day software trial with no card required and no automatic charge. After expiry, new earning, spins and redemptions pause until paid access is verified; your saved records stay available. Provider usage and reward funding are separate. Grow and Scale prices are set for your country, with checkout availability shown in Plan & billing. In the Shopify app, Shopify bills Grow and Scale, and the plans differ only in how many discount rewards can be active — 3 on Free, 20 on Grow, 100 on Scale. The pricing page has the detail.

Prices are indexed to local purchasing power rather than converted from one sticker price, which is why the number you see depends on where you are: US $29, Canada CA$39, UK £24, Australia A$45, €27 in Germany, France, Spain, Italy and the Netherlands, and €20 in Portugal. A shop in Lisbon is not quoted a New York price with the currency symbol swapped. Paid web plans are offered in 36 countries, each in its local currency, and open in each country as its prices go live; until then that country's pricing page says coming soon.

The arithmetic worth doing before you buy anything is cost per member. On the Canadian Grow price, a program with 400 members costs CA$39 divided by 400, or a little under CA$0.10 per member per month. Against that, ask what one additional visit from one member is worth to you. If your average ticket is CA$6, the plan pays for itself at roughly seven extra visits a month across the entire member base.

Full plan detail, and the price in your own currency, is on the pricing page.

What happens to your data

Your member list is yours, and the way to prove that is to describe the exit rather than assert the principle. Member data exports to CSV at any time, and the same public REST API that writes data reads it back out, so a migration does not depend on anyone approving a request.

There is a member export and an anonymize action that removes a member's contact details while keeping the anonymous ledger, an audit log on the plans that include staff roles, and two-factor authentication using TOTP. The privacy policy sets out exactly which fields arrive from a connected store and which are dropped rather than stored, and the security page covers the handling detail.

Questions that are not answered on any of those pages can go to support or info@rewardfinity.com, which reach the developer directly.