What it does

Your customers pay you, on your store, at the price you set. The plugin then creates them as a client of your Agency space and places the order in their name, so their details become the domain's public contact. You pay it there at your cost price — by card, or automatically from your prepaid balance — and the plugin follows it until every service is active. Nothing about Digipacket is shown to your customers, and your API key never leaves your site.

Your catalogue, at your prices

Every plan — hosting, servers, e-mail, SSL — imported as a WooCommerce product. A margin sets the price; any product can then be priced by hand, term by term, and keeps it on the next import.
Domains, on any page

A search box with your prices and the same name on other extensions, transfers with the authorisation code, and the domain registered in the same order as the hosting it is for.
Add-ons and terms

Control panel, dedicated IP, WHMCS licence and server operating systems come with the import. The term can be changed from the cart, which shows the renewal price beside it.
One order, one client

The buyer is found by e-mail among your clients or created from the billing address. No price travels with the order: your Agency space prices every line at your cost.
You pay, we deliver

The order waits in your Agency space until it is paid. The plugin reads it back hourly and completes the WooCommerce order once every service is active.
Sealed on your server

The API key is stored encrypted with your site's own salts, and a transfer's authorisation code is encrypted on the order and wiped as soon as your Agency space has it.

What it needs

WordPress: 6.4 or newer
PHP: 8.1 or newer
PHP extensions: No extension beyond a standard PHP build.
WordPress plugins: WooCommerce 8.0 or newer, with the classic cart and checkout
A Digipacket account: An active Agency Partner account, and an API key created in it under Agency Partners → Website & API.

How a sale works

Four steps between your customer paying you and the service running, and the one in the middle is yours.

Your customer buys, at your price

On your store, through WooCommerce's checkout and whatever payment method you already take. The money is yours.
The order reaches your Agency space

In the background once payment clears, retried every ten minutes if the network fails. Your customer becomes your client, and the order note carries our order number and the invoice.
You pay it, at your cost price

From the Pay link on the order, or automatically from your prepaid balance when it covers the invoice. Nothing is delivered before.
We deliver, and the order completes

The domain is registered or the service created in your client's name. When every service is active, the WooCommerce order is marked completed — a setting you can switch off.

Install it

From the WordPress.org directory

The shortest way: WP-CLI downloads the current release from WordPress.org over HTTPS and activates it. To check the file yourself first, use the command after it.

bash

wp plugin install digipacket-agency-partner --activate --path=/path/to/wordpress

Or, in WordPress: Plugins → Add New Plugin, search for the name above, then Install Now and Activate.

The whole install, in one command

Downloads, checks the file against the SHA-256 below, unpacks it into your plugins directory and cleans up after itself. Any step that fails stops the rest.

bash

cd /path/to/wordpress/wp-content/plugins \
  && curl -fL -O https://downloads.wordpress.org/plugin/digipacket-agency-partner.1.7.7.zip \
  && echo "4fca1a3e494b819bee8e24795df61e2b23140abf6f0909786e40bce0a69d31cb  digipacket-agency-partner.1.7.7.zip" | sha256sum -c - \
  && unzip -q digipacket-agency-partner.1.7.7.zip \
  && rm digipacket-agency-partner.1.7.7.zip

Activate it

With WP-CLI. Without WP-CLI, the plugin is now listed under Plugins → Installed Plugins and the button there does the same thing.

bash

wp plugin activate digipacket-agency-partner --path=/path/to/wordpress

Connect it

Once it is active, about five minutes in WordPress and in your Agency space.

Install and activate it

With WooCommerce already active — the plugin declares it and will not run without it.
Create a key for this site

In your account: Agency Partners → Website & API → Create a key. One per site, named so you recognise it; Show and copy brings it back whenever you need it.

Website & API
Connect

In WordPress: Digipacket Agency, paste the key, Save & connect. The dashboard then shows your agency, plan, currency and balance.
Set your margins, then import

