- Can I install quartet/webpay-bundle in a Laravel app with Composer?
- No. It is a Symfony 2 bundle that expects AppKernel registration, a container extension, and YAML service definitions; Laravel has no bundle system and a different container and event lifecycle. There is no first-class path to composer require it into a Laravel application and have it work. The realistic route is to vendor the source, extract only the WebPay API client logic, and rebuild it behind a Laravel service provider.
- Is quartet/webpay-bundle maintained and safe to use for payments?
- There is no meaningful adoption signal: zero stars, zero dependents, no recorded maintainers, and no issue history to inspect. Symfony 2 reached end of life in November 2018 and the code targets PHP 5.x-era idioms, so PHP 8.x will surface breaking changes. Treat every line as unvetted and specifically audit for cardholder data leaking into logs and any client-side handling of PANs.
- What Laravel and PHP versions does quartet/webpay-bundle support?
- It does not support Laravel at all; it is built for Symfony 2 and PHP 5.x-era environments. Running it on modern PHP will likely hit Guzzle major-version drift, removed APIs, dynamic-property deprecations, and old TLS defaults. There is no official Laravel version support matrix to rely on.
- How do I migrate the Symfony WebPay bundle to Laravel?
- Do not migrate the bundle itself. Instead, read it as documentation to learn the WebPay token, charge, and refund call sequences, then build a PaymentGateway interface in Laravel with a WebPay-shaped adapter. Register the adapter in a service provider, put configuration in config/services.php, and keep secrets in the environment or a secrets manager.
- Does WebPay still exist, and can I get sandbox credentials?
- WebPay (webpay.jp) is the Japanese card gateway whose service was wound down and absorbed into Stripe. Any dependency on a defunct or transitioned gateway is a business-continuity issue, not just a code-quality issue. Confirm merchant onboarding, sandbox access, and the migration path to the successor directly with the provider before any further evaluation.
- What license does quartet/webpay-bundle use?
- The license is not confirmed in the available context, and no LICENSE file means no legal right to use or redistribute the code. That is common in abandoned bundles and is an immediate blocker for a payments codebase. Verify the repository license with legal before using any part of it.
- Does this bundle support 3-D Secure, tokenization, idempotency, and webhook signatures?
- It is unclear whether the bundle handles 3-D Secure, tokenization, idempotency keys, or webhook signature verification at all. The available assessment suggests it may cover only the happy-path charge call. Audit the source and the upstream WebPay SDK before assuming any of these safety features exist.
- Is there PCI scope reduction, or does card data transit my servers?
- There is no evidence of hosted fields or client-side tokenization that would reduce PCI scope. You must audit the code for PAN handling and for cardholder data leaking into logs. If card data transits your servers, plan for the corresponding PCI obligations rather than assuming the bundle removes them.
- How should JPY amounts be handled with WebPay in this bundle?
- JPY is a zero-decimal currency, so minor-unit assumptions can produce amounts that are off by a factor of 100. The available assessment explicitly asks whether the bundle's amount handling assumes minor units incorrectly. Verify the amount conversion path and test against the gateway's sandbox before relying on it.
- What is a better alternative to quartet/webpay-bundle for Laravel payments?
- Use the bundle only as documentation of the WebPay API contract, then implement a supported gateway adapter in Laravel. A PaymentGateway interface with tokenize, charge, refund, and capture methods keeps the integration swappable. Implement the adapter against a maintained provider such as Stripe or PAY.JP, using Laravel's HTTP client or a pinned Guzzle version, not the abandoned Symfony bundle.