Download the PHP package sudiptpa/omnipay-esewa without Composer
On this page you can find all versions of the php package sudiptpa/omnipay-esewa. 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 omnipay-esewa
eSewa PHP SDK
Framework-agnostic, zero-dependency PHP SDK for eSewa ePay v2, with an optional Omnipay v3 bridge.
If this package has been useful to you, GitHub Sponsors is a simple way to support ongoing maintenance, improvements, and future releases.
Public API
This package exposes two public namespaces:
Sujip\\EsewaOmnipay\\Esewa
Highlights
- checkout, callback, and transaction flows built around request and result models
- typed value objects for amount, transaction UUID, product code, and reference ID
toArray()andfromArray()where they are useful- callback verification with explicit states:
verified,invalid_signature,replayed - zero-dependency core with built-in
CurlTransport - configurable retry policy and clock handling
- replay protection backed by filesystem or PDO storage
- optional PSR-18 transport support
- optional Omnipay v3 bridge
- PHP
8.2to8.5
Installation
Optional PSR-18 usage:
Documentation
- User Guide
- Migration Guide
- Architecture
Quick Start
The request constructor accepts strings for convenience. Internally, those values are normalized into value objects. If you want stricter typing in your own code, build the value objects directly:
Working With Models
The core models can be converted to arrays. That is mainly useful when you are crossing controller boundaries, queueing work, or saving fixtures for tests.
The client stays small. Most integrations only need three modules:
$client->checkout()$client->callbacks()$client->transactions()
Callback Verification
Do not treat the success redirect alone as proof of payment. Verify the callback on your backend and keep a status check as a fallback when something looks off.
Transaction Status
Production Notes
For live traffic, turn on replay protection and use persistent storage:
Retry behavior is also configurable:
Omnipay Bridge
Supported bridge flows:
purchase()completePurchase()verifyPayment()
