- Can I use tear/moip-bundle in a Laravel application?
- No, tear/moip-bundle is a Symfony bundle rather than a Laravel package, so it will not plug into Laravel's service container or package discovery. Laravel shares Symfony components but does not consume Symfony bundles directly. You would need to run a legacy Symfony service alongside Laravel or copy selected classes as reference material. For Laravel, a direct MoIP REST client or official SDK is the safer path.
- How do I install tear/moip-bundle?
- Installation would use Composer and then register the bundle in a Symfony 2 or Symfony 3 AppKernel, which is the legacy Symfony bundle model. The package is not designed for Laravel installation and has no Laravel service provider or package discovery support. Before attempting installation, check composer.json constraints for PHP, Symfony, Guzzle, and PSR packages because modern versions will likely conflict.
- Which Laravel versions are supported by tear/moip-bundle?
- None are officially supported. The package is a Symfony 2/3 bundle from 2017 and is not Laravel-native. It will likely conflict with modern Laravel versions through PHP, Symfony component, or Guzzle constraints. Treat it as reference material only, not as a Laravel dependency.
- Which PHP and Symfony versions does this MoIP bundle require?
- It was built for Symfony 2/3 applications and likely targets PHP 5.6 or PHP 7.x, based on its 2017 release timeframe. There has been no release since October 2017. On PHP 8+ or Symfony 5, 6, or 7, expect Composer constraint conflicts or deprecated API failures. Verify the exact composer.json constraints before any experiment.
- Is tear/moip-bundle safe for production payment processing?
- It is high risk for production payments. The package appears abandoned, with very low community validation, no release since 2017, and no visible maintained CI. Payment processing involves authentication, idempotency, webhooks, refunds, reconciliation, and PCI scope, which are the wrong responsibilities to place on an unmaintained wrapper. Do not adopt it as a production dependency.
- Does tear/moip-bundle still work with the current MoIP or Wirecard API?
- That is unclear and likely no. The bundle has not been maintained since 2017, and MoIP's corporate history with Wirecard means the provider brand, account terms, and API surface should be re-confirmed. The package may encode endpoints or payload assumptions that no longer exist. Confirm the current API version, account entity, credentials, and sandbox access before any design work.
- What MoIP payment features does tear/moip-bundle support?
- The package description says it provides services and configuration for handling payments, transactions, and MoIP API communication. It does not establish clear support for credit card, boleto, subscriptions, split payments, refunds, or chargebacks. Review the source and any tests to confirm actual feature coverage. Then compare that against current MoIP API documentation.
- How should I test tear/moip-bundle before using it?
- Do not test it as a production adoption candidate for Laravel. If evaluating it at all, run Composer installation in an isolated legacy Symfony 2/3 and PHP 7.x sandbox. For real integration confidence, spike a direct MoIP REST integration for the highest-value flows, such as card charge and webhook status update. Use MoIP sandbox credentials and verify idempotency and webhook signature handling.
- What are alternatives to tear/moip-bundle for Laravel?
- Use an official MoIP SDK if one is available and maintained, or build a direct REST client with Laravel's HTTP client, queues, and signed webhook handling. Wrap the integration behind an internal PaymentGateway interface covering authorization, capture, refund, webhook verification, status lookup, and reconciliation export. This avoids depending on an abandoned Symfony bundle and keeps payment operations testable.
- Is tear/moip-bundle maintained and can I fork it?
- It appears abandoned: 2 stars, 0 dependents, no release since October 2017, and a package score of 0.07. Forking is technically possible, but any fork must be vendored under a private namespace with pinned dependencies and a documented patch policy. You would also need to revalidate the MoIP API behavior and payment risk controls. It is better used as reference material than as a dependency.