MakePay ClientExec Gateway

Overview

The official MakePay ClientExec gateway adds hosted crypto checkout to ClientExec invoices. ClientExec creates the invoice, the gateway creates a MakePay payment link, and signed callbacks mark the invoice paid after the payment settles.

Recurring billing stays inside ClientExec. When ClientExec creates each renewal invoice, the same MakePay gateway flow lets the client pay that invoice.

Use Connect MakePay for normal setup. Manual API-key credentials remain available as a fallback.

Before You Start

• ClientExec 6.8 or newer, including ClientExec 7.x
• PHP 7.4 or newer with OpenSSL and cURL enabled
• HTTPS ClientExec URL
• ClientExec administrator access to Payment Processors
• A MakePay company where you can manage payment settings

Install The Gateway

Download the latest ZIP package:

https://plugins.makecrypto.io/downloads/clientexec/latest.zip

Extract the ZIP and upload the makepay folder to:

ClientExec/plugins/gateways/makepay

The package installs these files:

plugins/gateways/makepay/PluginMakepay.php
plugins/gateways/makepay/PluginMakepayCallback.php
plugins/gateways/makepay/callback.php
plugins/gateways/makepay/oauth.php
plugins/gateways/makepay/lib/*.php

In ClientExec, open Settings > Plugins > Payment Processors, select MakePay, and save the payment processor settings.

Connect MakePay

Open the MakePay payment processor settings and copy the Connect MakePay URL into your browser. The gateway:

1. Opens the MakePay connection page.
2. Asks you to sign in and choose the company that should receive payments.
3. Shows the permissions needed by the ClientExec gateway.
4. Returns you to ClientExec after approval.
5. Saves the connection on the ClientExec installation.
6. Configures the MakePay callback URL and webhook secret.

Configure MakePay

After connection finishes, keep Auth Method set to oauth. Review:

• MakePay company ID
• Settlement asset
• Payment expiration
• Webhook signing secret
• Signup name shown to clients

Manual fallback requires a MakePay company ID, API key ID, API key secret, and webhook secret.

Checkout Flow

When a client pays an unpaid ClientExec invoice with MakePay, the gateway creates a hosted payment link and redirects the client to MakePay checkout.

Field	Purpose
source=clientexec	Identifies the integration
orderId=clientexec_invoice_<invoiceId>	Maps MakePay activity back to ClientExec
invoiceId	ClientExec invoice number
clientId	ClientExec client ID when available
moduleVersion	Installed MakePay gateway version
clientexecVersion	ClientExec runtime version when available

The buyer returns to the original ClientExec invoice after payment or cancellation.

Recurring Invoices

ClientExec remains responsible for recurring products, renewal dates, taxes, invoice generation, and customer emails. MakePay does not create a separate subscription schedule in v1.

For every recurring invoice ClientExec creates, the MakePay gateway behaves the same as a one-time invoice: it creates a hosted checkout link and waits for the signed callback before marking that invoice paid.

Invoice States

MakePay sends signed callbacks to:

https://billing.example.com/plugins/gateways/makepay/callback.php

MakePay status	ClientExec behavior
paid, completed, confirmed, succeeded	Calls ClientExec payment acceptance and records the transaction ID
failed, expired	Logs the callback and leaves the invoice unpaid
cancelled, canceled	Logs the callback and leaves the invoice unpaid
refunded	Logs the callback for manual review
Other statuses	Logged and ignored

Security Notes

The gateway stores connection details on the ClientExec installation. Keep ClientExec administrator access limited to trusted operators, and disconnect the gateway from the MakePay dashboard if an administrator account or server backup is exposed.

The connection asks for these permissions:

• company:read
• makepay:payment-links:read
• makepay:payment-links:write
• makepay:customers:read
• makepay:customers:write
• makepay:settings:read
• makepay:settings:write

Troubleshooting

If Connect MakePay cannot start, confirm the ClientExec URL is public HTTPS and the makepay folder is uploaded under plugins/gateways. If clients see a checkout error, confirm MakePay is connected and the invoice is unpaid. If callbacks do not mark invoices paid, compare the MakePay callback URL with the callback URL above and rotate the webhook secret from the gateway settings.