One developer, in Ontario, Canada
Rewardfinity is built and operated by an independent developer based in Ontario, Canada. That is the whole company. 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.
| Capability | Status |
|---|---|
| Points, stamp cards, tiers, referrals, promo codes | Shipped |
| Spin-to-win, for members, the counter and staff | Shipped |
| Raffles and prepaid punch-down cards | Shipped |
| Merchant-owned gift-card vault, encrypted at rest | Shipped |
| QR channel campaigns with budget caps and a kill switch | Shipped |
| Hosted member page, installable app, web push | Shipped |
| Lifecycle automations: birthday, winback, welcome, anniversary, expiry | Web push, signed webhook events, and consented direct-channel queueing |
| Square POS | Native integration |
| Clover, Lightspeed, Loyverse, Zettle, Vend | Via Zapier webhooks |
| Shopify | Live, approved app |
| REST API with idempotent writes, signed webhooks | Shipped |
| Google Wallet presentation | Configured path |
| Apple Wallet presentation | Activation testing; public launch remains dark pending the physical canary |
| Automatic gift-card payout fulfilment | Not shipped — payouts stay pending |
| Staff gift cards | Not shipped |
| Rewardfinity NFC reader | Planned, not purchasable |
| Merchant-composed Email, SMS, or WhatsApp Messages | Operator-enabled provider paths; explicit channel consent and provider status evidence required |
Three rows are the ones most likely to be misread. Google Wallet presentation is a configured path. Apple Wallet remains dark for public launch while activation testing waits on the required physical canary. 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 plans. Free covers up to 100 members with points, one stamp card and one QR campaign. Grow removes the member limit and adds every loyalty type, unlimited QR campaigns, spin and referrals, Shopify and CSV import. Scale adds multi-location, brand channel campaigns, staff roles with an audit log, and priority support.
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, India ₹499, Nigeria ₦9,900, and so on across 36 countries. A shop in Lagos is not quoted a New York price with the currency symbol swapped.
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.
Seven visits, not seven hundred
CA$39 ÷ CA$6 average ticket ≈ 6.5 visits. The bar being low enough to test is the point, not that any given program clears it. Run the division with your own ticket size.
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 GDPR-grade export and anonymize path, 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, which reaches the developer directly.
Questions people ask
Who is behind Rewardfinity?
Rewardfinity is built and run by an independent software developer based in Ontario, Canada. It is not a venture-funded team or a division of a larger company. Product decisions, the code, and support replies all come from the same person, which is worth knowing both because it means direct answers and because it means there is no overnight support desk.
Is Rewardfinity a real company or just one person?
One person, operating a real and live product. The Shopify app is published and approved on the Shopify App Store, the platform has a public REST API with signed webhooks, and a native Square POS integration. Small team and unfinished product are different things, and the capability table on this page is there so you can judge the second directly.
Where is Rewardfinity based?
Ontario, Canada. Pricing is offered in local currency across 36 countries, but the operator is Canadian, and Canadian privacy and anti-spam law applies to how the business contacts people. The privacy policy names the specific data-handling commitments rather than leaving jurisdiction implied.
Can I talk to someone before I sign up?
You can, through the support page, but nothing requires it. There is no demo call, no sales qualification step, and no onboarding fee. The free plan exists so the evaluation can be done by using the product rather than watching someone present it. Most questions are faster to answer by configuring a stamp card than by scheduling anything.
What happens to my data if I stop using Rewardfinity?
You can export member data to CSV at any point while the account is active, and the public REST API reads the same records programmatically, so an export does not depend on a support request being granted. There is also a GDPR-grade export and anonymize path. Check the export before you commit to any loyalty vendor, including this one.
Does Rewardfinity work with Apple Wallet?
The Apple Wallet pass path is built, but public launch remains dark while activation testing waits on the required physical canary. Google Wallet is a separate configured path. If Apple Wallet is the reason you are evaluating loyalty software, treat it as unavailable for public launch until that canary passes.
Start on the free plan and judge it by using it.
Up to 100 members, points and one stamp card.