Website profiles · Technology insights · Alternatives

99minds.io

Unify your promotions across eCommerce and in-store. Manage loyalty, gift cards, store credit, referrals & more to drive repeat purchases and increase LTV.

Paid content
Visit website
Profile views 21 Outbound visits 41 Normal
99minds Full homepage screenshot

At a glance

Category
Shopping
Language
English
Paid-content signal
Paid contentObserved
Registered
Unknown
Hosting
CloudflareInferred
HTTPS certificate trusted
PassedObserved
Last updated

Website review

This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.

What is 99minds?

99minds is a retention and promotions platform for omnichannel brands. Its focus is on turning one-time buyers into repeat customers by combining gift cards, store credit, loyalty programs, memberships, referrals, coupons and wallet passes in one system that works across both online stores and physical retail locations. The tagline on the site, "Go Beyond Sales. Build Purchase Habits.", captures the intent: it is less about acquiring a single transaction and more about the mechanics that bring customers back.

What it actually does

The product line maps to common retention jobs:

  • Gift cards — issue and manage them across e-commerce and stores, including multi-currency support.
  • Store credit — a way to handle returns and refunds without sending money out of the ecosystem.
  • Loyalty programs — points or reward structures designed to encourage long-term repeat purchasing.
  • Memberships — paid or tiered programs that convert casual buyers into committed ones.
  • Referrals — a managed program for customer-driven acquisition.
  • Coupons — bulk, dynamic and personalized campaigns.
  • Wallet passes — push rewards to Apple and Google wallets so they are visible at the moment of a repeat purchase.
  • Automated workflows — rules that trigger gift card, store credit or coupon actions without manual work.
  • Multi-store rewards — one balance that works across stores, brands and channels.

Who it suits

The clearest fit is a retailer or DTC brand that sells through more than one channel — say a Shopify store plus a physical shop — and has outgrown handling gift cards, returns credit and loyalty in separate tools. The omnichannel angle matters most when a customer's balance or rewards need to work in both places. A single-channel brand with simple needs may find a narrower loyalty app sufficient.

A practical next step

If you are evaluating it, start with the specific problem you are trying to solve rather than the full feature list. For example: "Our returns process refunds cash and we lose the customer" points to store credit. "We want in-store rewards to match our online program" points to multi-store rewards and wallet passes. Then check the 99minds pricing page and book a demo to confirm how the pieces are bundled, since the value depends heavily on which modules you actually switch on.

How does 99minds help increase customer lifetime value for omnichannel brands?

99minds increases customer lifetime value by tying together the tools that bring shoppers back—gift cards, store credit, loyalty, referrals, memberships and wallet passes—and by letting a single balance or reward work across online and in-store channels. The goal is not one more sale but a repeatable purchase habit.

The retention loop it supports

  • Gift cards give a reason to return and are issued for both e-commerce and physical retail.
  • Store credit turns returns into future purchases instead of lost revenue.
  • Loyalty programs reward repeat buying over time.
  • Referrals and cashback bring in new customers while encouraging existing ones to come back.
  • Memberships convert casual buyers into committed ones.
  • Wallet passes push rewards into Apple or Google wallets, so the next purchase stays visible.
  • Multi-store rewards let one balance work across every store, brand and channel.

The practical effect is that a customer who buys once online can redeem a reward in a physical store, or vice versa. That consistency is what makes an omnichannel brand feel like one brand rather than separate shops, and it is usually what turns a single transaction into a relationship.

A concrete scenario

A shopper buys online, keeps the item, and earns loyalty points. Later they return a different item and choose store credit rather than a refund. Because 99minds supports multi-store rewards, that credit is usable in-store, where they also redeem a wallet pass coupon. Each step gives them a reason to come back without a new discount campaign. Over a year, that pattern raises per-customer revenue more reliably than one-off promotions.

How to judge whether it fits

If your priority is… 99minds is a strong fit when…
Fewer lost returns You want returns converted into store credit
Repeat purchases You need loyalty and wallet rewards working together
Online + physical stores You need one balance across channels
Global selling You need multi-currency gift cards
Less manual work You want automated workflows for gift cards, credit and coupons

A useful next step is to map your current customer journey and identify where repeat purchases drop off—after a return, after a first order, or between online and in-store. Then check the specific 99minds product pages for gift cards, store credit and loyalty to see which gap each one closes. For broader context on retention platforms, you can compare approaches at Shopify or review loyalty benchmarks from Emarsys.

