Product Decisions This Supports
- Payment provider selection for the Brazilian market. Relevant only if MoIP (the Brazilian gateway, later folded into Wirecard Brazil and resold after Wirecard's 2020 collapse) is on the shortlist. Treat this as one data point about the MoIP API surface, not as a viable integration path.
- Build vs. buy vs. wrap. The honest framing: this is a "wrap" candidate that fails the wrap test. With 2 stars, 0 dependents, and no release since October 2017, the maintenance cost of adopting it exceeds the cost of writing a thin HTTP client against the provider's REST API.
- Framework compatibility is a hard gate, not a preference. Despite the "Laravel/PHP" framing, this is a Symfony bundle — it wires services into the Symfony container and will not drop into a Laravel app. Any roadmap item that assumes Laravel compatibility based on the package name is mis-scoped and should be corrected before estimation.
- Migration and decommissioning planning. Where this package earns its keep today: as a specification artifact. Reading its request/response mapping tells you what the MoIP contract looked like circa 2017 — useful input for a rewrite or for scoping a provider migration.
- Not a fit for any greenfield or PCI-adjacent surface. A payment path needs security patching, API version tracking, and an owner. This package offers none of the three.
When to Consider This Package
Consider it only when:
- You maintain a legacy Symfony 2.x/3.x application with an existing MoIP integration and need to understand or temporarily preserve current behavior before a migration.
- You are reverse-engineering the MoIP API contract for a rewrite and want a reference implementation of payload shapes — read it, don't install it.
- You are doing due-diligence archaeology on an inherited codebase and need to identify what a dependency is doing in the payment flow.
Look elsewhere (or build) when:
- You are on Laravel — wrong framework; the bundle will not integrate.
- You need PHP 7.4+/8.x support, PSR-compliant HTTP clients, or modern dependency injection. A 2017 Symfony bundle will almost certainly pin outdated Symfony and Guzzle versions, creating a transitive dependency conflict in a modern
composer.json.
- You need security patching, vendor support, or an SLA on a payment-critical path. Zero maintainers means zero recourse.
- You need the current provider API. Verify first: the MoIP brand has been rebranded and resold at least once; the endpoints this package targets may no longer be the ones your account uses. Even the best-maintained wrapper would be stale here.
- You are evaluating provider alternatives — a wrapper for one gateway is not an argument for that gateway. Run a separate comparison against Pix support, fee structure, settlement timing, and SDK quality.
How to Pitch It (Stakeholders)
Recommendation: do not adopt. Reference only.
For executives: This package is a stale, low-adoption wrapper around a Brazilian payment gateway whose corporate ownership has changed hands since the package was last touched. It carries a permissive MIT license, so there is no legal obstacle — the problem is operational. Payments are the one code path where an unmaintained dependency is an unacceptable risk: an API change or a security advisory leaves us with no upstream fix. Adoption cost is low; exit cost and incident risk are high.
For engineering: Roughly an estimated 1–3 engineering days to implement a maintained HTTP client against the provider's documented API — comparable or less than the time we'd spend fighting transitive Symfony/Guzzle version constraints from a 2017 bundle. That client is ours, testable, and upgradeable.
The decision to make: not "should we use this package," but "is MoIP the right provider for our Brazilian payments, and what is our integration strategy for it?" Answer the second question directly and this package drops out of consideration on its own. If the answer is yes to MoIP, budget a small spike to read this bundle as reference documentation, then build a first-party client. If the answer is no, close the ticket.