Integrations
Using Ulises Licenses with Polymart
Sell Minecraft plugins on Polymart and enforce licenses with Ulises Licenses. Learn what integrates, how buyer activation works, and what stays separate.
Ulises Licenses works alongside Polymart sales: the storefront and transaction stay on Polymart while sellers issue Ulises license keys with per-server verification, HWID binding, and watermarked updates. Marketplace licenses are never imported; each system keeps its own records.
Polymart is a Minecraft marketplace for plugins, setups, and services where buyers purchase resources from independent sellers. Sellers remain responsible for how their resources are protected, and external licensing systems are an accepted way to do it.
With Ulises Licenses, the split is clean: Polymart handles the storefront and the transaction, Ulises handles keys, per-server verification, HWID binding, watermarked updates, and revocation.
Storefront stays on Polymart
Your listing, reviews, and checkout all remain on Polymart exactly as buyers expect.
Keys issued per buyer
After each sale, create a license in the dashboard and deliver the key to the buyer through Polymart's buyer communication.
Enforcement inside your plugin
UlisesLib verifies the key on every server, with HWID and IP limits you configure per product.
Leak tracing
Watermarked per-license downloads identify the source when a jar shows up where it should not.
How Polymart Integration works
- 1
Sell as usual
Publish and sell your resource on Polymart under their marketplace rules.
- 2
Issue the key
Generate the buyer's license in Ulises Licenses and send them the key.
- 3
Buyer activates
The buyer configures the key once. Verification, resets, and updates then run through Ulises Licenses.
Polymart Integration questions
Does this import my Polymart licenses?
No. Polymart purchases and Ulises licenses are separate systems with no automatic sync. Polymart records who bought; Ulises controls where it runs.
Is external licensing accepted on Polymart?
Sellers commonly protect resources with their own license systems alongside the marketplace purchase. Always confirm against the current Polymart terms before relying on this.
What happens on a refund or chargeback?
Revoke the Ulises license. The marketplace purchase record is unchanged, but the plugin stops verifying.
Without Ulises vs with Ulises
| Task | Manual | With Ulises |
|---|---|---|
| Issuing licenses | Copy-paste keys over DMs | Dashboard, bulk CSV, and Discord bot |
| Verification | None, or home-grown checks | Cloud API with signed responses |
| HWID and IP limits | Manual policing | Automatic enforcement with resets |
| Updates | Re-upload and re-share files | Auto-update with checksum verification |
| Leak tracing | No trail | Per-license watermarks |
| Revocation | Push a new build and hope | One click, effective on next check |
Related solutions
Java & Kotlin Licensing
Protect any JVM application with UlisesLib: Gradle and Maven setup, license verification, HWID binding, and automatic updates for Java and Kotlin software.
Minecraft Plugin Licensing
License protection for PaperMC and Spigot plugins with per-server HWID binding, IP limits, support-driven resets, watermarked downloads, and Discord management.
BuiltByBit Integration
Sell Minecraft plugins on BuiltByBit and enforce licenses with Ulises Licenses. Learn what integrates, how buyer activation works, and what stays separate.