Weave Code
Shaparak Laravel Package
php-monsters/shaparak
PHP package for integrating Iran's Shaparak payment gateway into Laravel or standalone PHP apps. It handles payment requests, gateway redirects, and transaction verification, making it simple to accept and confirm online payments with a clean, configurable setup.
Iranian IPG gateways handler for Laravel framework
Frequently asked questions about Shaparak
- How do I install php-monsters/shaparak in a Laravel app?
- Install the package with Composer and rely on Laravel package auto-discovery, then publish the config file with vendor:publish and add per-gateway credentials to your .env file. The expected lifecycle is request, redirect, callback, and server-side verify. Confirm the exact config keys and handler names from the package README before wiring it into checkout.
- Which Iranian payment gateways does php-monsters/shaparak support?
- The package abstracts Shaparak-connected PSPs, and the technical assessment lists Behpardakht/Mellat, Sadad, Parsian, Saman, Zarinpal, IDPay, and Pay.ir as examples. Per-gateway maturity and completeness can vary because each upstream has its own request and verify contract, callback payload shape, signature scheme, and currency unit. Validate every gateway you actually need rather than assuming uniform support.
- Is php-monsters/shaparak compatible with Laravel 10 and PHP 8?
- The package is designed as a Laravel package with a service provider and publishable config, and the assessment assumes a modern Laravel application on PHP 8.x. The exact Laravel version matrix is not confirmed in the provided context, so check composer.json and whether the supported matrix is CI-enforced. Do that before committing to Laravel 10 in production.
- What are the license terms for php-monsters/shaparak?
- The repository reports NOASSERTION, which means the actual license terms are not confirmed. The technical assessment calls this the single largest blocker and treats it as a gate for commercial use. Get written confirmation of the terms before shipping the package in a commercial product.
- How does the Shaparak payment flow work with this Laravel package?
- The normal lifecycle is request, redirect, callback, and server-side verify. Initiate the payment through the package handler, send the user to the gateway, then verify the transaction on your callback endpoint before fulfilling an order. Keep the package behind a project-owned PaymentGateway interface so you can enforce amount validation and idempotency independently of the upstream gateway.
- Does php-monsters/shaparak handle idempotency and transaction verification?
- The package handles transaction verification, but the assessment flags idempotency as an open question, so do not assume it is enforced for you. Verify how repeated callbacks are handled and whether verification can be safely retried. The safest design is to enforce idempotency keys and amount checks in your own adapter layer.
- Can I use php-monsters/shaparak outside Laravel in a standalone PHP app?
- The overview says it can be used in Laravel or standalone PHP apps, but the technical assessment warns that the value proposition drops sharply outside Laravel because you inherit Laravel container assumptions. If you are not on Laravel, consider a narrower internal adapter instead. If you are on Laravel, it is a natural fit as a thin anti-corruption layer.
- How should I test a Shaparak payment integration without live gateways?
- You cannot validate end-to-end without merchant sandbox accounts, so plan for credentialed integration testing rather than unit tests alone. Wrap the package behind your own PaymentGateway interface and use a test double in CI for the parts you control. Then run targeted sandbox tests for callback verification, amount handling, and repeated callbacks.
- Is php-monsters/shaparak production-ready and well maintained?
- Treat it as unproven for production until you verify license terms, maintenance activity, and per-gateway behavior. The repository has roughly 32 stars and a small maintainer surface, so peer review is limited and stagnation is a real risk. Check commit cadence, open-issue responsiveness, and whether tests cover callback verification and idempotency. Also assume Iranian PSP APIs can change without much notice.
- What are the alternatives to php-monsters/shaparak for Iranian payments in Laravel?
- Alternatives include building your own PaymentGateway interface with narrow adapters per PSP, or evaluating other Laravel packages that wrap Shaparak and Iranian IPGs. The important design move is to keep any package behind a project-owned interface so you can swap implementations later. Compare license terms, gateway coverage, test coverage, and maintenance activity before choosing.
Weaver
How can I help you explore Laravel packages today?