One margin for services and one for domains, then Import catalogue. Your store must be in the currency your Agency account is billed in; the dashboard says so when it is not.
Put it on your pages

With the shortcodes below. The imported products already have their own pages and can be sold as they are.

Step-by-step guides, with screenshots of each screen

Put it on your pages

Each one draws from the catalogue you imported, at your prices, and links to the products the import created. Paste one into any page, post or block that takes a shortcode.

`[digipacket_services]`

One card per service — hosting, servers, e-mail, SSL — priced from its cheapest plan, linking to the products the import created.

`[digipacket_plans product="…"]`

One service's plans as a pricing grid. per="month" makes plans sold on different terms comparable, highlight="…" marks one as most popular, and plans="…" pins the exact ones to show. The dashboard lists each service with its slug.

`[digipacket_domain_search]`

Availability and your price as the visitor types, then the same name on other extensions, each with its own add to cart. suggest="com,net,org" chooses them; limit="0" turns the list off.

`[digipacket_domain_transfer]`

Asks the registry whether a name can be moved, prices the transfer — which buys a year of ownership — and takes the authorisation code. Only its last four characters are ever shown again.

`[digipacket_domain_prices tlds="com,net,org"]`

A grid of extensions with your yearly price.

Why the commands look like this

Why -f is not optional

Without it, curl writes the server's error page into your file and exits 0. You unzip an HTML document into wp-content/plugins and WordPress shows a broken plugin. With -f, curl writes nothing and exits 22.
Why the checksum is printed here

A hash served next to the file only proves the download was not corrupted in transit. This page is a second channel: if the number here and the number on the file agree, both would have had to be changed.
Why the steps are chained with &&

A semicolon runs the next command whether or not the last one worked. With &&, a failed download or a failed checksum stops the chain before anything is written into your plugins directory.

Verify the download

Version: 1.7.7
File: digipacket-agency-partner.1.7.7.zip
Size: 102.5 KB 105,010 bytes
SHA-256: 4fca1a3e494b819bee8e24795df61e2b23140abf6f0909786e40bce0a69d31cb
Published: 7 October 2026
Source code: wordpress.org/plugins/digipacket-agency-partner Browse the source Release notes

Check what you downloaded

Prints OK, or names the file and exits non-zero. Run it before you unpack anything.

bash

# GNU coreutils, on a Linux server
echo "4fca1a3e494b819bee8e24795df61e2b23140abf6f0909786e40bce0a69d31cb  digipacket-agency-partner.1.7.7.zip" | sha256sum -c -

# macOS, and anywhere sha256sum is missing
echo "4fca1a3e494b819bee8e24795df61e2b23140abf6f0909786e40bce0a69d31cb  digipacket-agency-partner.1.7.7.zip" | shasum -a 256 -c

Check what is installed

Compares every file in the plugin folder against the checksums WordPress.org publishes for that version, and names any file that differs or should not be there. It works on a copy installed any way at all.

bash

wp plugin verify-checksums digipacket-agency-partner --path=/path/to/wordpress

Always the newest release

The pinned URL above is the one to use in documentation and in a change you want to be able to repeat. A provisioning script usually wants whatever is current — and WordPress.org serves exactly that at an address with no version in it.

That file has no fixed checksum

The unversioned file is always the current stable release, so its hash changes with every release. Comparing it against the hash on this page works today and fails on the next release — which teaches a script to skip the check.

Download the unversioned file, and once it is installed let WP-CLI check every file against the checksums WordPress.org publishes for that exact version:

Whatever the current release is

The file WordPress.org serves under the plugin's name alone, then the per-file check once it is installed.

bash

cd /path/to/wordpress/wp-content/plugins \
  && curl -fL -O https://downloads.wordpress.org/plugin/digipacket-agency-partner.zip \
  && unzip -q digipacket-agency-partner.zip \
  && rm digipacket-agency-partner.zip \
  && wp plugin verify-checksums digipacket-agency-partner --path=/path/to/wordpress

