Weave Code
Gateway Laravel Package
larabook/gateway
Larabook Gateway offers a clean Laravel abstraction for integrating and managing multiple gateways through a unified, driver-based API. It simplifies configuration, requests, responses, and extensibility so you can connect external services with consistent, testable code.
A Laravel package for connecting to all Iranian Banks
Frequently asked questions about Gateway
- Which Iranian banks and gateways does larabook/gateway support?
- Larabook Gateway is built around a unified, driver-based API for connecting to Iranian bank payment gateways, so coverage depends on the drivers shipped in the package. The available overview does not enumerate the supported banks, so review the repository's driver list and confirm each one against the bank's current API version. Treat required bank coverage as a launch gate and verify it with a sandbox spike before committing.
- Is larabook/gateway compatible with Laravel 10 and Laravel 11?
- The package's last release was 2021-11-21, so compatibility with Laravel 10 and 11 and modern PHP versions is a gating question rather than an assumption. Run a time-boxed compatibility spike on your exact Laravel and PHP matrix, checking Composer resolution, service-provider registration, config publishing, and callback routing. If the app is on an older Laravel version, the package may work as a tactical bridge; on current Laravel, budget time for patching or forking.
- How do I install larabook/gateway with Composer?
- It is a Composer-based Laravel package, so installation follows standard conventions: require it via Composer, then register the service provider and publish the configuration if the package documents those steps. Because the package is Laravel-oriented, expect config-driven gateway credentials and bank-specific drivers. Pin the package version and record the PHP and Laravel constraints it resolves against.
- Does larabook/gateway handle payment callbacks and transaction verification?
- The package is positioned to simplify requests, responses, and callback handling across gateways, and verification is part of a typical Iranian bank payment flow. However, the materials provided do not confirm specifics such as callback signature validation, idempotency, refunds, or reconciliation. Confirm those capabilities per driver and add contract tests for initiate, callback, verify, failure, timeout, and duplicate-callback cases.
- Is larabook/gateway actively maintained?
- The last release was 2021-11-21, and there is no commercial SLA or stated active maintainer in the evaluation. MIT licensing is favorable, but bank API drift and security fixes may require internal effort. Before production use, identify an internal owner or fork strategy prepared to patch bank drivers.
- What are the production risks of using larabook/gateway for payments?
- Primary risks include package staleness, bank API drift, incomplete coverage of current authentication and signature requirements, and unclear test coverage. Payment flows add security and financial exposure such as callback forgery, duplicate capture, timeout ambiguity, amount or currency mistakes, certificate rotation, and reconciliation gaps. Isolate the package behind internal interfaces and complete security, compliance, and jurisdictional review before going live.
- Can I use larabook/gateway outside of Laravel?
- Larabook Gateway is a Laravel-oriented package that likely relies on service providers and config-driven integration, so it is a poor fit for non-Laravel PHP services or polyglot architectures without wrapping. If you need it in another stack, run it as a separate payment service behind an internal API. Treat it as an accelerator for bank drivers, not as your payment domain model.
- How should I test larabook/gateway before enabling production traffic?
- Start with a staging spike on one low-risk bank using sandbox or merchant test credentials, with the package placed behind an internal adapter. Add contract tests for initiate, callback, verify, failure, timeout, and duplicate-callback scenarios. Then implement reconciliation and operational runbooks, and pilot with a feature flag and limited transaction volume before full rollout.
- Why should I put larabook/gateway behind an internal payment interface?
- Defining internal PaymentGateway, PaymentIntent, CallbackVerifier, and Reconciliation interfaces keeps your controllers and domain services independent of the package. That adapter-first approach lets you replace stale drivers with direct bank integrations or a maintained fork without rewriting checkout flows. It also keeps business-critical payment orchestration, idempotency, and auditability in your own code.
- What should I check before using larabook/gateway in production?
- Confirm which Iranian banks are mandatory at launch and whether the package supports each current API version, along with your required Laravel and PHP versions. Verify that merchant accounts, sandbox credentials, and bank test environments are available, and review security, data-residency, audit, and regulatory requirements. Also decide whether you will maintain a fork, replace drivers, or continue with pinned package versions based on the spike results.
Weaver
How can I help you explore Laravel packages today?