Monime Documentation

Payment Flow

Build the payment data in your plugin.
Pass the data to your adapter.
Create the Monime checkout request.
Redirect the user to Monime checkout.
Handle the webhook response in your plugin.

The key benefit of this flow is that you do not need to replace your own business logic. Your plugin can keep its current order or record system and only delegate the payment step to Monime.

Example Adapter

use Monime\contracts\MonimePaymentAdapterInterface;
use Monime\contracts\MonimeWebhookAdapterInterface;
use Monime\core\CreateMonimePayload;

class CustomMonimeAdapter implements MonimePaymentAdapterInterface, MonimeWebhookAdapterInterface
{
    public function getAdapterId(): string
    {
        return 'custom_adapter';
    }

    public function buildPaymentPayload(array $data): CreateMonimePayload
    {
        return new CreateMonimePayload(
            $data['lineItems'] ?? [],
            $data['idempotency_key'],
            $data['reference'],
            $data['name'],
            $data['description'],
            $data['cancel_url'],
            $data['success_url'],
            $data['financialAccountId'] ?? '',
            $data['currency'] ?? 'SLE',
            $data['paymentOptions'] ?? [],
            $data['metadata'] ?? [],
            $data['callbackState'] ?? ''
        );
    }

    public function handleWebhook(array $payload): void
    {
        // Read the verified Monime payload here.
        // Match the payment reference back to your local record.
        // Update the order, donation, invoice, or membership status.
    }
}

This example shows how your plugin should translate its own internal data into a Monime checkout request. In a real plugin, the $data array would usually come from your order builder, donation form, invoice screen, or membership checkout flow.

Webhook Handling

Use your webhook adapter to update custom orders, donations, invoices, or other payment records when Monime sends event updates. Monime verifies the webhook signature before it dispatches the payload to your adapter. That means handleWebhook() receives a verified payload, and your job is to map that payload back to your own record system.

What `handleWebhook()` Should Do

Your handleWebhook() method should usually:

Find the internal record associated with the Monime reference.
Confirm the payment state in the payload.
Update your local record only if the event has not already been processed.
Store any useful Monime identifiers for future support or reconciliation.

Common webhook actions include:

marking an order as paid,
recording the Monime transaction reference,
activating access to a service or membership,
and storing the final payment status for audit purposes.

Best Practices

Keep adapter logic small and predictable.
Do not hardcode sensitive credentials in your custom plugin.
Treat webhook delivery as the source of truth for payment completion.
Make webhook handlers idempotent so repeated deliveries do not create duplicate records.
Log the Monime reference and your internal reference together so you can trace payments later.

API Basics

Guides

Advanced Resources

Integrations

Usage

Payment Flow

Example Adapter

Webhook Handling

What `handleWebhook()` Should Do

Best Practices

​Payment Flow

​Example Adapter

​Webhook Handling

​What handleWebhook() Should Do

​Best Practices

Payment Flow

Example Adapter

Webhook Handling

What `handleWebhook()` Should Do

Best Practices