How to Create a Donation Refund Policy for MU Online Servers
Structure a clear donation refund policy for your MU Online server, covering deadlines, eligible cases, chargebacks, and how to avoid financial losses without losing player trust.
Every VIP shop on a MU Online server eventually faces refund requests — whether from genuine regret, a purchase mistake, dissatisfaction with the item received, or, in the worst case, a chargeback fraud attempt. Without a refund policy defined and communicated before the first donation, every case t
Every VIP shop on a MU Online server eventually faces refund requests — whether from genuine regret, a purchase mistake, dissatisfaction with the item received, or, in the worst case, a chargeback fraud attempt. Without a refund policy defined and communicated before the first donation, every case turns into an individual negotiation, prone to inconsistency and accusations of favoritism between players who compared how they were treated. A clear policy, aligned with the Consumer Protection Code and adapted to the payment reality of private servers, protects both the project's cash flow and the community's trust. This tutorial covers the legal fundamentals, eligible cases, the support workflow, and defense against fraudulent chargebacks.
Why every donation shop needs a formal policy
Without a written rule, every refund request gets resolved "in the heat of the moment," which creates two problems: inconsistency (different players get different treatment for similar cases) and legal exposure (online purchases in Brazil have a legally established right of withdrawal, and ignoring it can lead to a formal dispute at the payment gateway or a complaint with a consumer protection agency). Having the policy published in advance on the donation page also reduces the volume of abusive requests, because the player already knows the rules before buying.
Legal basis: right of withdrawal
Brazil's Consumer Protection Code (Art. 49) guarantees consumers the right to withdraw from a purchase within 7 calendar days of receiving the product or service, when the transaction happens outside a physical commercial establishment — which includes purchases made through a website/online store, a category private server donations fall under. This means categorically denying refunds within that window is legally fragile. The recommendation is to structure the policy already aligned with this deadline, rather than trying to deny it and risk a formal dispute.
Cases eligible for a refund
Not every request should be approved automatically. Define objective eligibility criteria:
| Case | Eligible for refund? | Note |
|---|---|---|
| Request within 7 days, item not yet used | Yes | Aligned with the right of withdrawal |
| Duplicate purchase due to checkout error | Yes | Refund the duplicate immediately |
| Item delivered with a system bug/error (not received correctly) | Yes | High priority, resolve quickly to preserve trust |
| Item already used/consumed (e.g. reset applied, VIP already in use) | No, except a documented exception | Make this clear in the shop's terms |
| Request after 7 days without a defect justification | No | Outside the legal withdrawal window |
| Regret after an account ban for cheating/fraud | No | A refund doesn't undo the consequence of a rule violation |
Refund request workflow
- Request received: a single, clear channel (Discord ticket or form), never a random DM to a moderator.
- Eligibility check: check the deadline (7 days), item/benefit usage status, and account history (bans, previous fraud).
- Documented decision: approve or deny with a recorded justification, for future reference in case of a dispute.
- Execution: refund through the same payment method used in the purchase, whenever the gateway allows it.
- Confirmation to the player: a clear message stating the expected reversal timeframe (varies by gateway, usually 5–10 business days).
Cash refund vs. credit/items
The policy can offer friendly alternatives (store credit, equivalent items), but should never force that alternative as the only option when the player demands a monetary refund within the legal deadline — that can be challenged as an abusive practice. A recommended structure:
| Situation | Default offer | Acceptable alternative if the player prefers |
|---|---|---|
| Within the 7-day window, item unused | Cash refund (legal obligation) | Double store credit (optional, if the player agrees) |
| Outside the window, exceptional case approved as goodwill | Store credit | — |
| System error (item not delivered) | Item resend or refund, player's choice | — |
Chargebacks: how to protect yourself
A chargeback is a dispute opened directly with the card issuer, bypassing your support — the player contests the charge and the amount is held/reversed automatically, often with an additional fee charged to the merchant even when the dispute is won. To reduce exposure:
- Always log item/benefit delivery (timestamp, account, IP, item delivered) — this evidence is what you attach when contesting the dispute at the gateway.
- Respond to every chargeback notification within the gateway's deadline (usually 7 to 15 days), even if the response is just "we have delivery evidence, see attachment."
- Prioritize resolving the request directly with the player before they open a formal dispute — it's cheaper and faster than disputing at the gateway, even when you're in the right.
- Consider enabling the gateway's antifraud tools (transaction risk analysis) if chargeback volume is recurring.
Preventing refund fraud
A common abuse pattern: the player uses the purchased benefit (reset, VIP, item) and, after already benefiting from it, requests a refund claiming buyer's remorse. The defense is simple and should be documented publicly before the purchase: a refund is only valid for items/benefits not yet used, verifiable through the system's usage log. Make this rule visible on the donation page itself, not just in an internal document — that alone discourages most attempts.
Communicating the policy to players
Publish the full refund policy on the donation page/shop itself, in plain language, before the payment button. A short summary works better than a long legal text — something like: "Refund available within 7 days, as long as the item/benefit hasn't been used yet. Already-used purchases aren't eligible. Contact us through the #financial-support ticket." This drastically reduces the number of requests that fall outside the criteria, because the player already knows the rules when buying.
Reversal timelines by gateway
The actual time it takes for the amount to be returned varies by payment method and gateway — communicate this to the player to avoid "where's my money" complaints before the normal deadline.
| Payment method | Typical reversal timeframe |
|---|---|
| Credit card | 1 to 2 billing cycles (can take up to 60 days, depends on the issuing bank) |
| Pix | Instant to a few hours, if processed manually by the administrator |
| Boleto | Manual refund via bank transfer, timeframe set by the administrator |
| Gateway account balance (Mercado Pago, PagSeguro) | 1 to 5 business days |
Common errors and fixes
| Symptom | Likely cause | Fix |
|---|---|---|
| Player opens a chargeback instead of requesting a refund | No clear/fast channel for direct requests | Advertise a visible financial support channel in the shop |
| Chargeback dispute lost without evidence | No item delivery log | Log every transaction (timestamp, account, item) |
| Accusations of unequal treatment between players | Refund decisions without documented criteria | Apply published, consistent eligibility criteria |
| Player requests a refund after already using the benefit | No clear rule about already-consumed items | Deny based on the published "not used" policy |
| Recurring losses from card fraud | No antifraud analysis on the gateway | Enable the gateway's risk-analysis tools |
Refund policy checklist
- 7-day deadline aligned with the Consumer Protection Code defined.
- Objective eligibility criteria documented and published.
- Single support channel for refund requests advertised.
- Item/benefit delivery logs recorded for every transaction.
- Chargeback response process defined with gateway deadlines.
- "Already-used item is not eligible" rule published on the shop page.
- Gateway antifraud tools evaluated and, if applicable, enabled.
With the refund policy defined, also review the server's overall monetization structure to make sure the VIP shop and donation system are sustainable long-term — see the MU Online server creation tutorial to understand how this whole economy connects to the project's infrastructure.
Frequently asked questions
Am I legally required to refund donations on a private MU server?
In Brazil, the Consumer Protection Code guarantees the right of withdrawal within 7 days for purchases made outside a physical establishment (including online purchases), which applies to donations treated as the purchase of a virtual item/service. That's why it's recommended to have a formal 7-day policy aligned with the law, instead of trying to deny all refunds outright.
What should I do when a player opens a card chargeback instead of requesting a direct refund?
Respond to the dispute on the payment gateway with evidence of what was delivered (delivery logs, IP, timestamp), but don't rely on that alone — it's usually cheaper and faster to negotiate directly with the player before the formal dispute, since chargeback fees are charged even when you win the dispute on some gateways.
Should I refund in cash or in in-game credits/items?
It depends on the policy you define, but a cash refund is what consumer law actually supports. In-game credits or items can be offered as a friendly alternative, but should never be forced as the only option if the player demands a monetary refund within the legal deadline.
How do I prevent refund fraud, where a player already used the item but asks for their money back?
Define that the refund is only valid if the benefit/item hasn't been consumed yet, verifiable through the usage log. Document this rule publicly before the case happens, and deny refunds on already-used items, making it clear in the purchase notice that the donation is considered consumed upon use.
Is it worth using a payment gateway with stronger fraud protection?
Yes, especially for servers with meaningful donation volume. Gateways like Mercado Pago and PagSeguro offer transaction risk-analysis tools; enabling them reduces exposure to cloned-card fraud, which triggers automatic chargebacks and doubles the loss (lost delivered item + dispute fee).