PipKey Help Centre
Answers for customers, developers and product teams.
Use this area for practical help. Technical integrators should also use the full documentation.
This page is intentionally static and privacy-conscious. Use your browser's Find function for instant searching.
New to PipKey
Start with the integration model, environments and security basics.
Something is not working
Diagnose activation, validation, credentials, webhooks and updates.
Product status
See what is live now and what remains in commercial development.
Contact support
Contact PluginPip Ltd for controlled onboarding and support enquiries.
Frequently asked questions
What is PipKey?
PipKey is PluginPip Ltd's licensing, entitlement, activation and secure software-delivery platform. PipKey Server 1.0 is live; the wider 1.1 commercial platform is being completed in controlled stages.
Is PipKey only for WordPress?
No. It is API-first and designed for WordPress, desktop, mobile, SaaS, server, API and other software-delivery models.
Can PipKey work offline?
Yes, where the product policy allows it. PipKey uses time-bounded signed offline assertions rather than permanent offline trust.
Does PipKey store my raw licence key?
The 1.0 design protects licence credentials server-side using keyed digests rather than retaining plaintext licence keys.
Can customers move an activation?
Deactivation and activation policy can allow capacity to be released, depending on the product rules.
What happens when a licence is revoked?
PipKey treats revocation as authoritative. Linked service credentials also fail verification when their linked licence is no longer valid.
Does PipKey process card details?
No. Payment processing belongs to the payment provider. PipKey must not receive raw cardholder data.
Are WooCommerce and Square supported?
Signed ingestion boundaries exist in PipKey 1.0. Fully automated commercial order-to-licence processing is part of controlled 1.1 work and is not presented as generally available until released.
How do I report a security issue?
Email security@pipkey.co.uk privately with enough information to investigate, but do not publish secrets or exploit details before PluginPip has had a reasonable opportunity to respond.
What to include in a support request
- Your product name and whether you are using test or live.
- Approximate date/time of the failure and request/correlation ID if available.
- The operation you attempted and the non-secret error message.
- What you expected to happen and what actually happened.
Never email licence keys, passwords, machine API credentials, private signing keys, peppers or payment-card information.