Download the PHP package uzhlaravel/maishapay without Composer

On this page you can find all versions of the php package uzhlaravel/maishapay. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

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 PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • 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.
Please rate this library. Is it a good library?

Example code of uzhlaravel/maishapay

Informations about the package maishapay

This is a laravel way to interact with maishapay.com

Latest Version on Packagist GitHub Tests Action Status GitHub Code Style Action Status Total Downloads

Installation

You can install the package via composer:

automated installation

You can publish and run the migrations with:

You can publish the config file with:

This is the contents of the published config file:

Add these to your .env file:

Usage Mobile Money Payment

Automate the database

Usage Bank Payment

Automate the database transactions :

Usage B2C (Business to Customer) Payment

B2C allows your business to send money directly to a customer's mobile money wallet — useful for payouts, refunds, salaries, or commissions.

B2C with automatic database logging

Note: For B2C, motif, customer_full_name and customer_email_address are optional (the MaishaPay API marks them as not required). amount, currency, provider and wallet_id remain required.

B2C using the static create() helper

B2C database migration

Run the additional migration to support B2C transactions:

This adds:

Querying B2C transactions

Checking transaction status from MaishaPay's servers

Instead of trusting the status stored in your local database, you can query the live status of a transaction directly from MaishaPay's Transaction Lookup API. This is useful when a callback was missed, delayed, or you simply want to confirm the real state before fulfilling an order. It works for any transaction type — Mobile Money, card, or B2C.

The lookup runs against MaishaPay's dedicated transaction endpoint (https://marchand.maishapay.online/api/transaction/rest/v2/check) and supports two modes:

Quick status check (raw response)

Canonical status via EnhancedMaishapayService

Refresh the local record from the server

refreshTransactionStatus() queries MaishaPay, syncs the matching local MaishapayTransaction record (so the database acts as a cache), and fires the TransactionStatusUpdated event when the status changes:

Configuration

The Transaction Lookup base URL and endpoint are configurable:

Config key Env var Default
transaction_base_url MAISHAPAY_TRANSACTION_BASE_URL https://marchand.maishapay.online/api/transaction
status_endpoint MAISHAPAY_STATUS_ENDPOINT /rest/v2/check

The lookup posts gatewayMode, publicApiKey, secretApiKey and transactionId (set to your merchant reference, with ?useRef=1, when looking up by reference). The canonical status is read from MaishaPay's transactionStatus field and normalized to PENDING, SUCCESS, FAILED or CANCELLED.

Testing

Changelog

Please see CHANGELOG for more information on what has changed recently.

Contributing

Please see CONTRIBUTING for details.

Security Vulnerabilities

Please review our security policy on how to report security vulnerabilities.

Credits

License

The MIT License (MIT). Please see License File for more information.

All versions of maishapay with dependencies

PHP Build Version
Package Version
Requires php Version ^8.3
spatie/laravel-package-tools Version ^1.16
illuminate/contracts Version ^11.0||^12.0||^13.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package uzhlaravel/maishapay contains the following files

Loading the files please wait ...