Product Decisions This Supports
- Support & finance ops visibility: Gives non-technical teams (finance, customer support) a read-only dashboard inside Nova showing Mollie transactions, so they can answer "did this customer pay?" without engineering help or logging into the Mollie dashboard.
- Build vs. buy (small scope): If the only requirement is "show Mollie payments in our admin panel," this is a candidate for a short internal spike rather than a sprint of custom Nova tooling — but evaluate it as a reference implementation, not a dependency.
- Roadmap prioritization for payments work: Useful mainly as a forcing function to answer a bigger question — is admin-side payment visibility a real recurring need, or a one-off support request? If recurring, the roadmap item should be a first-class reconciliation/reporting feature, not this package.
- Adjacent use cases it does not settle: refunds, disputes/chargebacks, subscription lifecycle, multi-currency reporting, or reconciliation against invoices — all out of scope here and should be scoped separately.
When to Consider This Package
Consider it only when all of the following hold:
- You are on Laravel Nova and want a minimal, embedded transaction list — nothing more.
- You have few or no transactions and no reporting/audit requirements.
- You're comfortable treating it as a starting point to fork and maintain in-house, not a stable third-party dependency.
Look elsewhere (or build in-house) when any of these are true:
- Maintenance risk is disqualifying. Last release was August 2018; Nova has shipped multiple major versions since, and Mollie's API has moved on (API v1 was retired in favor of v2). Expect incompatibility and required code changes before it runs at all.
- Very low adoption signal. ~10 stars and a low health score means little community validation, no security review, and no support path.
- Compliance or financial accuracy matters. Payment data touching finance workflows needs auditability, access control, and correctness guarantees a hobby-scale tool won't provide.
- You need anything beyond "list transactions" — refunds, exports, reconciliation, webhooks, alerts.
- You are not already committed to Nova — adopting Nova because of this package is upside-down.
Recommendation: treat it as a weekend spike / code reference, not an approved dependency. If the demo proves value, allocate a small in-house build against the current Mollie API.
How to Pitch It (Stakeholders)
To executives: This is a small, unmaintained open-source add-on that displays Mollie payment transactions inside our admin panel. It solves a narrow convenience problem — letting support and finance check payment status without engineering help. It is not production-ready: it hasn't been updated since 2018, has minimal community adoption, and predates the current Mollie API. Recommendation: do not adopt as a dependency. If the underlying need is real, it's a low-cost in-house feature — days, not weeks — that we can build correctly and own.
To engineering: It's a thin Nova tool wrapping Mollie transaction data, last touched in 2018 with ~10 stars. Assume it's incompatible with our Nova version and Mollie's v2 API. Best use is as a reference for the Nova tool scaffolding — steal the shape, discard the code. Owning a ~200-line internal tool is cheaper than carrying an unmaintained dependency through the next Nova upgrade.
Framing to avoid: "There's a package for this, so it's free." The real cost is the upgrade treadmill and the absence of a maintainer.