From registration to digital license delivery
The purchase flow is designed so the license is issued to a specific account, linked to project parameters, and made available in the customer account after payment confirmation.
How it works
-
01
Registration or sign-in
The user creates an account or signs in. The account is required for order history, licenses, downloads, and support requests.
-
02
Build selection
The user selects a supported Lineage II client or chronicle in the purchase form. The list is managed by administrators and displayed before payment.
-
03
Project parameters
The user enters the connection domain and technical data required to generate the license and protection files.
-
04
Terms review
Before invoice creation, the website displays the price, digital delivery rules, terms of use, refunds, and license restrictions.
-
05
Invoice and payment
An invoice is created through the payment gateway. The user opens the payment page and completes payment in the invoice currency.
-
06
Automatic verification
The website receives a server-side notification and verifies order, amount, currency, and invoice status. A redirect from the payment page alone does not issue a license.
-
07
License delivery
After successful verification, the order is marked as paid, the license appears in the account, and client/server files become available for download.
-
08
Post-purchase requests
For payment, license, refund, or security questions, the user opens a ticket in the account or uses the public contact form.
What is controlled at each stage
- buyer account and order ownership;
- final invoice amount and currency;
- unique public order identifier;
- payment status from the payment provider;
- license binding to selected client or chronicle and domain;
- download access only from the owner account.
Where to start
Open the pricing page, then proceed to the customer account to create a personal invoice and receive the license after payment.