> For the complete documentation index, see [llms.txt](https://magverse.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://magverse.gitbook.io/docs/core-mechanism/dispute-resolution-policy.md).

# Dispute Resolution Policy

### 1. Purpose

This policy defines how disputes are raised, reviewed, and handled on MagVerse.

MagVerse aims to provide a structured and fair process for resolving disagreements between merchants and curators while maintaining platform efficiency and trust.

***

### 2. Scope of Disputes

Disputes may arise in situations including but not limited to:

* disagreement on task completion or quality;
* mismatch between deliverables and task requirements;
* rejection of submitted work;
* delayed or withheld payments;
* suspected rule violations or misconduct.

***

### 3. Dispute Initiation

A dispute may be initiated by either a merchant or a curator.

To raise a dispute, users should:

* contact MagVerse support through official channels;
* provide relevant details, including:
  * task ID;
  * submission links or proof of work;
  * description of the issue;
  * any supporting evidence (e.g., screenshots, timestamps).

Incomplete or unclear submissions may delay the review process.

***

### 4. Review Process

Once a dispute is submitted:

* MagVerse will review the case based on available information;
* both parties may be asked to provide additional clarification;
* platform rules, task requirements, and submitted evidence will be considered.

MagVerse may use internal tools or system data to assist in the review process, but final decisions are made through platform judgment.

***

### 5. Settlement During Disputes

If a dispute is active:

* the associated settlement may be **temporarily paused**;
* payout will not be processed until the issue is reviewed and resolved.

This aligns with the platform’s T+3 settlement and safeguard framework.

***

### 6. Resolution Outcomes

After review, possible outcomes include:

* **Approval of submission** → settlement proceeds;
* **Rejection of submission** → no payout;
* **Partial acceptance** → adjusted payout (if applicable);
* **Request for revision or clarification** before final decision.

All outcomes are determined based on task rules, evidence, and platform standards.

***

### 7. Platform Role

MagVerse acts as a **coordinator and reviewer**, not a binding arbitrator.

* Decisions are made in good faith based on available information;
* MagVerse does not guarantee that all parties will agree with the outcome;
* ultimate responsibility for collaboration remains with users.

***

### 8. Abuse and Misconduct

MagVerse reserves the right to take action in cases of:

* fraudulent behavior;
* manipulation of task results;
* repeated low-quality or non-compliant submissions;
* misuse of the dispute process.

Actions may include:

* suspension of payouts;
* restriction of account activity;
* removal from the platform.

***

### 9. Processing Time

* Disputes will be reviewed as promptly as possible;
* resolution time may vary depending on complexity and responsiveness of involved parties;
* MagVerse does not guarantee a fixed resolution timeline.

***

### 10. Best Practices

To reduce disputes, users are encouraged to:

* clearly define task requirements (merchants);
* carefully review requirements before submission (curators);
* maintain clear and verifiable records of work;
* communicate promptly when issues arise.

{% hint style="info" %}
Repeated disputes without valid grounds may affect account standing.
{% endhint %}