Trademark Policy
Paygent's source code is open. The name is not. This page explains the difference, because the two are easy to confuse and the distinction is what keeps “Paygent” meaning one specific thing to the people trusting it with money.
The short version
You may build on Paygent, fork it, modify it, and ship it commercially — the software licence already grants that and this page takes nothing back. What you may not do is use our name or logo in a way that suggests we made, endorsed, or vouch for what you shipped.
What you may do without asking
- Say truthfully that your product works with, integrates with, is built on, or supports Paygent.
- Use the name in ordinary prose, documentation, tutorials, talks and comparisons, including critical ones.
- Keep the name in unmodified copies of our source code, package names, and licence files — you are required to, and it is not a trademark use we object to.
- Link to us.
What needs our permission
- Naming your product, company, app, or domain “Paygent” or anything confusingly close to it — including a modified build distributed under our name.
- Using the Paygent logo or wordmark as your own branding.
- Anything implying endorsement, partnership, affiliation, or official status when none exists.
- Merchandise, domain registrations, or social accounts using the name.
Ask at support@paygent.net. Permission is often given; asking is the whole cost.
“Paygent-compatible” means something specific
Compatibility claims about a payments system are safety claims: a user who believes two things interoperate will move money on that belief. So “Paygent-compatible” is not a matter of opinion here.
You may describe an implementation as Paygent-compatible when it passes the published conformance suite — the capability manifest and the golden fixtures that ship with the SDK, the same ones our own builds are held to. The suite is public, runnable by anyone, and the claim stands or falls on its result rather than on our permission.
If it does not pass, say “works with” or describe what it actually does. That remains entirely fine.
Forks
Forking is expressly welcome and the licence protects your right to do it. Give the fork its own name, and say plainly what it is derived from — “a fork of Paygent” is accurate, permitted, and clearer for everyone than a name that shadows ours.
Ownership
Paygent, the Paygent logo, and associated marks are property of Introspective Labs, Inc. This policy may change; it will not be applied retroactively to punish a use that was permitted when made.
Contact
Questions, permission requests, or a report of misuse: support@paygent.net.