- What Laravel and PHP versions does gts-meghni/laravel-satim support?
- The package is built as a Laravel-native integration using Composer, Eloquent, events, the scheduler, and queues. The provided technical evaluation does not list exact minimum PHP or Laravel versions, so check the composer.json constraints in the repository before installing. Confirm compatibility with your application's framework version and database driver during staging validation.
- How do I install and configure laravel-satim in a Laravel application?
- Install the package with Composer, then publish its configuration, migrations, and language files. Add your SATIM merchant credentials and set the audit retention value in the satim configuration. Run the migrations, wire the facade into your checkout flow, and schedule model:prune and satim:reconcile as part of deployment.
- Does this package support CIB and Edahabia card payments?
- Yes. The package is designed to accept CIB and Edahabia card payments in Laravel through the Algerian SATIM gateway. It provides configuration and helpers to initiate payment requests, handle gateway responses, and add SATIM checkout flows to your application. You should still validate the full card flow against the SATIM sandbox or staging environment.
- Is the package SATIM-certified or only aligned with the SATIM integration guide?
- The evaluation describes documentation such as docs/satim-gateway.md and guide-aligned protocol handling, but it does not state that the package itself is SATIM-certified. Treat it as an integration aid that reduces protocol work, not a certification guarantee. Confirm certification requirements directly with SATIM and validate all operations in a SATIM-provided test environment before production.
- How can I test SATIM payments without calling the real gateway?
- Use Satim::fake() to swap in a fake transport, define named fake responses, and make facade assertions in your Laravel tests. This lets you cover registration, acknowledgement, refund, and error paths without network calls. Be aware that fakes can hide real gateway latency, malformed responses, and SATIM-specific edge cases, so keep a small staging suite against the real sandbox.
- What does the SATIM audit trail store, and does it contain customer PII?
- The package requires database-backed audit storage for SATIM operations and defaults to a ten-year retention period under Algerian commercial-code expectations. The exact audit fields are not enumerated in the provided evaluation, so review the published migration before production. Treat merchant references, order details, and any customer-linked data as potential PII and plan access controls, pruning, and archival accordingly.
- How does reconciliation work, and how often should I schedule satim:reconcile?
- The package provides an Artisan command, satim:reconcile, with after, within, and limit controls for checking order status against SATIM. Reconciliation only helps if it is scheduled and monitored, because pending or stale orders will otherwise go unnoticed. Set the cadence and batch size to match your order volume and SATIM rate limits, and alert on failed or stale reconciliation runs.
- How are SATIM order numbers generated, and how do I guarantee uniqueness?
- Order-number generation depends on the package's audit trail and the Satim::orderNumber() helper. Uniqueness and race behavior must be validated against your merchant account and database, especially under concurrent checkouts. Reconcile any existing order-number formats and merchant references with the package's generator before production use.
- What breaking changes affect custom SatimTransport implementations in v1.1.0?
- Version 1.1.0 changed SatimTransport to an operation-based contract, which is a breaking seam for anyone who implemented a custom transport against the previous endpoint-string signature. Update custom transports to the new contract and run dual-path validation in staging before cutover. If you rely only on the built-in transport and facade, the upgrade path is simpler but should still be regression-tested.
- What production concerns should I plan for with laravel-satim?
- Plan for ongoing operational duties: schedule model:prune, monitor reconciliation, track SATIM guide changes, and review error-code coverage after gateway updates. The audit trail grows with payment volume and is retained for ten years by default, so review indexing, prune batching, and archival strategy. Add runbooks and alerting for pending orders, failed reconciliation, duplicate order numbers, and retention or pruning failures.