payme-quantum / payment-sdk
PAYME Payment Integration Library
Requires
- php: ^7.4 || ^8.0
- guzzlehttp/guzzle: ^7.0
README
This project provides a PHP-based integration with the PayMe API for processing payments through multiple providers. It supports both sandbox and production environments, handles real-time payment status callbacks, and includes a fallback polling mechanism.
Features
- Seamless Environment Switching: Easily switch between sandbox and production environments via environment variables.
- Real-Time Callbacks: Supports providerCallbackHost to receive real-time payment status updates.
- Polling Mechanism: A fallback polling mechanism for cases where callback notifications fail to get the final status of transactions.
- API User and Key Management: Automatically creates API users and keys in the sandbox environment after the onboarding process completed in the admin panel.
- Unique Payment References: Generates unique payment reference IDs using uuid_v4() for each transaction.
- Unique Payment Types: Support many payment types related to the user experience:
- Simple Payment: This is when one user does one payment at a time.
- Partial Payment: This is to allow merchants to accept if a customer will do multiple payments for a specific product or service.
- Group Payment: This is when many customers are doing the same payment.
Prerequisites
PHP (>= 7.4) Composer PAYME API access (for both sandbox and production environments)
Getting Started
1. Install the package in your project
composer require payme-quantum/payment-sdk
2. Environment Configuration
Create a .env file in your project root and add the following variables: text
General Configuration
SUBSCRIPTION_KEY_SANDBOX=<your_sandbox_subscription_key> CALLBACK_HOST_SANDBOX=<your_sandbox_callback_url> PAYME_CREDENTIAL_EMAIL=<your_sandbox_email> PAYME_CREDENTIAL_PASSWORD=<your_sandbox_password> SUBSCRIPTION_KEY_SANDBOX=<your_sandbox_subscription_key> CALLBACK_HOST_SANDBOX=<your_sandbox_callback_url> PAYME_CREDENTIAL_EMAIL=<your_sandbox_email> PAYME_CREDENTIAL_PASSWORD=<your_sandbox_password>
Sandbox Configuration
SUBSCRIPTION_KEY_SANDBOX=<your_sandbox_subscription_key> CALLBACK_HOST_SANDBOX=<your_sandbox_callback_url> PAYME_CREDENTIAL_EMAIL=<your_sandbox_email> PAYME_CREDENTIAL_PASSWORD=<your_sandbox_password>
Production Configuration
SUBSCRIPTION_KEY_PRODUCTION=<your_production_subscription_key> CALLBACK_HOST_PRODUCTION=<your_production_callback_url> PAYME_CREDENTIAL_EMAIL=<your_production_email> PAYME_CREDENTIAL_PASSWORD=<your_production_password>
3. Running the Application
To test the integration in sandbox mode, ensure that the PAYME_ENV
is set to sandbox part
in your .env
file.
php index.php
4. Payment Processing
Use the provided postPayment
and postPaymentItem
functions to initiate a payment. Here's an example of how to call them:
use PaymeQuantum\PaymentSdk\Payment; $email = PAYME_CREDENTIAL_EMAIL; $password = PAYME_CREDENTIAL_PASSWORD; $subscriptionKey = PAYME_SUBSCRIPTION_KEY; $sdk = new Payment($email, $password, $subscriptionKey); $transaction = $sdk->postPayment([ 'reference' => 'TEST006', 'amount' => 2000, 'fees' => 50, 'tva' => 5, 'description' => 'First Bill Payment', ]); var_dump($transaction); $payment = $sdk->postPaymentItem([ 'currency' => 'XAF', 'customer_name' => 'John', 'customer_email' => 'Doe', 'customer_country' => 'CM', 'amount' => 1000, 'fees' => 50, 'transaction_id' => $transaction->id, 'phone' => '677777777', ]); var_dump($payment);
For Developers
Different types declaration of the system
type Payment = [ 'reference' => string, 'account_id' => int, 'amount' => int, 'fees' => int, 'tva' => int, 'description' => string, 'status' => string, 'created_at' => string, 'updated_at' => string, ]; type PaymentItem = [ 'reference' => string, 'payment_id' => int, 'customer_id' => int, 'amount' => int, 'fees' => int, 'phone' => string, 'payment_method' => string, 'payment_proof' => string, 'status' => string, 'created_at' => string, 'updated_at' => string, ]; type Fees = [ 'operation_type' => string, 'corridor_tag' => string, 'operand' => string, 'min_amount' => int, 'max_amount' => int, 'value' => int, ]; interface PaymentParam { 'reference' => string, 'amount' => int, 'fees' => int, 'tva' => int, 'description' => string, } interface PaymentItemParam { 'reference' => string, 'currency' => string, 'customer_name' => string, 'customer_email' => string, 'customer_country' => string, 'amount' => int, 'fees' => int, 'transaction_id' => int, 'phone' => string, }
Methods
php
getFees(amount: int, country: string): array;
Given an amount, this function allows you to get the fees associated with an operation.
php
postPayment(param: PaymentParam): array;
Initiates the transaction request. php
getPaymentStatus(reference: string): array;
Retrieves the status of the transaction request. php
postPaymentItem(param: PaymentItemParam): array;
Initiates the payment request. Don't forget that a payment is related to a specific transaction. php
getPaymentItemStatus(reference: string): array;
Retrieves the status of the payment request. php
getPaymentWithItems(reference: string): array;
Polls for the transaction status and all its related payments.
Error Handling
- In case of an error during API requests, detailed error responses are logged.
- If the callback URL fails, the fallback polling mechanism ensures that the payment status is eventually retrieved.
Roadmap
- Future Support: Plans to expand SDK functionality to support other MoMo API features beyond collections, including disbursements and transfers.
Contributing
Contributions are welcome! If you find any issues or have suggestions for improvements, please open an issue or submit a pull request.
License
This project is licensed under the MIT License. See the LICENSE file for details.