Weave Code
Symfony Ideal Laravel Package
lensmedia/symfony-ideal
Symfony bundle from Lensmedia for integrating iDEAL payments into your application, with configurable payment flows, simple service setup, and a developer-friendly API for initiating and handling transactions securely. It helps add online payment support to Symfony projects with minimal configuratio...
Symfony bundle for handeling iDeal transactions
Frequently asked questions about Symfony Ideal
- Is lensmedia/symfony-ideal a Laravel package?
- No. It is a Symfony bundle that assumes symfony/framework-bundle, a Symfony DI container, a bundle configuration tree, and auto-registration. Those are not present in a standard Laravel application, so there is no supported composer require and go path for Laravel. Treat it as reference material or as a source for extracting a payment client.
- Can I install lensmedia/symfony-ideal in a Laravel app with Composer?
- Likely not. It will pull Symfony packages such as http-kernel and dependency-injection, and a framework-bundle requirement would make it unbootable in Laravel regardless of version alignment. Run composer why-not lensmedia/symfony-ideal in a throwaway branch before any design work. Composer resolution is the first hard gate.
- How would I add iDEAL payments to Laravel using this bundle?
- You cannot use the bundle directly in Laravel. The two viable routes are extracting the underlying payment client and discarding the bundle glue, or treating the repository as reference material only. Feasibility depends on how tightly the iDEAL transaction logic is coupled to container wiring; if business logic lives in AbstractController subclasses or container-aware services, extraction is a rewrite rather than a lift.
- Does it support Laravel 10 or 11 and PHP 8.2 or 8.3?
- There is no confirmed Laravel support because this is a Symfony bundle, not a Laravel package. The provided material does not show its PHP constraint, so verify composer.json against your Laravel and PHP baseline. Even if the PHP constraint aligns, a framework-bundle requirement blocks normal Laravel use.
- Which iDEAL API or version does lensmedia/symfony-ideal use?
- The evaluation does not confirm whether it talks to the legacy iDEAL Acquirer or Hub, a PSP such as Mollie or Adyen, or a bespoke bank integration. It also does not confirm iDEAL 2.0 support or a migration story away from classic iDEAL. This is a blocking question because classic iDEAL is being re-platformed under EPI and Worldline, so do not assume a January 2024 release covers current interfaces.
- Are callbacks and payment notifications cryptographically verified?
- The provided context does not confirm callback verification. Payments code must handle request signing, certificate storage, callback authenticity, amount tampering, and replay protection. With zero stars and zero dependents, assume no external audit has occurred and review the code before production use.
- Does it handle idempotency, refunds, and status reconciliation?
- The context does not confirm idempotency on payment create, refund support, partial refunds, or status reconciliation. Correctness risks include integer-cent money handling, a EUR-only assumption, the open, pending, paid, expired, and cancelled state machine, and retry behavior. iDEAL refunds are acquirer-mediated and not guaranteed, so verify these flows explicitly.
- Is lensmedia/symfony-ideal actively maintained?
- Maintenance signals are weak: zero stars, zero dependents, a single release in January 2024, a typo in the package description, and a changelog with one visible status-conversion fix. That points to a single-maintainer artifact with no peer-review signal. Bus factor is one, so upstream disappearance is a realistic scenario.
- What are better alternatives for iDEAL payments in Laravel?
- The technical evaluation recommends building against a maintained PSP SDK that already abstracts iDEAL 2.0, such as Mollie, Stripe, Adyen, or Buckaroo. Use this repository only to understand protocol shape or borrow specific parsing and status-mapping logic. Payments is the wrong place to accept a zero-signal package.
- Does it include tests, CI, sandbox fixtures, and a clear license?
- The provided overview does not confirm a test suite, CI, sandbox fixtures, or license terms. These are listed as blocking questions in the evaluation, so inspect the repository files and composer.json directly. Do not commit to production integration without license clarity and evidence of test coverage.
Weaver
How can I help you explore Laravel packages today?