Seller Protection Policy

When an order is placed, it becomes an active transaction tied to the listing details and the order record. This confirms buyer commitment and establishes a clear reference for what must be delivered and how acceptance works.

• Buyer commitment is recorded → the order is active before delivery begins.
• Listing scope governs the order → what’s included, excluded, and supported is documented.
• Review follows delivery → acceptance is based on the stated scope.
• The order record serves as reference if a dispute is raised.

• Deliver the project as described in the listing – including stated features, assets, and exclusions.
• Provide delivery using the declared method (repository access or download) and confirm access.
• Include clear setup documentation when required.
• Keep communication within the order so the record can support you if a dispute arises.

After delivery, the buyer reviews the project against the listing scope. If the delivered materials match what was promised, acceptance finalizes the order and moves it to payout.

If a buyer claims the delivery does not match the listing, the dispute is reviewed against the documented scope and the order record. Both parties may be asked to provide supporting evidence such as messages, files delivered, access confirmation, and timelines.

• Finalize payout to the seller when delivery matches the listing
• Full refund when delivery was not provided
• Partial refund when only part of the scope was delivered
• Split outcome in rare, case-specific situations

Payment becomes available after the buyer accepts delivery, or after the review window ends if no dispute is opened. This structure ensures sellers are paid when the documented scope is delivered.

• Off-platform payments or moving the transaction outside Mehor.
• Failure to deliver the promised scope, required files, or documentation.
• Using unlicensed assets, violating IP rights, or reselling restricted content.
• Missing agreed delivery expectations stated in the listing or order record.
• Large changes, new features, or ongoing work not included in the listing scope.