Common Issues
Adapter is not loaded
Confirm that your adapter file is included before Monime registers adapters. If the class exists but Monime still cannot find it, the issue is usually an autoloading or hook-order problem.Monime does not use my adapter
Check that your adapter is registered on themonime_register_adapters hook and that the adapter ID is unique.
If another plugin is using the same adapter ID, Monime may not know which adapter should handle the request.
Webhooks do not update custom records
Make sure your webhook handler is implemented and that the Monime webhook endpoint is configured with the correct secret. Also check that your webhook handler:- accepts the event payload Monime sends,
- can map the Monime reference back to your internal record,
- and updates the record in a way that can be repeated safely if the webhook is resent.
Checkout payload errors
Validate the data you pass intobuildPaymentPayload(), especially the line items, URLs, reference, and currency.
Common causes include:
- empty line items,
- invalid or missing return URLs,
- unsupported currency values,
- or a reference that does not match the record you are trying to pay for.
Debugging Checklist
When troubleshooting a custom integration, check the following in order:- Whether the adapter class loads without PHP errors.
- Whether the adapter is registered before checkout starts.
- Whether the payment payload contains all required fields.
- Whether the webhook endpoint is reachable.
- Whether the webhook handler can update the correct internal record.
Support
If the issue persists, inspect your WordPress error logs and the Monime webhook logs, then compare them with the adapter code path that created the payment. When you ask for help, share:- the adapter ID,
- the internal reference used for the payment,
- the Monime session or transaction reference,
- and the exact error message from the logs.