Update it

WordPress offers each new release under Dashboard → Updates, like any plugin from the directory. By hand, removing the folder first is safe: the API key, your margins, the imported products and the prices you set are all stored in the WordPress database, not in the plugin directory.

Update an existing install

Same chain, with the old directory removed before the new one is written. Unzipping over the top would leave files from the previous version behind.

bash

cd /path/to/wordpress/wp-content/plugins \
  && curl -fL -O https://downloads.wordpress.org/plugin/digipacket-agency-partner.1.7.7.zip \
  && echo "4fca1a3e494b819bee8e24795df61e2b23140abf6f0909786e40bce0a69d31cb  digipacket-agency-partner.1.7.7.zip" | sha256sum -c - \
  && rm -rf digipacket-agency-partner \
  && unzip -q digipacket-agency-partner.1.7.7.zip \
  && rm digipacket-agency-partner.1.7.7.zip \
  && wp plugin activate digipacket-agency-partner --path=/path/to/wordpress

Remove it

Deactivates first, so WordPress runs the plugin's own deactivation code rather than having the directory disappear underneath it.

bash

wp plugin deactivate digipacket-agency-partner --path=/path/to/wordpress \
  && wp plugin delete digipacket-agency-partner --path=/path/to/wordpress

What it sends

Every request goes to our API and nowhere else, and none is made before you connect a key. This is the list your own privacy policy needs; the plugin suggests a paragraph for it under Settings → Privacy.

Your API key and your site's address, with every request, so your Agency space can tell which site a key is used by.
When you connect and import: nothing about your customers. The plugin reads your account and the catalogue at your cost prices.
When a visitor checks a domain: the name they typed. Lookups are limited per visitor and cached for a minute, so a script cannot spend your API quota.
When an order is paid: your customer's billing name, company, e-mail address, phone number and postal address, the items bought and the add-ons chosen — and, for a transfer, the authorisation code they typed.
Hourly, while an order is in progress: its number, to read its status back.

What it does not do

Written down for the same reason as everything else on this page: finding out after you have installed it is worse.

It is not self-contained. Without an active Agency Partner account and a key from it, nothing imports and nothing sells — and a key stops working if the Agency space is suspended or its plan lapses. The plugin says so rather than failing quietly.
Nothing is delivered until the order is paid in your Agency space. Your customer has paid you, not us: an order you leave unpaid, with no balance to cover it, stays undelivered.
It needs the classic WooCommerce cart and checkout — the [woocommerce_cart] and [woocommerce_checkout] shortcodes. The billing-term selector and the domain field are drawn on their hooks, and the block cart has none.
It does not convert currencies. The store must be priced in the currency your Agency account is billed in.
A price you set by hand is kept on every import, including when your cost changes. Prices set by the margin follow the cost; yours do not.

If a command fails

`curl: (22) The requested URL returned error: 404`

The file name or the version in the URL is wrong. Copy the command again from this page rather than editing the version by hand — and note that curl wrote nothing, so there is nothing to clean up.

`WARNING: 1 computed checksum did NOT match`

Do not install it. The download was truncated, or it is not the file this page describes. Delete it and download it again; if it fails twice, write to us before running it.

`The plugin appears but will not activate`

Almost always the PHP version. Every plugin states its minimum above and refuse to run below it rather than failing halfway — check with php -v on the same server.

`The server answered with something that is not JSON`

Almost always the network, not the key: a firewall refusing the outbound call, or a security layer on your host answering with its own page. Check that the server may make outbound HTTPS requests, then send us the message the plugin shows.

`Two copies of Digipacket Agency Partner are installed`

The copy installed before the plugin was renamed, in wp-content/plugins/digipacket-agency-partner-for-wp, is still there. The new copy stands down rather than crash: deactivate the old one and delete its folder. Your settings are in the database and carry over.

Digipacket Agency Partner