- How do I install anandsiddharth/laravel-paytm-wallet in a Laravel app?
- Install it with Composer using composer require anandsiddharth/laravel-paytm-wallet, then publish the package config file with php artisan vendor:publish and add your Paytm merchant credentials to your .env file. Because the v2.0.0 release notes do not state a compatibility matrix, confirm the package supports your Laravel and PHP versions in a sandbox before wiring it into a real checkout flow. After that, register the callback route and hook the result into your order state transitions.
- Which Laravel and PHP versions does laravel-paytm-wallet support?
- The package does not publish a clear compatibility matrix, and the v2.0.0 release ships with link-only metadata rather than explicit version floors or breaking-change notes. Treat the supported Laravel and PHP range as unverified until you reproduce it yourself against your actual application versions. If your estate runs a modern Laravel line and the package targets an older one, that is a fork or blocker decision rather than a routine integration task. Record the versions and the date you verified them so the matrix does not silently rot.
- How do I configure Paytm merchant credentials with this package?
- Configuration is handled through a publishable config file, with your Paytm merchant ID and merchant key supplied from environment variables rather than hardcoded. Keep those values out of version control and use separate credentials for sandbox and production. Checksum and signing logic is handled internally by the package, so the config file is the main surface you need to review.
- How does laravel-paytm-wallet handle the Paytm callback?
- The package registers a callback route and handles checksum generation and verification as part of its Paytm integration. You still need to confirm in the source and in the sandbox that incoming callbacks are signature-verified and can be safely processed more than once, since retries and replays are normal in payment callbacks. Add your own idempotency keys and reconciliation checks rather than trusting the callback alone as proof of payment.
- What changed in laravel-paytm-wallet v2.0.0 and is there a migration guide from 1.x?
- There is no published migration guide. The v2.0.0 release notes are essentially link-only metadata pointing at an issue and a pull request, with no stated breaking-change surface, no compatibility matrix and no deprecation window. For a major bump on a payments package, treat that as a governance signal and reconstruct the changelog yourself by reading the referenced issue and PR. Assume breaking changes to namespaces, signatures, endpoints or checksums until you have proven otherwise in a sandbox spike.
- Is laravel-paytm-wallet safe to use in production for real payments?
- It is a single-maintainer community package sitting directly on the money path, with no vendor SLA, no documented security disclosure process and no changelog discipline. Defects here are money-losing and auditable rather than cosmetic, so the realistic posture is fork-and-vendor: mirror the package internally, patch it yourself, and re-evaluate upstream only on security or Paytm API-break events. Pair that with an adapter layer and documented internal on-call ownership so someone other than the original integrator can debug it.
- Can I use laravel-paytm-wallet alongside other payment gateways?
- Yes, but do not call the facade or package classes directly from your controllers if Paytm is one of several providers. Put the package behind your own thin gateway interface so Paytm is swappable and the dependency is referenced in exactly one adapter. That keeps the blast radius small and makes a rollback to package version 1.x or a move to a different integration a localized change.
- How do I test Paytm wallet payments with this package?
- Stand up a sandbox spike using Paytm test credentials and exercise initiate, status, refund and callback flows end to end before touching production code. Capture request and response fixtures so you can diff observable behaviour between package versions. Run staging with real callback traffic and reconciliation checks, then canary the rollout by percentage or merchant segment with a documented rollback path.
- Does laravel-paytm-wallet support refunds and transaction status checks?
- Transaction verification is explicitly part of the package scope, and the payment flow covers initiation, checksum handling and callback processing. Refund support is not clearly documented in the release notes, so verify it directly in the source and against the Paytm sandbox before depending on it. If refunds are missing or incomplete, implement them against Paytm's API inside your own adapter rather than patching controllers.
- What are the alternatives to using this package directly?
- The main alternatives are calling Paytm's official PHP SDK yourself, adopting a broader multi-gateway Laravel abstraction that already covers Paytm, or vendoring this package internally as a maintained fork. Whichever you pick, keep the integration behind a gateway interface so the choice is reversible. Given Paytm's fast-moving API and regulatory environment, prefer the option your team can patch and monitor on its own schedule.