Activating your CreditKit Pro licence
A CreditKit Pro licence key activates one site at a time and is entered at Credit System → License in wp-admin. Activation registers the site with the CreditKit licence server, which returns a signed response that CreditKit Pro caches for 12 hours. The licence controls plugin updates and support. Nothing in the credit system stops working while a licence is inactive or expired.
Entering the key
Go to Credit System → License, paste the key into the License key field and press Activate license. A CreditKit key starts with the CK prefix and carries five four-character segments, in the shape CK-XXXX-XXXX-XXXX-XXXX-XXXX. CreditKit Pro strips whitespace and upper-cases the key before sending it, so a key pasted out of an email with a stray line break still activates.
The shape of the key is not validated on the site. The licence server decides whether a key is real, which activation slots remain and when the licence expires, and the License screen reports that answer back.
What the License screen shows
| Field | Value |
|---|---|
| License key | Masked: the first 8 characters, then asterisks, then the last 4 |
| Product | CreditKit Pro |
| Expires | The expiry date, or “Never (lifetime license)” on a lifetime key |
CreditKit Pro verifies an Ed25519 signature on every licence response against a public key bundled with the plugin. A cached response whose signature does not verify is treated as invalid, so editing the stored licence data in the database does not produce a working licence.
Moving a site or freeing a slot
Press Deactivate this site on the License screen before moving the licence to another domain. Deactivation tells the licence server to release the activation slot and clears the stored key and cached response locally. The local clear happens even when the server is unreachable, so a site cannot get stuck holding a key it can no longer verify. A staging clone inherits the stored key, so deactivate on the clone to avoid consuming a second slot.
When a licence expires
CreditKit Pro keeps running. Balances, the ledger, the Pay with Credits gateway, bundles, webhooks and the REST API are unaffected by licence state, because no feature gate in the plugin calls the licence validity check. What stops is the supply of new versions: the licence server declines to serve an update package for an expired licence, so the WordPress updates screen stops offering CreditKit Pro releases, and support access ends with the licence term. Renewing and re-activating restores both.
An install with no key stored never contacts the licence server at all. The updater is registered only when a key is present, so an unlicensed site makes no outbound licence requests.