Can 99minds integrate with my existing eCommerce platform and in-store POS system?

Yes. 99minds is built around omnichannel retention, so its stated purpose is to connect promotions and customer data across eCommerce and physical stores. Its product set includes gift cards, store credit, loyalty, coupons, memberships, referrals, automated workflows, multi-currency gift cards, wallet passes and multi-store rewards, all presented as working across online and in-store channels.

What that means in practice

The evidence points to channel-level integration rather than a single-platform tool. For a retailer, the useful question is not simply "does it integrate?" but which systems it can talk to and what data flows between them.

  • eCommerce platform: 99minds would need to connect to your storefront so gift cards, store credit, coupons and loyalty balances appear at checkout and in customer accounts.
  • In-store POS: The same balances and promotions should be redeemable at the point of sale, which is what makes it omnichannel rather than just online.
  • Shared customer identity: Loyalty and rewards only work across channels if the same customer is recognised online and in store.
  • Wallet passes: Rewards sent to Apple or Google wallets can be used in store without staff looking up an account.

A useful comparison

Need What to check with 99minds
Online checkout Whether your eCommerce platform is a supported integration
In-store redemption Whether your POS can validate gift cards, store credit and loyalty
Unified customer view How customer records are matched across channels
Multi-store operation Whether one balance works across brands and locations
Automation Which events trigger gift card, credit or coupon workflows

Next step

Before booking a demo, list your exact eCommerce platform and POS system, then ask 99minds directly whether both are supported and how the connection is maintained. The site lists an integrations section and API documentation, so those are the two places to confirm technical fit. If your POS is older or closed, ask how redemption is handled at the counter, since that is usually the hardest part of an omnichannel setup.

What pricing plans does 99minds offer for small businesses?

99minds does not publish named pricing tiers with fixed rates on its site; the pricing page is the place to confirm current plans and any free or trial options before committing. See 99minds for the product lineup and Pricing for plan details.

For a small business, the practical question is not the sticker price but which modules you actually need. 99minds bundles several retention tools that can be adopted separately or together:

  • Gift cards, including multi-currency and omnichannel issuance
  • Store credit for returns and exchanges
  • Loyalty programs and memberships
  • Coupons, referrals and automated workflows
  • Wallet passes for Apple and Google wallets
  • Multi-store rewards with one balance across brands and channels

How to decide

A single-location shop that mainly wants to convert returns into future purchases can start with store credit and gift cards. A brand with an online store plus a physical location gets more value from omnichannel gift cards and multi-store rewards, because one balance works across channels. If repeat purchase frequency is the weak point, loyalty and wallet passes matter more than coupons.

What to check before choosing

Ask the vendor directly about transaction fees, the number of stores or users included, and whether loyalty, referrals and wallet passes are separate line items. Pricing that looks low per month can become expensive once you add modules, so compare the total for the features you will realistically use in the first year.

A useful next step: list the two or three retention behaviors you want most, such as more repeat visits or fewer refunds, then request a demo and ask which plan covers exactly those features.

How do I set up a loyalty program using 99minds?

Setting up a loyalty program in 99minds means configuring how customers earn and redeem rewards, then connecting that program to the places they already shop — your online store and your physical locations. The platform groups loyalty alongside gift cards, store credit, referrals, memberships and coupons, so the practical starting point is deciding which of those mechanics you actually want to run before you touch any settings.

What the setup actually involves

  • Choose the reward mechanic. Points-based loyalty, cashback, store credit, referrals and memberships are listed as separate products. Pick the combination that matches your margin and your average order value; running all of them at once on a small catalogue usually creates confusion at checkout.
  • Decide the earning rules. Points or cashback per unit spent, per category, or per campaign. The platform advertises bulk, dynamic and personalised coupons, which is where promotional bonuses and multipliers typically live.
  • Decide the redemption path. Rewards can be spent as store credit, as a coupon, or pushed to a customer's Apple or Google wallet as a wallet pass. Wallet passes suit repeat local shoppers; coupon codes suit one-off campaigns.
  • Connect your channels. Multi-store rewards let one balance work across stores, brands and channels, which matters if you sell online and in person and want a single loyalty identity.
  • Automate the lifecycle. Automated workflows handle gift card, store credit and coupon events, so birthday bonuses, post-purchase points and win-back credits run without manual issuing.

