- Can I install gordalina/mangopay-bundle in a Laravel application?
- No, not as a normal Laravel package. It is a Symfony2 bundle built around Symfony's DependencyInjection component, so it does not provide a Laravel service provider, facade, or config publishing. Installing it in Laravel would likely cause Composer conflicts and would not give you native Laravel integration. Treat it as a reference implementation rather than a drop-in dependency.
- Does gordalina/mangopay-bundle support Laravel 10 or Laravel 11?
- There is no indication that it supports Laravel 10, Laravel 11, or any Laravel version. The repository targets Symfony2, which is end-of-life, and its constraints are likely incompatible with modern Laravel and PHP 8.x stacks. You should expect Composer resolution to fail or require ignoring platform requirements, which is not acceptable for payments. Use the official MangoPay PHP SDK instead.
- How do I configure MangoPay credentials with this bundle in Laravel?
- You cannot configure it through Laravel's config system because the bundle uses Symfony2's configuration tree and service container. Any credentials would need to be wired into Symfony-style service definitions, which Laravel does not consume. A safer approach is to store MangoPay credentials in Laravel's config and env files and pass them to the official MangoPay SDK through a custom service provider. Do not hard-code payment credentials in bundle configuration files.
- Is gordalina/mangopay-bundle maintained and safe for production payments?
- It appears effectively unmaintained: the assessment notes 5 stars, 0 dependents, and ties to end-of-life Symfony2. Payment flows add high stakes around credentials, webhooks, idempotency, reconciliation, and API deprecation, and this bundle lacks modern community validation. Adopting it directly would make your team responsible for security and API compatibility. Prefer MangoPay's official SDK with a Laravel adapter and sandbox tests.
- What MangoPay API and SDK versions does this Symfony bundle target?
- The repository does not provide enough current detail in the context to confirm the exact MangoPay API or SDK versions it targets. The assessment indicates it was designed for older MangoPay SDK and API surfaces from the Symfony2 era. Before relying on any code, inspect composer.json and the bundle's SDK dependency constraints. Expect the official SDK to have evolved significantly since then.
- How do I handle MangoPay webhooks and idempotency if using this package?
- The bundle does not appear to address modern webhook verification, idempotency keys, or MangoPay error semantics in a Laravel context. You would need to build webhook signature checks, replay protection, idempotent payment creation, and reconciliation yourself. In Laravel, use queued jobs, request validation, and a dedicated webhook controller around the official SDK. Do not assume the bundle handles these payment-critical concerns.
- Can I extract the MangoPay service classes from the Symfony bundle for Laravel?
- Possibly, but only as a reference exercise. The useful domain logic may be entangled with Symfony2 service definitions, container assumptions, and older SDK calls. Porting it into Laravel application services or a package would require rewriting configuration, dependency injection, and error handling. For most teams, wrapping the official MangoPay PHP SDK directly is faster and lower risk.
- What are the alternatives to gordalina/mangopay-bundle for Laravel?
- The primary alternative is MangoPay's official PHP SDK, wrapped in a Laravel service provider and an internal anti-corruption layer. You can add config publishing, facades, DTOs, webhook handlers, and queued jobs tailored to your payment flows. There is no evidence of a maintained Laravel-native MangoPay package in the assessment. Build a thin adapter rather than depending on a Symfony2 bundle.
- How do I test MangoPay payments, wallets, and transfers with this bundle?
- There is no described test coverage for payment creation, refunds, KYC, wallets, or transfers, and the bundle is not structured for Laravel testing. You should not rely on it for sandbox or production test suites. Instead, test the official MangoPay SDK behind your Laravel adapter using sandbox credentials and mocked HTTP responses. Cover onboarding, pay-ins, payouts, refunds, disputes, webhook replay, and failure states.
- What PHP and Symfony version constraints does this bundle declare, and will Composer conflict with Laravel?
- The assessment expects older PHP and Symfony2 constraints, with likely conflicts against PHP 8.x, Laravel 10/11, and Symfony 6/7 components. Composer resolution will probably fail or require ignore-platform-reqs, which is unacceptable for a payments integration. Check the bundle's composer.json for exact constraints before attempting anything. In practice, do not install it directly into a modern Laravel application.