MakePay Restrict Content Pro Gateway

The official MakePay gateway for Restrict Content Pro lets members pay for membership levels through hosted crypto checkout. Restrict Content Pro keeps control of membership levels, invoices, account pages, emails, and access rules. MakePay handles the checkout page and sends signed status updates back to WordPress.

Overview

Use this plugin when your WordPress site sells memberships, subscriptions, premium communities, courses, or restricted content with Restrict Content Pro.

Before you start

• WordPress 6.7 or newer
• Restrict Content Pro active
• HTTPS site URL
• Administrator access to Restrict Content Pro payment settings
• A MakeCrypto company with MakePay settlement configured

Install the plugin

Download the latest package:

https://plugins.makecrypto.io/downloads/restrict-content-pro/latest.zip

In WordPress, open Plugins > Add New > Upload Plugin, upload the ZIP, and activate MakePay for Restrict Content Pro.

Then open Restrict > Settings > Payments, enable MakePay, and save the settings.

Connect MakePay

Click Connect MakePay in the gateway settings. You will be sent to MakeCrypto to choose the company that should receive payments, then returned to WordPress after approval.

After the connection finishes, save the Restrict Content Pro payment settings.

Checkout mode

Hosted redirect is the safest default: the member leaves WordPress, pays on MakePay checkout, and returns to the RCP confirmation page.

Embedded checkout is also available from the MakePay gateway settings. It sends the member to a WordPress page with a secure MakePay iframe and a fallback hosted checkout link.

Manual API key fallback

Use manual API-key mode only when the Connect MakePay flow is not possible. Enter the company ID, API key ID, API key secret, and webhook secret in the MakePay gateway settings.

Checkout flow

When a member selects MakePay at Restrict Content Pro checkout, the plugin:

1. Uses the pending RCP payment created during checkout.
2. Creates a MakePay payment link with the RCP payment and membership IDs.
3. Opens hosted MakePay checkout or the embedded checkout page.
4. Receives a signed webhook when the payment status changes.
5. Marks the RCP payment complete after a successful payment. RCP then activates access for the selected membership.

Payment statuses

MakePay status	RCP payment status
paid, completed, succeeded, confirmed	complete
processing, confirming	pending until final update
failed, expired	failed
cancelled, canceled	cancelled
refunded	refunded
Any other status	stays pending

Restrict Content Pro remains responsible for applying access rules after the order reaches a successful state.

Security notes

Keep the WordPress admin account protected, keep the site on HTTPS, and verify that the webhook URL remains publicly reachable. If the site domain changes, reconnect MakePay so redirect and webhook URLs match the live site.

Troubleshooting

If checkout does not redirect, confirm that MakePay is enabled under Restrict > Settings > Payments and that the connection status is shown in the MakePay settings.

If membership status does not update, verify that MakePay webhook settings point to the public WordPress URL and that security plugins are not blocking webhook requests.