DUNGINX // LEGAL
Refund Policy
DunginX uses order records, payment verification, delivery status, buyer confirmation, disputes, and escrow controls to review digital-product issues. A refund is not automatic simply because an order is digital or because a payment was submitted.
Last updated: August 23, 2026
Before delivery or confirmation
If payment has not been verified, the order remains in its payment state and fulfillment should not be treated as complete. If a verified order has not been delivered, contact Support with the order reference and keep the conversation inside DunginX.
Do not submit duplicate payment evidence or create multiple claims for the same order. This can delay review and make the record harder to reconcile.
Digital delivery and buyer review
Auto-delivery products may be reserved and delivered from available inventory after payment verification. Manual and service products are delivered by the seller through the order workflow. Buyers should verify the received product using the relevant platform’s legitimate redemption or transfer process before confirming receipt.
Once a digital code has been securely revealed or an order has been confirmed, a refund is not guaranteed. The order record, delivery evidence, product description, and applicable dispute review determine what happens next.
Disputes and escrow
If the product is missing, materially different, invalid, or otherwise not delivered as described, open a DunginX dispute from the order page as soon as possible. Provide concise evidence such as screenshots, relevant error messages, and the steps you took. Never include passwords or unrelated credentials.
An active dispute pauses the normal confirmation and fulfillment path while the case is reviewed. Depending on the evidence and resolution, the outcome may include continuation of the seller order flow, a buyer wallet refund, a provider refund where available, or an eligible replacement. DunginX does not promise one outcome for every case.
Payment reversals and exceptions
Payment verification, provider settlement, and refund processing are separate operations. A submitted crypto transaction hash is not proof that DunginX has verified or received the payment. If a provider or administrator approves a refund, the order and payment records are updated through the existing transaction workflow.
For account access, payment, delivery, or refund questions, use the DunginX Support Center and include the order reference without sharing payment secrets.