A gift card sale creates two customer experiences: the purchaser pays today, and the recipient redeems the value later. A polished card designer helps, but activation, delivery, partial redemption and refunds determine whether the program is manageable when something goes wrong.
Amasty Gift Card, Mageplaza Gift Card and Aheadworks Gift Card all address gift certificates for Magento stores. This comparison uses official product pages, user guides and terms checked on October 22, 2026. We have not installed the products, tested a payment integration or measured sales results. The aim is to identify which documented workflow deserves a closer demonstration.
Start with the gift card lifecycle
A gift card is stored value represented by a code or account, rather than an ordinary promotional coupon. Adobe Commerce already includes native gift card functionality, while Adobe’s documentation identifies that feature as unavailable in Magento Open Source. Commerce merchants should establish the gap in their existing program before introducing a second gift card implementation.
Write down when value becomes usable, who receives the code, what happens after a delivery failure, and how much can be spent per order. Decide whether physical certificates are actually printed and fulfilled by your team or by another service. An extension that tracks a physical card does not automatically provide a printing operation.
| Product | Workflow emphasis | Frontend checkpoint | Observed commercial position |
|---|---|---|---|
| Amasty Gift Card | Code pools, card designs and tiered integration features | Hyvä Theme/Checkout companions; edition and tariff matter | Basic/Pro/Premium are one product; selected prices and renewals need a quote |
| Mageplaza Gift Card | Customer personalization, templates and usage conditions | Magento 2.4.4–2.4.9 advertised; Hyvä and PWA scope must match checkout | $249 Community or $449 Enterprise/Cloud first year |
| Aheadworks Gift Card | Virtual, physical and combined cards with code-pool administration | Observed list: Open Source/Commerce 2.4.6–2.4.8; Hyvä add-on and GraphQL available | $297/year shown; five-year option also offered |
Prices are USD observations, not all-inclusive implementation quotes. Confirm tax, edition, production-store licensing and renewal at checkout. No free edition was verified for these three products. A vendor’s free installation offer is not a free software license.
Amasty Gift Card
Amasty is worth investigating when the card program needs detailed code-pool administration and integrations with other Amasty functions. Its guide describes fixed or open-value cards and virtual, printed or combined delivery types. Codes activate after invoicing, which is important when reviewing unpaid orders and payment failures.
The product has Basic, Pro and Premium tariffs. Those are editions of the same extension, not separate competitors. Automatic replenishment of code pools is described for Pro/Premium, while Premium includes store-credit capabilities. Ask for a feature-to-package list rather than treating every example on the product page as part of the lowest-priced tariff.
Hyvä requires particular care. The guide names amasty/module-giftcard-hyva-compatibility, plus amasty/module-gift-card-pro-functionality-hyva for Pro/Premium and amasty/module-gift-card-graph-ql. Separate Hyvä Checkout companions are documented. The same guide says the Adobe Payment Services integration does not currently support Hyvä Checkout, so the two individual compatibility claims should not be combined into a promise for that payment and checkout together.
Current release notes identify PHP 8.5 and Magento 2.4.9 support, but select the exact Open Source, Commerce or Cloud package and patch range. The guide also lists a PWA add-on with requirements and limitations. Strength: detailed program controls and a documented integration ecosystem. Limitation: tariff, subscription and companion-module dependencies make the final scope harder to infer. A reliable selected-edition price and renewal amount were not verified; request both, including the allowed production instance and store views.
Mageplaza Gift Card
Mageplaza places substantial emphasis on personalization. Its product page describes merchant-prepared templates, customer-uploaded backgrounds, previewing the result and a block-based card designer. This suits a team whose gift program needs several seasonal designs without asking developers to rebuild the presentation each time.
Usage conditions are another useful distinction. The vendor describes restrictions involving cart value, product quantity, products and shipping or payment methods. The operational question is how those conditions are explained before purchase and redemption. A recipient should not discover an unexpected restriction only after entering a valuable code at checkout.
The manual documents code generation, balances, history, expiration and import/export workflows. Work through a partial redemption and a refund with the vendor. Confirm whether the returned value goes back to the original code or another customer balance, and how staff find the transaction. Avoid assuming that gift card credit is the same ledger as a separately installed store credit extension.
The page lists Magento 2.4.4–2.4.9 and advertises Hyvä Theme/Checkout and PWA/API capabilities. Release-specific PHP requirements and the precise headless presentation package should be confirmed before deployment. Observed first-year pricing is $249 for Community and $449 for Enterprise/Magento Cloud, with one year of support and updates. The license covers one live installation plus unlimited test installations; verify multi-website scope and renewal. Strength: flexible card presentation and redemption conditions. Limitation: configurable restrictions and multiple delivery channels require careful customer messaging and separate service-cost checks.
Aheadworks Gift Card
Aheadworks offers a practical shortlist for teams centered on a familiar virtual, physical or combined card workflow. Its documentation describes fixed or customer-defined value, personalized designs and scheduled delivery. Code pools support physical certificates, while administrative tools track balances and expiration.
The manual covers importing and exporting codes, applying cards to admin-created orders and displaying card information on invoices. These details matter for customer service: replacing a lost delivery should not create a second spendable balance. Ask staff to demonstrate finding the original card, checking its remaining value and correcting the delivery destination under your own controls.
The product page observed in this research lists version 1.10.1 and Magento Open Source/Adobe Commerce 2.4.6–2.4.8. It also advertises a Hyvä add-on through Aheadworks Composer and GraphQL. We did not verify 2.4.9 support or a complete PHP matrix, so a merchant on that release should obtain explicit confirmation. REST/SOAP or GraphQL access does not establish that every custom PWA interaction is supplied.
The listed annual price is $297, and a one-time five-year license option is also presented. Confirm the selected license term, renewal after that term, support entitlement, Commerce edition and number of production stores; the displayed headline is not enough to settle those questions. Strength: a coherent code-pool and service-team workflow, with documented Aheadworks checkout/reporting integrations. Limitation: the observed compatibility ceiling is narrower than some competing pages, and exact checkout/payment combinations still need verification.
Compare costs and compatibility using one scenario
Prepare a small acceptance script: buy a card with a future delivery date, invoice the purchase, redeem part of the balance against an order containing shipping and tax, then refund one item. Repeat with a failed purchase payment and an expired card. These are recommended checks, not results from our own testing.
Give vendors the exact Magento edition and patch, PHP version, Luma or Hyvä build, checkout, payment gateways, currencies and website layout. Ask which Composer packages are mandatory and which require an active subscription. If SMS, printing, POS or another delivery service is involved, identify who supplies it and its recurring charges.
Budget for renewal, custom card templates, email delivery work and upgrades as well as the license. Define whether purchased value may move across websites and whether the license permits those websites. Keep gift card issuance and redemption reports separate from ordinary coupon reporting and reconcile outstanding balances after migrations.
For adjacent decisions, see our checkout comparison and reward points comparison. Neither an attractive checkout nor a loyalty program proves a gift card integration works correctly.
Which product fits your program?
Investigate Amasty for a detailed, tariff-based program within its ecosystem; Mageplaza for personalization and configurable usage conditions; and Aheadworks for code-pool operations and its documented checkout connections. Choose after seeing the same purchase-to-refund example on your required stack. The clearest balance history and most dependable integration fit are more valuable than the longest list of card designs.