A concrete scenario

A retailer with one online store and two physical shops wants repeat visits rather than one-off discounts. They enable loyalty points on every purchase, let customers redeem as store credit, and issue a wallet pass so the balance is visible on the customer's phone. A shopper who buys online can spend the balance in a shop, and the multi-store rewards setting keeps that balance consistent. Referrals are added later as a separate acquisition channel rather than mixed into the launch.

Deciding between loyalty and cashback

Mechanic Best when Trade-off
Points loyalty You want repeat purchases over time Rewards feel abstract unless the balance is visible
Cashback You want an immediate, easy-to-understand incentive Can train customers to wait for discounts
Store credit You process returns and want to keep the revenue Only useful if customers return to buy again
Memberships You want predictable recurring revenue Requires a clear, ongoing benefit to justify the fee
Referrals Your customers talk about you unprompted Slow to scale if the audience is small

A useful next step

Map one full customer journey on paper first: how someone earns, where they see the balance, and how they spend it. Then open the pricing page at 99minds to confirm which products and channels your plan covers, and book a demo if you need the multi-store or wallet pass setup walked through against your own store configuration.

What are the benefits of using 99minds' digital wallet pass for repeat purchases?

99minds' wallet pass feature is designed to put rewards and balances directly into customers' Apple or Google wallets, so the incentive to return lives on the customer's phone rather than in an inbox or an app they have to remember to open. The company describes the intended outcome as increased repeat purchases, with rewards sent straight to those wallets.

What the wallet pass actually does

According to the page, the wallet pass sits alongside the rest of 99minds' retention stack — gift cards, store credit, loyalty, coupons, memberships, and referrals — and is positioned as a way to "increase repeat purchases by sending rewards straight to Apple/Google wallets." A related capability, multi-store rewards, lets one balance work "across every store, brand, and channel," and the platform markets a unified balance across online and in-store.

Practical benefits for a repeat-purchase goal

  • Reduced friction at redemption. A pass that already sits in a native wallet avoids the download-an-app or dig-out-an-email step at the moment of purchase.
  • Top-of-mind presence. Wallet passes can surface via notifications and location prompts, which is useful for short purchase cycles — coffee, groceries, quick-service food, beauty replenishment.
  • One balance, multiple channels. If a shopper earns in-store and redeems online (or vice versa), a shared balance removes the "which account was that on?" problem that kills repeat visits.
  • Stacking with other programs. Because gift cards, store credit, and loyalty all live in the same platform, rewards can be issued from any of those programs into the same pass.

Who benefits most

Omnichannel retailers with a physical footprint and a reasonably frequent purchase cycle get the clearest gain, since wallet passes are strongest when the customer is already out and about. Pure-play ecommerce brands with long consideration cycles will see less lift from the wallet channel itself and more from the underlying loyalty or store-credit mechanics.

A concrete scenario

A three-location pet supply retailer issues store credit for a return instead of a refund. That credit lands in the customer's Apple Wallet. Two weeks later, near a store, the pass surfaces; the customer redeems the credit on a repeat purchase of food. The retailer keeps the revenue and gains a visit it might otherwise have lost to a card refund.

How to decide

Test the wallet pass against your existing email or SMS reward delivery for one cohort over 60–90 days. Track redemption rate, repeat purchase rate, and time-to-second-purchase. If your customers are already heavy mobile wallet users and your purchase cycle is under a month, the case is usually strong; if your cycle runs to quarters, prioritise the loyalty and store-credit logic first and treat the wallet as a delivery layer.

As a next step, review the platform's integration list and confirm your ecommerce stack and POS are covered, then check 99minds pricing before committing to a plan. For broader context on loyalty mechanics, Shopify documents common retention patterns for omnichannel merchants.

Related questions

More questions →
What Is AI Programming and How Are Developers Actually Using It?

AI programming is the practice of using machine-learning models to generate, complete, review, or test code inside a developer's existing workflow. It covers everything from a single-line autocomplete suggestion in an IDE to a chat assistant that explains an unfamiliar function to an autonomous agent that opens a pull request on its own. The practical dividing line is not the model but the level of human oversight: the more a tool acts without review, the narrower the tasks it should be trusted with.

