A customer returns an order, accepts store credit, and later buys from another store view. The balance, tax treatment, refund history and payment remainder all need to agree. Choosing a Magento store credit extension therefore starts with the money lifecycle, rather than the appearance of the balance widget.
This comparison examines Amasty Store Credit & Refund, Mageplaza Store Credit and Mirasvit Store Credit & Refund for customer balances, refunds and prepaid credit. Research was checked against official product pages, documentation and license terms on October 22, 2026. This is a documentation-based comparison; we have not installed these extensions or measured their performance.
What a store credit extension needs to control
Store credit is a recorded customer balance that can fund later purchases. It differs from a coupon that changes a price and from reward points governed by an earning scheme. Adobe documents native store credit for Adobe Commerce; Magento Open Source merchants should not assume the same feature is included. Commerce teams should first establish whether their existing native balance already meets the requirement before introducing another ledger.
Define who may issue credit, when a return becomes eligible, whether customers can buy top-ups, which currencies hold balances, and how partial refunds work. Keep the approval workflow separate from the financial transaction: our Magento RMA comparison covers return requests and exchanges. A return authorization does not by itself establish that a credit transaction has been posted.
| Product | Useful emphasis | Compatibility checkpoint | Cost checkpoint |
|---|---|---|---|
| Amasty Store Credit & Refund | Refund balances, customer controls and Amasty integrations | Listed Magento 2.4.5-p15 through 2.4.9 branches; Hyvä and GraphQL packages require attention | Selected edition price and renewal were not reliably exposed; request a current quote |
| Mageplaza Store Credit | Prepaid credit products, balance management and transaction notifications | Listed 2.4.4–2.4.9; Hyvä Theme and Checkout advertised | Community $149; Enterprise/Cloud $349 first year; renewal requires confirmation |
| Mirasvit Store Credit & Refund | Cashback, currency balance modes and customer transfers | Listed Open Source/Commerce 2.3.*–2.4.9; version 1.4.0 changes integration packaging | Displayed $149 first year and $90 annual support/update prolongation; verify edition |
USD observations exclude any unconfirmed tax, installation or customization charges. These are commercial products; no free edition was verified. A lower displayed entry price is not an equivalent quote for every Magento edition or deployment.
Amasty Store Credit & Refund
Amasty fits teams that want refunds, customer balance visibility and email updates within an existing Amasty deployment. Its product page describes allowing shoppers to decide how much credit to use. That matters when a customer wants to retain part of a balance for another order instead of automatically consuming everything at checkout.
The guide exposes settings for whether credit covers tax and shipping and whether refunding to credit is selected by default. Those controls deserve a written operational policy: an administrator’s default should reflect the refund outcome agreed with the customer. The documented transaction log and customer account information can support reconciliation, but they do not replace your accounting system.
Compatibility is version-specific. The current page lists 2.4.9, 2.4.8-p5, 2.4.7-p10, 2.4.6-p15 and 2.4.5-p15. Its changelog identifies PHP 8.5/Magento 2.4.9 support in 1.5.1 and PHP 8.4/2.4.8 in 1.4.2. For Hyvä, the guide names amasty/module-store-credit-product-hyva and amasty/module-store-credit-hyva; confirm the Checkout companion required by your release. GraphQL has a separate suggested package, and availability is tied to an active product or support subscription.
Strength: a documented route for configuring credit within the vendor’s broader checkout ecosystem. Limitation: a compatibility badge does not identify every companion package or payment combination. We could not verify a dependable selected-edition purchase and renewal price. Ask Amasty to identify the licensed production instance, allowed website/store views, subscription term and integration entitlement in the quote.
Mageplaza Store Credit
Mageplaza is worth considering when selling credit is as important as refunding it. Its documentation describes credit products with fixed amounts or customer-entered amounts, including a price percentage for a prepayment bonus. A merchant can therefore design an explicit top-up offer rather than relying only on manual balance adjustments.
The guide also describes customer-group controls, a balance link, transaction history, administrative adjustments and using a customer’s credit in an admin-created order. These are useful for a service team that receives orders by phone. Before adoption, demonstrate the precise permissions and customer notification attached to each administrative change.
The current page lists Magento 2.4.4–2.4.9, Hyvä Theme, Hyvä Checkout and API/GraphQL/PWA support. Version 4.1.5 explicitly adds PHP 8.5 compatibility and fixes a Hyvä spending-setting issue. This is a reason to match the installed release, rather than transfer an older extension’s compatibility assumptions to the newest storefront. API availability still leaves the presentation and transaction handling of a custom headless checkout to be established.
Observed first-year pricing is $149 for Community and $349 for Enterprise/Magento Cloud, with one year of support and updates. The license allows one live Magento installation and unlimited test installations; an additional live installation requires another license. Confirm multi-website use within that installation and the actual renewal amount. Strength: prepaid credit and service-team workflows. Limitation: prepaid bonuses introduce another balance source that your reporting and refund procedures must distinguish.
Mirasvit Store Credit & Refund
Mirasvit is the strongest candidate to investigate when currency handling and credit transfers are deciding requirements. Its manual distinguishes one global balance converted from a base currency from separate per-currency balances. This is a material policy choice for a merchant operating localized store views, not merely a formatting option.
The product documentation describes partial credit-memo refunds, cashback rules and transfers between registered customers. Cashback is credited on completed orders. Decide whether transferred and promotional amounts should follow the same service policy as refund credit, and document how staff investigate a disputed transfer.
A significant October 16, 2026 change appears in version 1.4.0: Hyvä and GraphQL support now ship in the main extension. The older mirasvit/module-credit-hyva and mirasvit/module-credit-graph-ql companions are removed. Custom references to Hyva_MirasvitCredit and old template paths need review; the vendor instructs Hyvä users to regenerate configuration and rebuild theme CSS after upgrading. Older installation instructions should not override this release-specific migration note.
The page lists Open Source and Commerce 2.3.*–2.4.9 and displays $149 initially, then $90 yearly for support and updates. Confirm the selected edition and PHP constraint; a full PHP matrix was not verified. The EULA licenses one Magento installation, includes the first support/update year and distinguishes later subscriptions from access to purchased source. Strength: explicit currency and transfer behavior. Limitation: an upgrade can affect customized storefront templates even when the balance data remains unchanged.
Questions that should decide the purchase
Use one staged scenario across the shortlist: issue a partial refund, spend part of it with a second payment method, cancel a later order, then refund one line item. Reconcile the customer’s balance, invoices, credit memos and email messages. This is a suggested acceptance exercise, not a test we performed.
Provide each vendor with your exact Magento Open Source or Adobe Commerce patch, PHP runtime, Luma or Hyvä version, checkout and payment modules. Ask whether GraphQL supplies every operation your PWA needs. Quote production installations, websites, currencies and store views separately; a customer’s ability to cross a store view does not establish license coverage.
Compare a three-year maintenance budget, including renewal, migration work and the time needed to reconcile balances after an upgrade. Coordinate the choice with your loyalty points policy so customers and staff can distinguish credit from promotional rewards.
Which should you shortlist?
Shortlist Amasty for a refund-led Amasty workflow, Mageplaza for prepaid credit products and administrative ordering, and Mirasvit for currency balance choices and transfers. The final choice should follow a reconciled transaction example and a written compatibility/licensing quote. None of the documented feature lists establishes a universal winner for every checkout.