License
The core of the DaxPay open-source payment platform is released under the GNU Lesser General Public License v3.0 or later (LGPL-3.0-or-later), protected and limited by the laws and regulations of the People's Republic of China. The core software charges no license fee; read the open-source license, the user authorization agreement, and the applicable terms of each component before use — if you do not agree, do not use it.
Copyright © 济南易杯光年软件技术有限公司.
Key Points of LGPL-3.0-or-later
The LGPL (Lesser GPL) is a variant of the GPL designed for libraries and more permissive than the GPL. The core difference lies in how "linking" is treated:
| Usage | Must you open-source your code? | Notes |
|---|---|---|
| Via API / network calls | Usually no | Business systems calling DaxPay over its HTTP APIs usually need not disclose business code for this reason |
| Dynamic linking | No | Business code may stay closed-source when dynamically linking an LGPL library |
| Static linking | Yes | Statically linking an LGPL library requires open-sourcing your business code, or providing relinkable object files |
| Modifying license-covered source code | Yes | Modifications to DaxPay source code covered by the license must be provided under LGPL terms |
Typical DaxPay usage
In the vast majority of scenarios, business systems call DaxPay (an independently deployed payment service) over RESTful HTTP APIs. That counts as "network calling", and business code usually need not be disclosed for it; commercial use must still comply with the LGPL, the user authorization agreement, and the applicable requirements of third-party components and payment channels.
Commercial Use
LGPL-3.0-or-later allows commercial use as long as the license conditions are met. Specifically:
- ✅ Commercial licensing — the core software charges no license fee; enterprises may use it in commercial projects under the license
- ✅ SaaS services — you may offer SaaS payment services based on DaxPay
- ✅ Closed-source business code — business systems calling DaxPay via APIs may keep their code closed
- ✅ Secondary development — you may modify the source to fit your own needs (modifications to DaxPay itself must be open-sourced)
- ✅ Private deployment — you may deploy in internal private environments without publishing your configuration
Modifications must be open-sourced
If you modify DaxPay source code covered by the license (rather than merely calling its APIs), you must provide the modified source under LGPL terms. When you only call the HTTP APIs, business code usually need not be open-sourced for this reason.
Commercial License
The open-source edition is under LGPL-3.0-or-later and allows commercial use under the license. If you need to keep modifications to DaxPay source code closed-source, or want dedicated support, inquire about a commercial license; the scope of a commercial license is governed by the contract.
Open-source License vs Commercial License
| Dimension | Open-source (LGPL-3.0-or-later) | Commercial license |
|---|---|---|
| Cost | Core software free of license fee | Quoted by license scope and value-added services |
| Commercial use | ✅ Allowed | ✅ Allowed |
| Closed-source modifications | ❌ Modifications must be open-sourced under the LGPL | ✅ Modifications need not be open-sourced |
| Deep customization | Bound by the LGPL | No open-source obligation |
| Technical support | Community groups | Dedicated group + ticket support |
| Code access | Public repositories | Aliyun Codeup private registry |
When you need a commercial license
- You modified DaxPay source code and want to keep those modifications closed-source
- You want dedicated technical support and prioritized issue response
- If you only call the APIs (without modifying the source), the core software usually requires no purchased license — but deployment, channels, operations, and customization services may still incur costs
Edition Selection
DaxPay commercial editions are quoted by license scope and value-added services; the official payment-platform commercial edition currently starts at ¥9999. Business subsystems such as POS and restaurant management use independent key-based licensing and are not included in the payment-platform commercial license. The full scope is subject to the official pricing page and the contract.
Contact for Purchase
Add the assistant on WeChat (sdcit2020) to inquire about commercial licensing and edition selection.
Your Obligations
When using DaxPay, you must comply with the following obligations:
- Keep copyright notices — retain the original copyright and license notices when distributing or deploying
- Open-source modifications — modifications to DaxPay license-covered source code must be provided under LGPL terms
- Attribute the source — derivative works must state that they are based on DaxPay
Full License Texts
- LGPL v3.0 license text (English)
- LGPL v3.0 license text (Chinese translation)
- GPL v3.0 license text (the LGPL is based on the GPL)
Disclaimer
This page is a plain-language explanation of LGPL-3.0-or-later and does not constitute legal advice. If in doubt, read the license text or consult a professional legal adviser. The original LGPL text prevails.