Download the PHP package artpar/razorpay without Composer
On this page you can find all versions of the php package artpar/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
razorpay-php
Razorpay client PHP Api. The api follows the following practices:
- namespaced under Razorpay\Api
- call $api->class->function() to access the api
- api throws exceptions instead of returning errors
- options are passed as an array instead of multiple arguments wherever possible
- All request and responses are communicated over JSON
- A minimum of PHP 5.3 is required
Installation
- If your project uses composer, add following to composer.json
Then, run composer update. If you are not using composer, download
the latest release from the releases section.
You should download the razorpay-php.zip file.
After that include Razorpay.php in your application and you can use the
API as usual.
Usage
For further help, see our documentation on https://docs.razorpay.com.
Developing
See the doc.md file for getting started with development.
License
The Razorpay PHP SDK is released under the MIT License.
Release
Steps to follow for a release:
- Merge the branch with the new code to master.
- Bump the Version in
src/Api.php. - Rename Unreleased to the new tag in
CHANGELOG.md - Add a new empty "Unreleased" section at the top of
CHANGELOG.md - Fix links at bottom in
CHANGELOG.md - Commit
- Tag the release and push to GitHub
- A release should automatically be created once the travis build passes. Edit the release to add some description.
