All integration tutorials
JavaCreate → implement → sell

How to license and sell a Java application

Add the Maven SDK, enforce that each key belongs to this product, handle signed offline grace, and sell the application from the same platform.

Build your Store Try live validation
0% PermitCore commission Your payment account Automatic license delivery
Java
Maven dependency
dev.permitcore:permitcore-sdk:2.1.1
import dev.permitcore.PermitClient;

PermitClient client = new PermitClient(
    "https://api.permitcore.dev"
);
var result = client.validate(
    licenseKey,
    appVersion,
    productId
);

if (!result.isValid)
    showActivationDialog(result.message);
One connected workflow

From product record to paid customer

Use PermitCore for the licensing layer and Store checkout. Verified paid evidence triggers the configured license issuance and queues the delivery email; test actual delivery before launch.

  1. 01
    Create

    Create the product and license policy

    In Products, create the software your key unlocks. Choose its activation limit, validity, offline grace period, version range, and feature flags.

    • Create the Java desktop product
    • Set activation and version boundaries
    • Choose an offline grace period
    • Copy the product ID
  2. 02
    Implement

    Install the Java SDK and scope the key

    Put license activation in the first-run flow and validation at startup. Pass your product ID so a valid key for another product cannot unlock this one.

    These are application fragments: supply your own key/product variables and UI or host flow. A validation call does not register a device or reserve a floating session. Check failure before protected work. Offline use needs explicitly configured trusted public keys; follow the SDK 2.1.1 offline setup. For C++, use the vcpkg registry and pinned baseline in its installation reference, rather than assuming a built-in public port.

    dev.permitcore:permitcore-sdk:2.1.1
    • Add the 2.1.1 Maven dependency
    • Activate on the first installation
    • Validate on later launches
    • Pass expectedProductId to every check
    Read the complete Java SDK reference
  3. 03
    Verify

    Test the real validation path

    The shown fragment performs online validation. For SDK 2.1.1 offline grace, first configure trusted public keys, a private cache directory and a stable device ID as described below. Test valid, revoked, expired and wrong-product states, then disconnected behavior after a valid signed proof has been cached.

    Run the public demoSee a real PermitCore API response Open the SandboxExplore the product before signup
  4. 04
    Sell

    Publish the product in your Store

    Connect your chosen Stripe, Paddle or Lemon Squeezy account, add the product to your branded PermitCore Store, and publish. Account credentials, matching catalog prices and signed webhook configuration are required. PermitCore processes the verified payment and handles Store license fulfillment.

    • Create a Store listing for the build
    • Choose pricing for your saved Stripe, Paddle or Lemon Squeezy provider
    • Publish the branded checkout
    • Confirm automatic license delivery
    Follow the Store setup guide
    PermitCore branded Store showing software products ready to buy
    Verified payment triggers license issuance and the delivery email queue.
Before you ship

Java production checklist

The sample is intentionally small. Add these safeguards before making licensing part of a paid release.

  • Run activation work away from the Swing or JavaFX UI thread.
  • Treat a signed offline-grace result as temporary and show its state.
  • Test minimum and maximum version enforcement against actual release versions.
  • Keep the product ID configurable per edition while keeping Admin credentials server-side.
The complete commercial path

Stop at a working sale, not a working API call.

Create the license policy, ship the Java integration, and give buyers a Store where they can purchase it.

Start free Explore all 8 SDK tutorials