- Is kiakaha/chargily-v2 a Laravel package or a Symfony bundle?
- The package is packaged as a Symfony bundle, not a Laravel-idiomatic package. There is no evidence of Laravel auto-discovery, a publishable config, a facade, or Laravel-specific exception types. You can still consume it in Laravel because the container and HTTP client abstractions are compatible enough, but expect to add bridging glue in your payment path.
- How do I install kiakaha/chargily-v2 in a Laravel application?
- Install it with Composer; the package is Composer-installable and PSR-4 autoloaded. Because it is a Symfony bundle, you may need to register the bundle or service provider manually rather than relying on Laravel package discovery. Check the composer.json constraints for PHP, Laravel, and Symfony component versions before adding it to your lockfile.
- Does this package support Laravel auto-discovery and a publishable config file?
- There is no evidence of Laravel auto-discovery or a publishable Laravel config file. Configuration is more likely supplied through a Symfony bundle config tree, environment variables, or constructor injection. Plan to map your Laravel configuration into whatever mechanism the bundle expects.
- How does webhook signature verification work for Chargily Pay v2 in this package?
- The package must verify the signature header using HMAC-SHA256 over the raw request body with a timing-safe comparison such as hash_equals. If it verifies a parsed or re-serialized payload instead of the raw bytes, signature checks can fail intermittently or be bypassable. Read this code line by line and ensure verification runs before any middleware parses the request body.
- How are DZD payment amounts represented in kiakaha/chargily-v2?
- DZD is effectively a zero-decimal currency in this gateway's model, so amounts should be handled as integer minor units end to end. Any float arithmetic or implicit decimal scaling is a correctness bug with financial consequences. Assert the amount type and conversion behavior in your sandbox spike before production use.
- Does kiakaha/chargily-v2 handle webhook idempotency and duplicate deliveries?
- There is no evidence that the package handles duplicate webhook deliveries or provides an idempotency key on checkout creation. You should implement idempotency, replay protection, and reconciliation in your Laravel application regardless of the package. Treat webhook processing as at-least-once delivery and make your order state machine tolerant of repeats.
- Which Laravel and PHP versions are supported, and is kiakaha/chargily-v2 actively maintained?
- The provided context does not specify exact Laravel or PHP version constraints, so inspect composer.json for PHP, Laravel, and Symfony component ranges and check for lockfile conflicts. Maintenance signals are thin: version 1.0.1 with a one-line release note, no visible changelog discipline, and likely a single maintainer. A payment adapter needs an owned failure mode, so plan for vendor or in-house fallback support.
- Can I use kiakaha/chargily-v2 safely with Laravel Octane and queued jobs?
- Symfony or EventDispatcher coupling can bloat the Laravel container and produce confusing runtime behavior in queued jobs and long-lived Octane workers. Test the bridge in the same worker model you use in production, not only in a short-lived HTTP request. Keep the payment adapter small and explicitly reset any state between jobs if needed.
- Is there a sandbox or test mode for Chargily Pay v2 in this package?
- Sandbox fidelity and test card behavior for Chargily are not safe to assume from the package description alone. The context does not document a shipped sandbox or test mode, so validate test-mode availability directly with Chargily before committing. Run checkout creation and webhook verification against test credentials during the spike.
- What are the alternatives to kiakaha/chargily-v2 for Laravel payment integration?
- You can use the official Chargily SDK or call the Chargily Pay v2 HTTP API directly with Laravel's HTTP client. A small in-house adapter around checkout session creation and raw-body webhook verification avoids Symfony bridging glue in your payment path. Evaluate whether a maintained Laravel-specific community package exists before adopting a Symfony bundle for a Laravel application.