- What is akira/laravel-sisp and what does it do?
- akira/laravel-sisp is a Laravel package for integrating the SISP Payment Gateway directly into a Laravel application. It provides organized configuration, service bindings, and helpers for common SISP API operations to reduce boilerplate. It is a thin single-gateway integration surface, not a full payments domain abstraction.
- How do I install akira/laravel-sisp in a Laravel app?
- Install with composer require akira/laravel-sisp, then publish the package config and set your SISP merchant credentials and environment. Expose the callback route SISP needs and dispatch any post-payment work to a job. The TPM assessment describes the Laravel wiring as straightforward; SISP onboarding is usually the longer critical path.
- Which Laravel and PHP versions does akira/laravel-sisp support?
- The provided context does not state a supported Laravel/PHP matrix, so check the package's composer.json for illuminate/* and php constraints before adopting it. The TPM assessment positions Laravel 10, 11, or 12 on PHP 8.2+ as the best-fit stack, but that is an evaluation recommendation rather than a confirmed package guarantee. Pin an exact version and commit the lockfile.
- How do I configure SISP merchant credentials and environment in Laravel?
- After publishing the package config, set your SISP merchant credentials and choose the sandbox or production environment through environment variables or the config file. Confirm which SISP entity and API version you are integrating, because field names and signature schemes can differ by deployment. Keep secrets out of version control and verify the package does not register conflicting global middleware or migrations.
- Does laravel-sisp verify SISP callback signatures and handle idempotency?
- The overview does not confirm that callback signature or fingerprint verification is implemented in-package, so audit the source and test it before relying on it. Payment callbacks should be authenticated and replay-protected, and you should verify idempotency on repeated notifications. Keep the integration hosted or redirect-only so cardholder data does not transit your servers.
- Does akira/laravel-sisp support refunds, partial captures, voids, and 3DS?
- The package is described as providing helpers for common SISP API operations, but the provided context does not enumerate refunds, partial refunds, voids, pre-authorization or capture, 3DS challenge handling, MB WAY versus card, or multicurrency support. Audit the client methods against the exact SISP operations your business needs before committing. Pay special attention to edge paths such as expired intents and currency rounding.
- Can I test akira/laravel-sisp against a SISP sandbox?
- A SISP sandbox proof-of-concept is the right first step, but SISP merchant onboarding and sandbox credential issuance are typically the long pole rather than Laravel wiring. The context does not indicate whether the package tests against a real sandbox or only mocks, and it notes no CI or coverage evidence. Put the sandbox integration behind a feature flag before committing to adoption.
- Is akira/laravel-sisp safe for production given its low adoption?
- Treat it as high supply-chain risk: the assessment cites 16 stars, 0 dependents, a single maintainer, and no indicated CI, coverage, static analysis, or security disclosure process. The recent 2026-10-01 release is a positive currency signal but not proof of correctness on refunds, partial captures, expired intents, or currency rounding. Use a feature flag, a parallel run, and nightly reconciliation against SISP settlement reports before cutover.
- Should I use laravel-sisp directly or wrap it in a PaymentGateway interface?
- Wrap it behind an internal PaymentGateway interface with create, confirm, refund, and query methods so vendor DTOs and exceptions do not leak into order, billing, or subscription code. The package is a single-gateway driver, not a payments abstraction, and without that seam future gateway changes become application-wide refactors. In a polyglot estate, prefer one payment service calling SISP directly over adopting a PHP-only SDK everywhere.
- Who maintains akira/laravel-sisp and what license does it use?
- The package is MIT licensed, which gives a permissive fork or private-vendor escape hatch. The context identifies a single-maintainer bus factor and no stated security disclosure process or issue response time. Verify maintainer activity and budget for a fork from day one rather than treating it as a contingency.