- Can I use teknoo/mango-pay-bundle in a Laravel application?
- No, not as intended. It is a Symfony bundle that registers MangoPay PHP SDK services in Symfony's dependency injection container, and Laravel has no compatible bundle or kernel wiring. For Laravel, integrate the official MangoPay PHP SDK directly behind your own service provider and facade.
- Is teknoo/mango-pay-bundle still maintained?
- No. The repository is explicitly archived and unmaintained, and the last release was in 2019 with only 2 stars and 0 dependents. That means no bug fixes, security patches, or compatibility updates from upstream, so any use creates a fork-and-own maintenance burden.
- What Laravel or PHP versions does teknoo/mango-pay-bundle support?
- The bundle targets Symfony 2.7-era projects and was last released in 2019, so its PHP and Symfony constraints likely conflict with modern Laravel requirements such as PHP 8.1 or newer. It is not a Laravel package and has no Laravel version support. Avoid forcing installation with --ignore-platform-reqs in production.
- How do I install MangoPay in Laravel if this bundle is not compatible?
- Install the underlying MangoPay PHP SDK with Composer instead of the Symfony bundle. Create a Laravel service provider, configuration file, and a small MangoPayService wrapper that reads credentials from environment variables. Then add sandbox contract tests and webhook verification around that wrapper.
- What does teknoo/mango-pay-bundle actually provide?
- It is a thin Symfony dependency injection wrapper around the MangoPay PHP SDK, exposing ready-to-use services for users, wallets, bank cards, transfers, and payment operations. Its value is configuration and service registration, not payment-domain logic or compliance features. In Laravel you would need to recreate that wiring yourself.
- Are there security or compliance risks with using an archived payment bundle?
- Yes. Payment integrations are security- and compliance-sensitive, and an archived 2019 bundle can bring stale SDK wiring, unpatched dependencies, and PHP version drift. You should verify the underlying MangoPay SDK's support status, implement webhook verification and idempotency, and obtain security or compliance sign-off before production. Do not assume the bundle handles PCI or regulatory requirements.
- Can I fork teknoo/mango-pay-bundle and port it to Laravel?
- You can review the MIT-licensed code as a reference for service wiring ideas, but porting the bundle into Laravel is usually not worth it. Its surface area is small and mostly Symfony DI configuration, so building a Laravel service provider around the official MangoPay SDK is cleaner. If you fork, confirm license terms and assign clear internal ownership for maintenance.
- Does teknoo/mango-pay-bundle handle webhooks, idempotency, KYC, refunds, or payouts?
- The bundle mainly wires MangoPay SDK services into Symfony; the provided context lists users, wallets, bank cards, transfers, and payment operations. It does not advertise higher-level handling for webhook verification, idempotency, KYC workflows, refunds, or payout reconciliation. Those behaviors must be designed and tested in your application regardless of the wrapper.
- How should I test a MangoPay integration in Laravel?
- Use MangoPay sandbox credentials and write contract tests around your own service wrapper rather than the Symfony bundle. Cover credential configuration, user and wallet creation, transfer or payment flows, webhook signature verification, retry behavior, and idempotency keys. Keep sandbox tests out of production and log requests carefully without exposing sensitive data.
- What is the migration path if a Symfony app already uses teknoo/mango-pay-bundle?
- Freeze the bundle, document its current service wiring and behavior, and plan a replacement with direct MangoPay SDK usage behind an internal interface. Do not migrate the bundle into a Laravel application. For Laravel, prototype the SDK directly first and only borrow wiring ideas from the bundle as reference.