The four things AI actually does in a codebase

Most day-to-day use falls into a few recognizable activities:

  • Completion — predicts the next line or block as you type, based on the file and surrounding context.
  • Generation — produces a function, class, config file, or migration script from a natural-language description.
  • Explanation and review — summarizes what a piece of code does, flags suspicious patterns, or suggests a refactor.
  • Testing and debugging — writes unit tests for existing code, proposes fixes for a failing test, or traces a stack trace back to a likely cause.

These are not separate products so much as separate modes. The same assistant that autocompletes a loop can also be asked to write the test for it.

Tool categories and where each fits

Category Typical form Best for Main trade-off
IDE copilot Inline suggestions in the editor Boilerplate, repetitive patterns, unfamiliar syntax Suggestions arrive without context about your architecture
Chat-based assistant Side panel or separate window Explaining code, drafting a design, debugging a stack trace You must paste or describe context manually
Autonomous agent Runs commands, edits files, opens PRs Multi-file changes, dependency upgrades, test scaffolding Highest blast radius; needs the tightest review

The categories overlap, and many tools now span more than one. The useful question is not which category is best but how much of the change you are willing to accept without reading it line by line.

What a realistic workflow looks like

A common pattern, for example when adding a new API endpoint:

  1. Describe the endpoint in a comment or chat prompt — method, path, expected input and output.
  2. Let the assistant draft the handler and the data model.
  3. Read the draft and correct the parts that assume an API or library version you don't use.
  4. Ask the assistant to generate tests for the happy path and at least one failure case.
  5. Run the tests, then review the diff as you would any teammate's pull request.

The assistant compresses the first draft; it does not remove steps 3 and 5. Teams that skip the review step are the ones that report the worst outcomes.

Where it breaks down

The limitations are consistent enough to plan around:

  • Hallucinated APIs. Models invent function names, parameters, and library methods that look plausible and compile-fail or, worse, silently do the wrong thing.
  • Insecure suggestions. Generated code may interpolate user input into queries, disable certificate checks, or hardcode credentials because the training data contained those patterns.
  • Licensing and provenance. Suggestions may closely resemble licensed source; teams need a policy on what is acceptable to commit.
  • Data privacy. Pasting proprietary code into a hosted assistant may send it to a third party. Check whether your tool runs locally, offers an enterprise tier with data controls, or is approved for your codebase.
  • Stale knowledge. Models have a training cutoff and will confidently describe an older version of a framework.

None of these make the tools unusable. They make verification mandatory.

How to verify AI-generated code

Treat every suggestion as an untrusted contribution:

  • Compile and run it. A suggestion that doesn't build is a cheap failure; catch it before review.
  • Check every external call. Confirm the function exists, the signature matches, and the version is the one you depend on.
  • Read for security. Look specifically at input handling, authentication, secrets, and anything touching the network or filesystem.
  • Test the edges. Ask for failure cases, not just the happy path, and add the ones the model missed.
  • Keep the diff small. A 20-line suggestion is reviewable; a 400-line agent-generated refactor is not, at least not in one pass.

How teams adopt it gradually

The lowest-risk entry point is tasks where a mistake is cheap and visible: writing tests for existing code, generating documentation comments, scaffolding a config file, or translating a snippet between languages. From there, teams typically move to in-editor completion for routine code, then to chat-based assistance for debugging and design questions. Autonomous agents that modify multiple files tend to come last, and usually behind a branch-and-review gate rather than direct commits.

The pattern that holds up: start where you would notice an error immediately, expand only after the review habit is established, and keep a human accountable for anything that reaches production.

Website Overview

Page metadata, canonical configuration and social previews work together to provide more consistent search and sharing presentation.

Domain and Registration

Unknown

DNS and Email

Nameservers are provided by Amazon Route 53, indicating managed DNS hosting. MX records point to the Google Workspace email service. SPF and DMARC are configured. DKIM status is unknown. TXT records include verification markers for Google, Meta. Such markers may also remain after a service stops being used. The lowest observed DNS TTL is 300 seconds.

TLS and Certificates

The public key uses EC with 256 bits. The server supplied a complete certificate chain. No organization name is present in the certificate; the available fields are consistent with domain validation. The certificate was issued within the Google Trust Services cloud or CDN ecosystem. The certificate's total validity is about 90 days, consistent with a short renewal cycle.

