Download the PHP package laraditz/razorpay without Composer
On this page you can find all versions of the php package laraditz/razorpay. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package razorpay
Laravel Curlec by Razorpay
A Laravel wrapper package for the Razorpay Curlec API. Built directly on Laravel's HTTP client, it provides a fluent facade for Payment Links, Orders, Payments, Refunds, and Settlements with database persistence and webhook-driven, event-based sync out of the box.
Features
- 🔗 Payment Links — create, fetch, update, cancel, list, resend notification
- 🧾 Orders — create, fetch, list, update, fetch payments for an order, plus Checkout payment-signature verification
- 💳 Payments — fetch, capture, update, list — synced locally from both the API response and the
payment.authorized/captured/failedwebhooks - 💸 Refunds — create, fetch, list (account-wide and per-payment), update
- 🏦 Settlements — fetch, list — synced locally from both the API response and the
settlement.processedwebhook - 🗄️ Local database persistence for every resource (
RazorpayPaymentLink,RazorpayOrder,RazorpayPayment,RazorpayRefund,RazorpaySettlement), each apayment_id/razorpay_idjoin away from the others - 📜 API request/response logging — every outbound call recorded, with customer PII redacted and configurable retention
- 🕵️ Webhook audit log — every signature-valid inbound webhook recorded for later audit, separately from signature-failure diagnostics in your app's log channel
- 🔔 Automatic webhook handling with HMAC-SHA256 signature verification
- 🔁 Idempotent webhook sync — local records stay correct even if Razorpay retries a delivery
- 🎯 Generic + typed events for every webhook-driven state change
- 📦 Uses Laravel's HTTP client only — no Guzzle, no vendor SDK
- 🛡️ Type-safe with PHP 8.2+ backed enums
- 🚫 Package-owned exception hierarchy — never leaks raw HTTP or vendor exceptions
Requirements
- PHP 8.2+ (Laravel 13.x itself requires PHP 8.3+)
- Laravel 10.x, 11.x, 12.x, or 13.x
Installation
Install the package via composer:
Publish the configuration and migrations:
Run the migrations:
Add your Razorpay credentials to .env:
Configuration
config/razorpay.php:
Usage
Every service is accessed through the Razorpay facade. Full method reference, parameters, and more examples for each are in Documentation section.
Payment Links
→ Full documentation
Orders
→ Full documentation
Payments
→ Full documentation
Refunds
→ Full documentation
Settlements
→ Full documentation
Querying local records
Every create() call (and, for Payments/Settlements, every fetch()/capture()/update()/all() call too) persists a local Eloquent record, kept in sync automatically as webhooks arrive — no manual polling required:
Error Handling
Every non-2xx API response is caught and rethrown as a package-owned exception — you never need to catch raw HTTP client exceptions:
Webhooks
A webhook route is registered automatically at POST /razorpay/webhook (configurable via RAZORPAY_WEBHOOK_PATH) — never part of Laravel's web middleware group, so the X-Razorpay-Signature header is the sole authentication boundary. Point your Razorpay Dashboard's webhook URL at it and set RAZORPAY_WEBHOOK_SECRET.
Typed events fire for the events this package understands (PaymentLinkPaid, PaymentAuthorized, PaymentCaptured, PaymentFailed, OrderPaid, RefundCreated/Processed/Failed, SettlementProcessed), each keeping the matching local record in sync — plus a generic RazorpayWebhookReceived event for every verified delivery, regardless of type.
→ Full documentation — event reference, listener setup, idempotency notes
Logging
Outbound API calls and inbound webhook deliveries can each be optionally recorded for troubleshooting/audit, independently toggled and retained:
→ Full documentation
Documentation
For detailed documentation on each service, please refer to:
- Payment Links — create, fetch, update, cancel, list, resend notification
- Orders — create, fetch, list, update, fetch payments for an order, Checkout signature verification
- Payments — fetch, capture, update, list
- Refunds — full/partial refunds, account-wide and per-payment listing
- Settlements — fetch, list, reconciliation
- Webhooks — event reference, listener setup, idempotency
- Logging — API request/response logging and webhook audit log
Testing
The test suite uses Http::fake()/Event::fake() throughout — no real network access or live Razorpay credentials are required.
Security
If you discover any security related issues, please email [email protected] instead of using the issue tracker.
License
The MIT License (MIT).
