Paymenter server extension Free & open source

Pelican Panel server extension for Paymenter

Paymenter has no Pelican extension: not in Paymenter 1.5.9 and not in its development branch (checked on 25 October 2026), and it is a long-standing request (Paymenter discussion #535). Pelican started as a fork of Pterodactyl, but its API has changed enough that the Pterodactyl extension does not work with it.

Download free on Gumroad →Pelican extension on SourceXchange →

Free on Gumroad. The SourceXchange listing is in review.

Tested with: Paymenter 1.5.9 and Pelican Panel v1.0.0-rc.2
Based on: Paymenter's MIT-licensed Pterodactyl extension
License: MIT
Price: Free

This extension starts from Paymenter's own MIT-licensed Pterodactyl extension and follows Pelican's current Application API. When an order is paid, Paymenter creates the server in Pelican; Paymenter's suspend, unsuspend, upgrade and terminate actions change it there, and customers get a Go to server button that opens it in Pelican.

Paymenter product settings for Pelican: egg tag, egg, Docker image, egg variables, node and node tags — Eggs, images and egg variables straight from Pelican

What Pelican Panel extension for Paymenter does

Creates the server when an order is paid

With the product's egg, Docker image, egg variables, memory, swap, disk, CPU, IO weight, CPU pinning, and database, backup and port limits.

Eggs straight from Pelican

Pelican has no nests: the product page lists every egg, narrows the list by egg tag, and shows the egg's Docker images and a field per egg variable.

Node tags or a fixed node

Pelican has no locations: a product uses any node with one of its node tags, or always the same node.

Every server gets a port

Pelican's automatic deployment only assigns a port when a port range is sent, so the extension picks the node and the port itself. Port ranges, port arrays and dedicated IPs work.

The right customer account

Pelican's email filter also matches parts of addresses, so the extension reads every page and takes the account with exactly the customer's address, or creates one.

Clear errors

Test Connection checks the URL, the key and every read permission, and names the missing one. Errors show the HTTP status, the request and Pelican's reason.

How it works

Upload. Admin → Extensions → Available Extensions → Upload Extension in Paymenter, and upload the zip.
Create the API key. In Pelican: Admin → Advanced → API Keys. Server and User Read & Write; Node, Allocation and Egg Read; everything else None.
Connect. Paymenter → Admin → Servers → Create, Server PelicanPanel, the Pelican URL and the key, then Test Connection. On each product, pick the egg, the node tags (or a node) and the resources.

Screenshots

Paymenter service page with a Go to server button, and the server's console in Pelican — Go to server opens the customer's server in Pelican

Test Connection message saying Pelican answered HTTP 403 and the API key needs Read for Allocation — Test Connection names the missing permission

Pelican's Create Application API Key form with Read & Write for Server and User and Read for Node, Allocation and Egg — Five permissions, step by step in the README

Differences from the Pterodactyl extension

Eggs without nests (egg tag filter), and node tags instead of locations.
The extension picks the port; Pelican's automatic deployment would leave the server without one.
Egg variables and the Docker image can be set on the product page; config options named after a variable still work.
The customer's account is matched by the whole email address, on any page.
After an upgrade the allocation limit still counts the server's own ports.
Terminating a server that was already deleted in Pelican succeeds.

Good to know

Products have to be set up again, because eggs, nodes and tags live in Pelican.
New Pelican accounts get a set-password email from Pelican, so Pelican needs working mail settings.
Tested with a local stand-in for Wings, so real nodes (installation, power actions) were not part of the test.
For Pterodactyl 1.x, use Paymenter's Pterodactyl extension; on Pterodactyl 2.0, use Pterodactyl 2.0 for Paymenter.

FAQ

Does the customer get a Pelican password?

If the account is new, Pelican emails a link to set one (Pelican needs working mail settings). Existing accounts with the same email address are used as they are.

"Go to server" shows 404 in Pelican.

The browser is signed in to Pelican as someone who does not own the server; Pelican answers 404 for other users' servers. Sign out or sign in as the customer.

Can customers choose the memory or a game version?

Yes, with Paymenter config options whose environment variable is memory (or another product setting) or the egg variable's name, such as MINECRAFT_VERSION.

Does it reinstall a server on upgrade?

No. It changes the resources of the same server. A product with another egg moves the server to that egg; Pelican does not reinstall it by itself.

Is it free?

Yes, free and open source under the MIT license, on Gumroad and SourceXchange, where the listing is in review.