Refund and Dispute Policy

Scope

This version explained how refunds were reviewed on RSBazaar. Decisions depended on the order record, delivery evidence, buyer and seller messages, dispute timing, payment status, and the protection terms shown for the product.

What applied to buyers

Buyers had to start from the order page when something was wrong and keep messages, delivery proof, screenshots, usernames, worlds, timestamps, and the exact issue inside the order thread so support could review the full record.

Standard order disputes were normally reviewed before the order became final. Account-related protection or other product-specific coverage could continue only when the order page said that coverage was still active.

What applied to sellers

Sellers had to provide clear delivery evidence, answer support requests quickly, and keep fulfillment on-platform. Seller proceeds could remain held while a refund request, dispute, safety review, or payment reversal was being reviewed.

Wallet and payment returns

Wallet refunds were credited to the RSBazaar balance when that was the outcome. Outside payment methods could take additional time after approval. The order or wallet record showed the refund amount and status where available.

Buyer payment fees were tracked separately from the seller order subtotal. If a fee was refunded, retained, or affected by a payment reversal, the support outcome was expected to explain that result.

What was not covered

Refund protection did not cover false reports, abusive chargebacks, off-platform deals, fake evidence, stolen payment methods, refund farming, collusion, or attempts to avoid the order dispute flow. Those actions could lead to wallet holds, withdrawal limits, account restrictions, or a permanent ban.

Next steps

Users were directed to Support with the order ID, payment transaction ID shown on the receipt if available, screenshots, delivery proof, and message timestamps. The Terms of Service explained marketplace rules applying to every order.