An overview of the Lancevero model, current content controls, and the matters to agree before enabling payments.
Closed beta. Payments, fund reservation, payouts, refunds, and payment guarantees are unavailable. The payment partner and financial model have not been approved.
Marketplace model
Lancevero supports individually commissioned services: task → independent provider selection → agreement on scope, deliverables, and acceptance criteria. The operator is a Ukrainian individual entrepreneur. Providers may be individuals without sole proprietor registration. There are no paid subscriptions to private channels.
1. Available on the public site
Closed beta features. Availability does not establish that a particular provider was reviewed or that a service was paid for.
Profiles, projects, and profile changes are moderated before publication. Current rules prohibit illegal services, fraud, copyright infringement, and harmful materials.
A journal of initial and follow-up manual checks of descriptions, categories, and links. Records contain a profile snapshot, completed checks, risks, and reasons. Completed records have an immutable history.
Detection of profile content changes and manually scheduled follow-up dates. Content review does not verify identity or enable payments. External and private channels are not monitored automatically.
Message reports and support requests. Moderators operate within their role; visitors to this page cannot access private discussions or contract materials.
Participants can download all terms versions, messages and attachments in a private workroom archive. Files have SHA-256 checksums; the archive is not proof of payment or a signed service acceptance document.
2. Verified only on a local test stand
These additions were accepted on an isolated stand using synthetic data. Test contract execution is disabled in production; a local PASS does not establish an available financial product.
Manual review schedule: the next Kyiv calendar date is 30 days later or earlier; the server rejects a later date for a new completed review. Profile changes, reports and unresolved findings are handled separately. This is not automatic review or blocking.
Delivery → revision request → resubmission → acceptance, version history and access restrictions have been tested on synthetic contracts. QA financial states are simulations only, without money movement.
An email-worker for the responsible operator covers new reports, moderation queues and content changes/review dates. The queue, retries, current permissions and minimal email payload were tested locally; activation and live delivery require separate acceptance.
A QA-only dispute module for UAH contracts supports party statements, explicitly shared evidence, an assigned non-conflicted reviewer and an immutable reasoned report. A separate email queue and explicit recipient acknowledgement are implemented locally; transport acceptance does not prove reading. Budget allocation and the 7% platform fee remain draft_only, not an executable financial instruction.
The offline archive verifier and evidence index help check integrity and locate terms, deliverables and decisions. SHA-256 does not establish identity, authorship, payment or actual service delivery.
3. Proposed for approval
These are open launch conditions, not available payment services or approved participant rules.
Eligibility of a Ukrainian individual entrepreneur as operator and payouts to individual providers without sole proprietor registration; the financial institution, product, and contracts.
Operator KYB, client/provider KYC, sanctions screening, and account ownership: responsibilities, required data, and verification results. Financial KYC is not connected.
Proposed flow: client payment → funds reserved with the financial partner → payout after acceptance, with dispute blocking and cancellation refunds. This is a request for approval, not an available product.
Permitted service categories, follow-up review requirements, and data scope and retention.
Refunds, payment claims, and chargebacks: deadlines, fees, evidence, responsible parties, and funding of possible losses. New financial commitments have not been accepted.
Not yet operational or complete
External profile identity verification is not connected. Financial KYC, sanctions screening and account ownership verification are unavailable. Verified email and moderation do not replace them.
The operational foundation is internally approved: working hours, pilot services, escalation and a manual complaint register. Live notification acceptance and backup monitoring are still required; no substitute or independent conflict reviewer has been appointed. This overview does not establish a public support SLA.
Live dispute notifications require separate activation, delivery verification and a manual fallback. Explicit in-app acknowledgement is separate from internal control dates; without it, a party response deadline is not proven. Local synthetic checks do not constitute real-process acceptance or automatic fault for silence.
A journal risk flag or report decision does not itself unpublish content or block an account or funds. Emergency removal of already published harmful content requires a separately completed and tested procedure.
How to assess the demonstration
A demonstration should show real actions and persisted results: profile → manual review → history; report → explicitly submitted evidence → decision; terms version → delivery → revisions/acceptance → archive. The local test stand and synthetic data must be labeled. Workrooms and their exports are participant-only, not accessible to visitors of this overview.
The existing video overview is an edit of actual local test screens, not a continuous process recording or a KYC video. A new continuous recording has not been prepared; a working identity verification video requires that integration first. Private evidence and test access are not published.
Current documents and drafts
The contact page, terms and privacy policy below describe the current closed beta. The operational foundation and 7% product fee model are internally approved; contract drafts covering KYC, refunds, disputes, chargebacks and service documents do not replace current terms and require appropriate legal drafting and approval. Service documents, signatures and tax roles for providers without sole proprietor registration remain to be defined.