Works with:
Store Credit
(store-credit)
30-day money back guarantee
Gitlab access is only given to Agencies and Freelancers after
approval process.
Please note: we do not provide installation or implementation services for our extensions.
Installation should be handled by the developer or agency managing your store. This approach ensures:
- Compatibility with your current setup
- Proper configuration based on your specific version
- Implementation by someone familiar with your codebase
Although we don’t offer installation, we maintain a curated list of recommended development agencies experienced with our solutions.
If you'd like to receive this list, please contact us at [email protected].
Partnership Inquiries
- For partnership opportunities, reach out to: [email protected]
Description
Financial-grade store credit infrastructure for Magento 2 & Mage-OS.
One license = one e-commerce project instance. Multi-store deployments under a single project are covered; additional project instances require additional licenses. Source is published and reviewable on the github.com/qoliber organization — commercial use requires a purchased license key.
Store Credit is a financial-grade store credit infrastructure designed for agencies, solution architects, and merchants who need correctness, scalability, and long-term maintainability. Built around an append-only ledger with reserve / capture flows and atomic balance operations, the module handles refunds, customer balances, multi-currency credits, and headless storefronts without compromising performance or financial integrity.
Store credit looks trivial until refunds, partial captures, and concurrent sessions hit production. We treat balances as a ledger, not a number — the operational risk you'd otherwise discover months later is engineered out at install time.
The module ships as a repeatable primitive: one installation pattern, the same reconciliation tools, the same upgrade path across every project. Agency teams stop writing custom financial logic per client and start reusing infrastructure with a reviewable surface.
Security hardening, race-condition handling, and replay safety are done upstream so the team shipping the storefront focuses on the storefront — not on rebuilding a credit primitive every quarter.
Append-only ledger. Reserve, capture, refund — atomically.
- › Append-only store_credit_ledger with running balance projection
- › Reserve → capture state machine with idempotency keys
- › Row-level locking against concurrent balance mutation
- › Atomic refund-to-credit with over-refund caps
- › Fixed FX rate snapshot per transaction, per currency
- › Retry queue + bin/magento qoliber:store-credit:repair
- › Reconciliation service + /health/store-credit endpoint
- › Swappable strategy interfaces & stable service contracts
- › Migration importer for legacy store credit balances
A store credit primitive is too small to justify a four-week build per project, and too financial to leave undocumented. Store Credit collapses that recurring cost into a single, reviewable module and removes the long-tail of reconciliation tickets from the agency's backlog.
| seq | op | ref | Δ amount | balance |
|---|---|---|---|---|
| 0007 | reserve | order#100000247 | −€ 18.00 | € 142.40 |
| 0006 | capture | invoice#000000183 | −€ 45.00 | € 160.40 |
| 0005 | refund | creditmemo#000091 | +€ 32.00 | € 205.40 |
| 0004 | fx_snapshot | USD → EUR @ 0.928 | — | € 173.40 |
| 0003 | grant | admin/loyalty | +€ 50.00 | € 173.40 |
| 0002 | capture | invoice#000000172 | −€ 27.60 | € 123.40 |
| 0001 | open | migration:legacy_credit | +€ 151.00 | € 151.00 |
Bring every balance across. We handle the import.
Already running Magento store credit from another vendor — or the legacy Adobe Commerce module? The migration importer is included at no extra cost. Balances, transaction history, and customer references move into the append-only ledger with full provenance, no manual SQL, and zero customer disruption.
Balances preserved
Every customer's current available balance is imported 1:1, including reserved and pending amounts where the source schema exposes them.
Transaction history
Historical credits, debits, refunds, and admin adjustments are replayed as append-only ledger entries with original timestamps and references.
Dry-run & reconcile
The importer runs against a copy of production first, emits a drift report, and only commits after reconcile reports zero variance.
Zero customer disruption
Cutover happens inside one maintenance window. Customers never see a missing balance, a duplicate refund, or a credit that silently changes value.
Twelve capabilities that ship in the box.
Every capability below maps to a concrete service, table, or CLI command in the module — not a marketing bullet. Each was added because we hit it in production on a Magento project.
Financial-grade ledger
Store credit is handled through an append-only ledger with reservation and capture flows instead of simple balance subtraction. Every operation is auditable and traceable.
Double-spend protection
Database row locking prevents concurrent balance usage across multiple tabs, devices, or sessions. Credit cannot be spent twice.
Atomic refund workflows
Refund-to-credit operations are atomic, replay-safe, and capped against over-refunding scenarios to eliminate balance inconsistencies.
Built for agencies
Deploy repeatable, production-ready credit infrastructure across multiple Magento projects without building custom financial logic for every client.
Multi-currency ready
Fixed FX rates captured at transaction time ensure stable reconciliation across currencies and international storefronts.
REST & GraphQL APIs
Complete REST and GraphQL coverage enables headless storefronts, PWA projects, Hyvä integrations, and custom checkout implementations.
Hyvä & headless native
Dedicated Hyvä Checkout support with native Magewire components plus API-first architecture for modern commerce builds.
Self-healing operations
Automatic retry queues and repair CLI commands recover failed capture and refund operations without manual intervention.
Reconciliation & health checks
Built-in verification, rebuild tools, reconciliation services, and health endpoints simplify production monitoring and operational support.
Extensible architecture
Swappable strategy interfaces and stable service contracts allow developers to extend core behaviors without rewriting business logic.
Enterprise code quality
Built with PSR-12, Magento coding standards, PHPStan Level 8 and extensive automated testing for long-term upgrade stability.
Migration included
Free migration from existing Magento store credit solutions including balances and transaction history with zero customer disruption.
Operational primitives, not a feature gallery.
The cost of store credit isn't visible in the demo. It shows up in the third refund of a multi-currency order, in the customer who opened two tabs, in the upgrade six months from now. Store Credit is engineered for what happens after launch.
-
01Append-only ledger instead of mutable balance fields.Every state change becomes an entry. Bugs become reviewable instead of catastrophic.
-
02Reserve → capture workflows prevent financial inconsistencies.Two-phase movement of funds eliminates the "credit applied, order not placed" failure mode.
-
03Headless-ready APIs simplify PWA and custom checkout builds.REST + GraphQL parity, no admin-only endpoints — checkouts are not second-class citizens.
-
04Stable @api contracts reduce upgrade risk.Service interfaces follow Magento's API stability rules. Minor versions don't break your patches.
-
05Recovery tooling and reconciliation are part of the platform.Repair CLI, retry queue, drift detection — the tickets that wake an on-call dev are handled upstream.
-
06Hyvä-native implementation without storefront compromises.Magewire components ship in the package — no Knockout fallbacks, no jQuery glue, no rewrites.
Store Credit vs. a typical 3rd-party module.
Compared category-by-category against what is commonly shipped in Magento store credit extensions. The comparison reflects defaults, not what can be retrofitted with custom development.
Comparison reflects common defaults across publicly available Magento store credit extensions as of 2025. Individual third-party vendors may address specific gaps; the table compares out-of-the-box behavior, not custom-built variants.
What's tested, what's legacy.
Production status is reserved for stacks we run in CI and verify on every release. Legacy stacks remain supported on request — backported for active customers, not maintained by default.