HTTP and Browser Security

The response lacks these common security headers: HSTS. No X-Powered-By header was found, reducing one common source of backend fingerprinting information. The cf-ray response header indicates a CDN or caching proxy in the delivery path. No obvious internal addresses or debug information were found in the headers. The Server header identifies cloudflare without an exact version.

Technology Stack Analysis

The public page identifies Alpine.js, Google Tag Manager, Intercom, Cloudflare without precise versions, leaving fewer clues for version-specific scanning.

Search and Social Sharing

Open Graph is partially configured; og:type is missing. Twitter Card metadata is configured. JSON-LD includes Organization data, helping describe the organization as an entity. The title has 51 characters, within a common display range. A meta description is present, with 155 characters.

Hosting and Email

DNSAmazon Route 53
HostingCloudflare
EmailGoogle Workspace
Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) United States flagUnited States Inferred 216.24.57.16

Registration details

RDAP / WHOIS

Unknown

DNS records

DNS

TypeNameValueTTLPriority
Agcp-us-west1-1.origin.onrender.com.cdn.cloudflare.net216.24.57.16300—
Agcp-us-west1-1.origin.onrender.com.cdn.cloudflare.net216.24.57.18300—
MX99minds.ioaspmx.l.google.com36001
MX99minds.ioalt1.aspmx.l.google.com36005
MX99minds.ioalt2.aspmx.l.google.com36005
MX99minds.ioalt3.aspmx.l.google.com360010
MX99minds.ioalt4.aspmx.l.google.com360010
NS99minds.ions-1511.awsdns-60.org172800—
NS99minds.ions-1727.awsdns-23.co.uk172800—
NS99minds.ions-190.awsdns-23.com172800—
NS99minds.ions-581.awsdns-08.net172800—
TXT99minds.ioanthropic-domain-verification-jjqp1g=NC8nzc80k6eMgislcG2pdxf353600—
TXT99minds.iofacebook-domain-verification=28sxkkq8teky2qrlzmqtfyp1lu2czv3600—
TXT99minds.iogoogle-site-verification=plINb-fh1SCEx-_X8fyJdK4YaBmQsz3XUSQGMZh8gh83600—
TXT99minds.iohubspot-developer-verification=NGE0ODI2ZjctY2E1Mi00ODAzLWJiOWYtZGQ0OTU4ZGRlM2Nh3600—
TXT99minds.iopostman-domain-verification=5fd2e9bdcb5f571c0ea4d1c67fdad7ffcc6b807e43c0e631f0ab3d26d0d61393f0779b833b85335ecd311e81216cbfa58b65b90f012c9373cdef3117ec402abf3600—
TXT99minds.iov=spf1 include:_spf.google.com include:mailgun.org include:amazonses.com include:transmail.net.in include:zcsend.in ~all3600—
CNAMEwww.99minds.iowww-99minds-io-astro.onrender.com3600—
DMARC_dmarc.99minds.iov=DMARC1; p=reject; rua=mailto:[email protected]; pct=100; adkim=s3600—

TLS and certificates

TLS / SSL

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subjectwww.99minds.io
IssuerGoogle Trust Services
Valid until2026-11-13T23:54 · Remaining when checked: 32 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

HeaderValue
content-typetext/html; charset=utf-8
cache-controlpublic, max-age=0, s-maxage=300
servercloudflare
content-security-policyframe-ancestors 'none'; object-src 'none'; base-uri 'self'; upgrade-insecure-requests
x-frame-optionsDENY
x-content-type-optionsnosniff
referrer-policystrict-origin-when-cross-origin
permissions-policycamera=(), microphone=(), geolocation=(), payment=(), usb=()

Identified technologies

Alpine.jsGoogle Tag ManagerIntercomCloudflare

Pages, Search and Sharing

Meta descriptionUnify your promotions across eCommerce and in-store. Manage loyalty, gift cards, store credit, referrals & more to drive repeat purchases and increase LTV.
Canonical URLhttps://www.99minds.io/
LanguageEnglish (default)
Twitter Cardsummary_large_image
All bots 1 allowed · 0 disallowed
  • Allow/
pinterestbot 0 allowed · 0 disallowed

User reviews (0)

  • No reviews yet.