- Home
- What's New
- Reward Points for Magento 2
🎯
Feature Spotlight
Overview
26 releases in the last year
Each square is a week. Pick one to jump to its releases.
Less
More
November 2026
Nov 10
3.7.1
Nov 10
Improved
-
⚠️ Database tables now managed by declarative schema — The Reward Points tables are now described in
etc/db_schema.xmlinstead of the old install/upgrade scripts, so on Magento 2.4.7+ with MySQL 8.0.29+ they are created inutf8mb4. On upgrade,setup:upgraderemoves leftovers of the old scripts: the legacy foreign keys on the*_customer_groupand*_websitetables (which could abort the upgrade and broke saving a rule for some websites), the duplicatemst_rewards_tier_websitekey and the old "fulltext index" duplicates, no longer adds a redundant second unique key to the purchase table, and adds report columns missing on stores upgraded from versions before 1.0.42. Stores with a database table prefix keep the keys and indexes they need. Runbin/magento setup:upgradeafter updating. TheInstallSchema/UpgradeSchemaclasses are removed. - "Expire after (days)" explains that changes are not retroactive — The setting's hint now says that points which already have an expiry date keep it, even when you set the value to 0.
-
⚠️ The tier email template ID is now a string in the REST API (
TierInterface::getTemplateId()/setTemplateId()), so values such asnoneor a template code are no longer returned as0.
Fixed
- Partial refunds adjust reward points correctly — A partial refund now takes back exactly the share of reward points earned and restores exactly the share spent, so several partial refunds on one order add up to the full amount. The credit memo totals in the admin show the same numbers.
- Empty reward-points banner no longer shows on product pages — The reward-points notification banner is hidden on a product page when its message has no visible text (for example, an emptied WYSIWYG field), instead of showing a blank banner.
-
Reward-points purchase lookup limited to the shopper's own orders — A signed-in customer can no longer retrieve another customer's order through the reward-points purchase request (
GET /V1/rewards/mine/purchase/:orderId). - Applying points at checkout can no longer change another shopper's address — When points are applied, only the shipping-estimate fields (country, region, postcode, city, street, name, company, phone) are taken from the request, so a crafted request can no longer overwrite another cart's shipping address.
- Reward Points reports respect admin role permissions — Access to the Reward Points reports can now be granted or restricted per admin role.
-
Customer tiers and points estimates in GraphQl are no longer shared between customers —
mstRewardsTiersandmstRewardsEarningEstimateare excluded from the GraphQl page cache, so one customer no longer sees another customer's tier or points estimate when the query is combined with cached fields. - Rules without a display name are hidden in the customer account — Earning and spending rules whose display name was cleared no longer appear as blank lines (or as "[]") on the Reward Points account pages.
-
Filtered REST lists return the right total —
total_countin Reward Points REST list responses now counts only the records matching the filters, not the whole table.
October 2026
Oct 26
3.7.0
Oct 26
New
Remove applied points from a cart in GraphQl
The new
mstRewardsRemovePointsFromCart mutation takes a cart_id and clears the reward points applied to that cart, so a headless or PWA storefront can offer "remove points" next to the existing mstRewardsApplyPointsToCart. Removing points from a cart that has none applied does nothing and returns no error.
New
Points earned for a product in GraphQl
mstRewardsEarningEstimate(productId, options) returns the points the product page badge shows: the base rate for a guest, the rate of the customer's tier when logged in, with the price of the selected customizable options taken into account. An unknown product or option ID returns a translatable GraphQl error.
Improved
- Reward Points now works with Mirasvit Core 2.0.
Fixed
- Saving the Reward Points settings failed with "Invalid file name" — Saving any field in the Reward Points configuration, at any scope, rolled the whole section back with this error because the Rewards Logo image was checked in the wrong folder. Settings now save normally, and uploading, replacing or deleting the logo works as before.
- The Referral Invitation Message never showed on the storefront — The text saved in the admin did not appear in the invitation box on the customer's "My Referrals" page. It now appears, and a message saved before version 3.2.10 (when the setting lived in a different group) is still picked up after the upgrade without saving it again.
- The Points report failed with Mirasvit Core 2.0 — Refreshing the admin Points report now works on stores that use Mirasvit Core 2.0.
- For developers using the referral repository in custom code: saving, loading and deleting a referral no longer fails with a type error, saving returns the referral itself, and loading an unknown ID reports "not found" only in that case instead of for every error.
Oct 21
3.6.0
Oct 21
New
Hyvä support now ships with the extension
The companion package
mirasvit/module-rewards-hyva is gone: the points on product pages, the social share buttons, the "Use points" form in the cart and in Hyvä Checkout, and the customer account pages are now part of Reward Points itself. There is no second package to find and keep in step, and on a Luma store the Hyvä part simply stays dormant. Composer removes the companion package by itself when you upgrade. The "Use points" form in Hyvä Checkout no longer uses its own Magewire component, and magewirephp/magewire is no longer required.
New
GraphQl support now ships with the extension
mirasvit/module-rewards-graph-ql is gone; the mstRewardsTiers query, the mstRewardsApplyPointsToCart mutation and the reward points fields on Cart and Customer used by headless and PWA storefronts are part of Reward Points itself.
New
Reward points on placed orders in GraphQl
customer { orders { items { mstRewardPoints { … } } } } now returns the points spent on each order and the discount they gave, the points earned, and whether and when the earned points become available, so a headless order history can show them. Points given back by a cancellation or refund are subtracted, a cancelled or closed order does not show its promised points as pending, and an order with no points left returns null. A page of orders is loaded in a few queries. Magento 2.3 has no customer.orders; there the same fields are on customerOrders { items { mstRewardPoints { … } } }.
New
Points earned for a product in GraphQl
mstRewardsEarningEstimate(productId, options) returns the points the product page badge shows: the base rate for a guest, the rate of the customer's tier when logged in, and the price of the selected customizable options taken into account. A product that does not exist is a GraphQl error.
Improved
-
⚠️ The
Hyva_MirasvitRewards,Hyva_MirasvitRewardsBehavior,Hyva_MirasvitRewardsCatalog,Hyva_MirasvitRewardsCheckoutandHyva_MirasvitRewardsCustomerAccountmodules are gone, not renamed - You only need to act if you referenced them yourself: in a customdi.xml, a layout file, or a deployment script that enables modules by name. -
⚠️ If you overrode a Hyvä template in your theme, check it - Overrides of the
Mirasvit_Rewards*templates in your theme are still read, but most of those templates are now shared between Luma and Hyvä, so compare your copy with the new one. Four templates the Hyvä package referenced under its own name moved:Hyva_MirasvitRewardsCatalog::pricing/adjustment.phtmlis nowMirasvit_RewardsCatalog::pricing/adjustment.phtml;Hyva_MirasvitRewardsCheckout::checkout/price-summary/total-segments/*.phtmlis nowMirasvit_RewardsCheckout::with the same path;Hyva_MirasvitRewardsCheckout::checkout/cart/wireusepoints.phtmlis replaced byMirasvit_RewardsCheckout::checkout/cart/usepoints.phtml; andHyva_MirasvitRewardsBehavior::js/social.phtmlis gone (the script is nowMirasvit_RewardsBehavior::js/social.js). On Hyvä the cart block now usesMirasvit_RewardsCheckout::checkout/cart/rewardspoints-hyva.phtml, so a Hyvä theme override ofcheckout/cart/rewardspoints.phtmlis no longer read there. An override at an old path is simply not read, with no error to say so. -
⚠️ Reward Points now requires Magento's GraphQl modules -
magento/module-graph-ql,magento/module-customer-graph-ql,magento/module-quote-graph-qlandmagento/module-sales-graph-qlare now Composer dependencies. If your project removes Magento's GraphQl modules (for example with areplacesection in the rootcomposer.json), keep these four. -
After upgrading a Hyvä store, run
bin/magento hyva:config:generateand rebuild your theme's Tailwind CSS. - The social share buttons, the points on product pages, the reward points notification and the tier details popup now use the same lightweight script on Luma and Hyvä.
-
⚠️ Points transactions are now indexed by their code (a new index on
mst_rewards_transaction.code), which speeds up every order lookup of earned and spent points (order pages, the admin order totals, the GraphQl order history) on stores with a long transaction history. -
The reward points notification on product pages is no longer cached separately for every tracking parameter in the URL (
utm_source,gclid, …), so the block cache holds one copy instead of many. - ⚠️ Storefront labels follow one casing style: sentence case for descriptions, title case for buttons and actions. Some phrases changed (for example "Remove auto-applied points" is now "Remove Auto-Applied Points" and "Points Amount to Spend" is now "Points amount to spend"), so your own translations of those phrases need updating.
Fixed
- Hyvä Checkout did not tell the customer about the minimum points to spend - An amount below the minimum was reported as applied without the "Minimum number is X" message, and there was no "Remove auto-applied points" control. Hyvä Checkout now applies points through the same form and messages as the Luma checkout
- AddToAny share buttons never appeared on the Hyvä referral widgets - Luma was unaffected
- The "earn N points" hints on the Hyvä share buttons showed as plain text blocks - They are now hover hints, as on Luma
- The subscribe and unsubscribe links on the Hyvä points history page did not work - They now use the same form as Luma
- Tier names were not escaped on the Luma account Tiers page - in "Your current tier is…", "Earn N to get to…" and the tier details popup
- The Hyvä cart showed "You Earn" only to customers who could spend points - The row waited for a totals refresh that only the "Use points" form or a shipping estimate triggers; it is now there from the first page load
- On phones, a long first or last tier name on the Luma account page no longer sits against the screen edge; it lines up with the page margin
- Partial refunds gave back the wrong number of points - A credit memo restored spent points and took back earned points by its share of the order subtotal. With a spending rule limited to some items, or with points earned on the discounted price with tax, both amounts were wrong (for example 2,995 of 16,500 spent points restored, and 588 earned points taken back instead of about 330). Spent points now follow the refunded items' share of the points discount and earned points follow their share of the earning base; referral rewards are still reversed by the subtotal share, and no empty 0-point "restore" transactions are written
- Customers reaching a behavior rule's daily points limit earned nothing, with no explanation - Once a customer hit the daily limit, further reviews, "email a friend" sends or social shares silently earned nothing, which looked like a broken program. A customer submitting a review now sees a notice, and the points history shows a 0-point "daily limit reached" line for the blocked action
- The entered shipping address was replaced with the customer's default address - When a logged-in customer estimated shipping to a country without regions (for example the UK, Ireland or Hong Kong), the next page load brought back their saved default address and discarded the one they had just entered
- The reward points purchase cleanup cron ran out of memory on large stores - It loaded every row of the purchase table just to count them, which crashed on tables with more than a million rows; it now counts them in the database
- The expiration date entered on an admin transaction was saved wrong - On stores behind UTC the date was stored a day early, so the points expired early; dates in day-first formats (22/10/2026) caused an error, and days up to the 12th had day and month swapped. The date is now read in the admin's locale format and stored as the end of that day in the store's time zone, and an invalid date is refused with a clear message
-
Transaction import could credit or change the wrong customer - A row whose website did not match fell back to any customer with the same email on another website; rows must now name the customer's own website. An update by
transaction_idcould also move a transaction to another customer or change its code; updates now only correct amounts and dates. The "Delete" behavior now only deletes a transaction that belongs to the customer named in the row - Re-uploading the same transaction file credited customers twice - Rows already imported from the same file are now skipped
- Transaction import accepted invalid values - An empty, non-numeric, fractional or out-of-range amount was stored as a wrong number; it is now reported as an error. A file can no longer set internal columns such as used points, activation or expiry flags. A row with an invalid expiration date is now reported and skipped instead of making the whole file fail to import
- Transaction import sent one balance email per row - A file with many rows for the same customer mailed them once per row. Customers now receive one email each, and none are sent when the file updates more than 200 customers
- Admins without the Reward Points transactions permission could import transactions - Access to System ▸ Import was enough to credit points and email customers through the Reward Points transactions import; it now also requires the Reward Points transactions permission
-
Exported transactions could run as spreadsheet formulas - A comment or code starting with
@or a tab was exported as is; such cells are now exported so that spreadsheet apps show them as text - The checkout logo was not installed on stores using remote media storage (S3) - The upgrade failed or skipped the logo; it is now written through Magento's media storage
- The Rewards Logo preview in the admin was broken, and uploaded logos did not show on the storefront - Logos uploaded meanwhile are repointed automatically on upgrade
-
{{store url=""}}in the checkout, notification and earning rule messages now renders the store URL instead of appearing as raw text, on Luma and Hyvä - The account points history now shows "0 spent, N remaining" for points earned after the customer's last spending, instead of hiding the breakdown
- The GraphQl tiers query no longer fails for a customer who has no tier yet
- The Luma social share buttons sit in one row, as on Hyvä
- Hyvä product page: the "earn points" label is shown right under the price, and the bundle "Your Customization" summary shows the points for the configured price and updates with the selected options and quantity
- Hyvä cart and checkout: the checkout message has its variables filled in and is shown inside the rewards box, now in Hyvä Checkout too, and the guest note sits under "Checkout now and earn"
- Hyvä cart: when the minimum points rule changes the entered amount, the points field shows what was actually applied, and the "Use Reward Points" notice folds like the Luma block
- Hyvä account pages: the page title lines up with the content, the tabs form one strip without underlines until hover, and the referral form marks its required fields
Oct 14
3.5.2
Oct 14
New
Choose where a referral link lands
New setting Rewards > Referrals > Referral Link Landing Page: the homepage (as before), the Create an Account page, or a custom page or URL. Sending invited friends straight to sign-up removes a step before they earn the referral reward. Existing stores keep landing on the homepage until the setting is changed.
New
Points expiry can now be set per earning rule: behavior earning rules have a new Expire after (days) field, so, for example, birthday points can expire in 30 days while other points keep the global expiry. Leave it empty to use the global Expire after (days) setting; existing rules are not affected
New
New setting Purchase points expire after (days) (Stores ▸ Configuration ▸ Mirasvit Extensions ▸ Reward Points ▸ General Settings, website scope) for points earned for orders. Leave it empty to use the global Expire after (days) setting
New
New settings in Reward Points ▸ Social Buttons ▸ Display Options: Show Social Buttons block on product page and Show Refer Friends button. The second one hides only the button in the Social Buttons block; the referral program stays active
Improved
-
⚠️ A new nullable
expires_after_dayscolumn is added to themst_rewards_earning_ruletable. Existing rules keep an empty value and use the global expiry
Fixed
- Fixed the expiry column being hidden in the customer's points history when the global expiry was set to 0, even though some transactions had an expiry date (from an earning rule or the purchase points setting)
- Fixed the table of expiring transactions in the points expiry email failing to render on Magento 2.3
-
Fixed Apple Pay checkout failing with a JavaScript error (
undefined is not an object (evaluating 'quote[base_discount_amount]')) when paying with reward points through Braintree builds that expect the quote when collecting cart line items
Oct 2
3.5.1
Oct 2
Improved
- Reward points blocks in the cart, checkout, admin order creation and social share buttons keep working with upcoming Mirasvit Core versions, which no longer ship the Content Security Policy helper these blocks relied on
Fixed
- Fixed the "Send a test digest now" button showing raw internal error text when the digest could not be sent for a reason other than an email delivery failure. It now shows a clear message and writes the details to the exception log; email delivery errors are still shown as before
- Fixed the "Learn more" manual links on the Earning Rules, Spending Rules, In-cart & Account Messages, Tiers, Referrals and Reports admin pages leading to "Page not found"; they now open the current Reward Points manual pages
September 2026
Sep 29
3.5.0
Sep 29
New
Points expiry reminders are grouped per customer: when points from two or more of a customer's transactions are about to expire, the customer receives one email with the total, the earliest expiry date and the list of transactions, instead of one email per transaction. If you customised the Points expire Email template, customers with several expiring transactions now receive the new Points expire email for several transactions template: make your own copy in Marketing ▸ Email Templates and select it in Stores ▸ Configuration ▸ Mirasvit Extensions ▸ Reward Points ▸ Email Settings, or set that setting to "- Disable these emails -" to keep one email per transaction. Setting Points expire Email to "- Disable these emails -" still turns all expiry reminders off
Improved
- Faster product pages when several earning rules are active: a configurable product's child products are now checked once per page instead of once per earning rule
-
⚠️ A new nullable
store_idcolumn is added to themst_rewards_transactiontable, recording the store view in which points were earned or spent. Existing transactions keep an empty value -
⚠️ Removed unused PHP classes that could not work:
Mirasvit\Rewards\Model\Earning\Behaviorwith its resource model and collection (their table never existed),Mirasvit\Rewards\Plugin\DataProviderGroupFilter,Mirasvit\RewardsCheckout\Observer\LockPurchaseOnOrderPlaceBefore, and the earning ruleapplyAll()/applyAllRulesForDateRange()product indexer methods. Check any custom code that references them
Fixed
- Fixed high database load from the rewards cron job on stores with many customers. When an "Inactivity" earning rule was active, the cron checked each customer's last visit with a separate database query, which added up to thousands of queries every run. It now looks up the last visit for all of the rule's customers in one query. Points are still awarded to the same customers as before
- Fixed the balance update email being sent with the wrong store's template and language when a customer earned or spent points on a store view other than the one they registered on
- Fixed expired points occasionally being deducted twice when two runs of the points cron job overlapped
- Fixed transactions activated by the cron job being activated again, with a repeated balance update email, when the job ran more than once in the same process
- Fixed a notification rule limited to certain customer groups being shown to all customers
- Fixed notification rules being displayed in reverse "Sort Order", and cart and checkout notifications appearing on the referral page
- Fixed the "Product Type" condition in spending and notification rules never matching products
- Fixed the "Quantity" condition in spending and notification rules causing an error whenever a rule was checked
- Fixed rule conditions on store-view-scoped product attributes always using the default value instead of the store view's own value
- Fixed a blank page after checkout for orders placed without points; the success page message about spent points is now shown correctly
- Fixed the unsubscribe link in reward emails showing "Page not found" to customers in groups for which the reward points account menu is hidden
- Fixed earning rules and tiers with no points or step configured causing a "division by zero" error or awarding unexpected points
- Fixed the 2 MB size limit for tier logo uploads not being applied
- Fixed warnings when a tier was saved with only some of its fields, for example when uploading a logo or changing its status
- Fixed an error on credit memos where the maximum points refund was not collected
-
Reward Points transaction import: the "Delete" behavior now actually deletes transactions (matched by
transaction_id, which is now required) instead of reporting success and deleting nothing; rows with an empty customer email are reported as errors instead of being silently skipped or merged with neighbouring rows; the "value is required" error message is now translated; and the import no longer lowers a PHP memory limit that is already set higher than 1 GB - Fixed "Activate" mass action in the transactions grid saving an empty activation date
- Fixed "Save and Continue Edit" on an earning rule redirecting to a missing page
- Fixed an error when adding a rule condition without a condition type
- Fixed an error in the admin transactions grid page
- Fixed the time-series report export failing on PHP 8.4 and later
-
Fixed the refunds list API (
getList()) failing with a "Cannot instantiate interface" error
Sep 18
3.4.4
Sep 18
New
Reward Points transaction import can now send the balance update email to customers. A "Send balance update email to customers" checkbox appears in the import options (System ▸ Data Transfer ▸ Import) for the Reward Points Transactions entity; when enabled, each imported customer receives the standard balance update email. Customers who opted out (rewards_subscription = 0) are skipped, and the default (unchecked) behavior is unchanged.
Fixed
- Fix FK crash when building a referral link for an order without a customer
- Drop the productMetadata dependency the fix left dead
Sep 14
3.4.3
Sep 14
Fixed
- A single name/email pair posted as scalars sent no invitation
- Stop loading a customer per spend row in calculateUsedPoints
- Show per-transaction balance and remaining points.
Sep 10
3.4.2
Sep 10
Fixed
- Fixed a backend order paid in full with reward points failing to submit with "The requested Payment Method is not available." When the points covered the entire order total, re-collecting totals on submit double-counted the reward discount on each item, so the eligible amount collapsed, the points spilled onto shipping, the grand total never reached zero and the free payment method was rejected. Reward-discounted items now keep their eligible amount across a re-collect, so a fully points-paid admin order submits correctly.
- Fixed the "Earn N Reward Points" label missing from product and category pages on stores with full page cache or Varnish. If the first visitor to load a page had no earning rule running for them — a guest, or anyone visiting before a scheduled campaign's start date — the label was left out of the cached page and never appeared for anyone afterwards until the cache was flushed by hand. The label is now always prepared on the page and filled in per visitor, so it shows the right amount for each shopper. On top of that, a campaign that starts or ends on a date now takes effect on its own within an hour instead of waiting for the rule to be re-saved, a shopper who becomes eligible sees points on their very next page view, and the per-visitor point total is never reused by a shared cache for a different shopper.
- Reward reports no longer error on a fresh install before the first report data has been generated.
Sep 3
3.4.1
Sep 3
Fixed
- Referral invitations are now deduplicated per inviting customer instead of store-wide, so the "already invited" notice can no longer be used to find out whether an email address is known to the store. The daily limit of 100 invitations per customer is also enforced as the invitations are sent, so a single request can no longer go over the cap.
-
Removed a stray rewards account URL (
/rewards/account/abstractcontroller) that opened an empty rewards account page nothing in the store links to. It now returns a normal 404. - Removed two unused internal lookups on the storefront rewards account and referral pages that fetched a transaction or a referral by id without checking it belonged to the signed-in customer. Nothing in the module used them, and they are gone rather than left as a trap.
- Fixed the Facebook share icon being blocked by the Content Security Policy on stores running another Mirasvit module that whitelists the same address.
August 2026
Aug 25
3.4.0
Aug 25
New
Apply a spending rule automatically
A new "Force spending rule immediately" option on a spending rule discounts the cart with reward points as soon as it qualifies, so the customer no longer has to open the rewards block and click Apply. Two settings go with it: "Points to spend when auto-applied" (spend up to the rule's max-points cap, or only the amount the rule requires) and "Let the shopper undo it in the cart", which shows a "Remove auto-applied points" button in the cart. Removing the points is remembered for the rest of the session, so they are not re-applied when the cart is recalculated. The customer's available balance and the rule's cap are always respected, and an amount the customer types in themselves still wins.
Improved
- Reward email and notification message fields can no longer be used to run privileged template code entered in the admin.
- Reward admin grid filters (customer name, website) now handle filter values safely.
- Reward refund and rule-condition admin screens are now restricted to users who hold the matching reward-points permission.
- Removed an unused referral invite endpoint that could be reached without signing in.
- Reward points can no longer be farmed by reloading or altering social-share links — each share now earns points once per action.
-
⚠️ This release adds new database fields, so run
setup:upgradeafter updating. The hourly report aggregation tables also gain a primary key and are rebuilt automatically on the next aggregation run, so no data is affected.
Fixed
- Fixed checkout breaking for guests on stores protected by HTTP Basic authentication (for example staging sites): on the payment step the rewards block called a customer-only endpoint for everyone, and the resulting error could make the browser drop its saved credentials into a login loop. Guests now skip that call entirely, in both the standard checkout and the Magestore One Step Checkout integration.
- Turning an earning rule on or off now takes effect on product and category pages right away, instead of the "Earn N Reward Points" label keeping its old state on already-cached pages until the cache was cleared by hand.
- Editing a notification rule now refreshes pages that show the notification-rule list widget, instead of serving the old rule text for up to a day.
- Fixed a fatal error on category pages for stores using the Pinterest "Pin it" button.
- Guests who arrive through a referral link keep getting referral credit reliably, including several genuine visitors who share one IP address (office networks, mobile carriers, CGNAT).
- Referral link visits and guest referral sign-ups are now limited to one per visitor and link per hour, so repeated or automated requests can no longer flood the referral table or inflate a link owner's statistics.
- Fixed the hourly reward-points and programme-liability report tables being created without a primary key, which could take a MySQL Group Replication cluster offline and read-only after a database node restart until the tables were fixed by hand.
Aug 6
3.3.32
Aug 6
New
Filter reward transactions by tier downgrade over the API
The rewards transactions REST endpoint (
GET /V1/rewards/customer/:id/transactions and /mine) now accepts a type=tier_down filter, so you can pull just the records where a customer dropped to a lower tier. It combines with the date-range filter, and an unrecognized type simply returns an empty list instead of an error.
New
"Activity Over Time" chart on the rewards report
Daily earned/spent/expired, 30/90/365-day or custom period, period-over-period summary, CSV export
New
Outstanding programme-liability, reworked into its own filter-aware report
New
Weekly email digest of the rewards report
New report_digest config group (enable, recipients, send day/hour, period, "Send a test digest now"), a new cron group rewards_report_digest, and an email template
New
Merchant-configured Custom Behavior Events surfaced as columns in the Reward Points report
Fixed
- Fixed the "points as currency equivalent" amount shown on the product page for spending rules that have a spend-max cap: it was frozen and no longer changed with the product price on low-priced items. It now reflects the real value of the earned points and is correctly limited by the cap.
- Fixed store-view-specific values on earning and spending rules (front-end name, email/history/product messages) overwriting the "All Store Views" value, and clearing a value on one store view wiping it for every other store view. Each scope is now saved and cleared on its own.
- Reward point amounts now display with the correct thousands and decimal separators for each store view's locale.
-
Fixed the store name and other store variables (e.g.
{{var store.getFrontendName()}}) rendering as blank in product-page and notification messages. - Fixed a crash when uploading or editing a reward tier logo on Magento 2.4.9, including a clear error message when the logo file cannot be saved and no longer crashing the edit page when a tier's logo file is missing from disk.
- Fixed transaction export producing an empty file when a Created At / Expires At / Activated At date range was applied — the export now returns the same rows shown in the filtered grid.
- Fixed a checkout error on PHP 8.5 caused by cart items that had not yet been saved.
July 2026
Jul 28
3.3.30
Jul 28
New
Add virtual type=tier_down searchCriteria filter to rewards transactions REST endpoint
Fixed
- Skip quote items with no DB id in CalcPriceService to avoid null array offset (PHP 8.5)
- Fixed checkout failing with a PayPal error when a customer paid with reward points through Braintree and product line items were not being sent — PayPal no longer rejects the order with a "PATCH_VALUE_REQUIRED" (2046) error
- Fix null array offset in Discount::calcPoints when item not yet persisted
- Guard Braintree rewards line item against credit-only PayPal
- Cast monetary_step to float to preserve decimal exchange rates in spending rules
- Clear NoSilentCatchRule: report cron aggregation failure, annotate tier fallbacks
- Tier logo upload/edit fatals on Magento 2.4.9
- Evaluate newsletter subscriber rule condition by subscription status, not row existence
- Restore %1 placeholder in RewardsCheckout "Use %1" translations
- Restore corrupted %1/%2/%3 placeholders in translated values
- Native-language review of restored placeholders (grammar, roles, terms)
- Wrap store in VariableObject for product/notification template vars
- Format reward points with store-view locale separators
- Use earned points (not spend-max cap) for product currency equivalent
- Earning/spending rule store-view fields no longer corrupt scope data
- Transaction export ignores UI component grid filters
Jul 9
3.3.29
Jul 9
New
Added a new reward tier qualification method based on the customer's order count
Fixed
- Tier cron did not process all customers
- Referral link attribution did not work correctly when email confirmation was required
- Referral attribution could fail if the referrer customer no longer existed
- Phantom points notification was sent after newsletter re-subscription
- Expiry default admin notice could not be dismissed
Jul 8
3.3.28
Jul 8
Fixed
- Corrected invalid __1 placeholder to %1 in ja_JP translation "in %1 days" phrase
June 2026
Jun 17
3.3.26
Jun 17
Improved
- Compatibility with PayPal PPCP module
Fixed
- Skip quote items without ID in canProcess to avoid undefined array key warning in Rewards/Model/Total/Quote/Discount.php
Jun 17
3.3.25
Jun 17
Fixed
- Issue preventing access to the checkout page when the minimum order amount validation was enabled.
Jun 5
3.3.24
Jun 5
Fixed
-
Reward points could not be spent when a fixed-price bundle product was in the cart — the "Apply Points" block was hidden at checkout.
RuleQuoteSubtotalCalc::shouldNotCalculate()no longer skips the fixed-price bundle parent that holds the price. -
Fixed three broken
mine/*REST API endpoints.
May 2026
May 26
3.3.23
May 26
Fixed
-
Removed
unserialize()fallback inMirasvit\Rewards\Helper\Serializer. The helper is now JSON-only and marked@deprecatedin favour of\Magento\Framework\Serialize\Serializer\Json. The legacy non-Magento-serializer branch inMirasvit\Rewards\Helper\Jsonwas removed for the same reason.
May 15
3.3.22
May 15
Fixed
- fix: Using null as an array offset is deprecated in customer account rewards history
May 15
3.3.21
May 15
Fixed
- fix: Using null as an array offset is deprecated when add product to cart
May 11
3.3.20
May 11
Improved
- i18n: full localization of admin and storefront strings to 15 locales (ar_SA, de_DE, es_ES, fr_FR, it_IT, ja_JP, ko_KR, nl_NL, pl_PL, pt_BR, ru_RU, tr_TR, uk_UA, vi_VN, zh_Hans_CN)
Fixed
- Transaction activation and expiry are now configured per customer store
May 4
3.3.19
May 4
Improved
- PHP 8.5 compatibility: updated all code to be fully compatible with PHP 8.5, including strict typing and deprecation fixes
March 2026
Mar 24
3.3.18
Mar 24
Fixed
- Show empty status instead of points are expired if all transaction points were used
- Coupon with free shipping was not applied to cart if Rewards earn condition = "coupon used"
- Earned points are not updated on points applying
- Actions conditions were not validated for cart item spending rules
- TypeError: in_array(): Argument #2 ($haystack) must be of type array, null given in Ui/Earning/Form/Modifier/Tier.php
January 2026
Jan 13
3.3.17
Jan 13
Improved
- Tier update cron performance — rewrote tier recalculation to use direct SQL queries and in-memory caching, significantly reducing database load and execution time for stores with many customers
Jan 5
3.3.16
Jan 5
Improved
- Sortable rewards balance column — rewards balance column in the customer admin grid is now sortable and displays as a number
Fixed
- Reward points form now prevents applying or canceling when no points are entered or applied