Frequently asked questions

Choose Create Account, provide a valid email, username, and password, and complete the verification step sent to your inbox. Use only the canonical DunginX domain when opening an authentication link.

Open the verification message and follow its secure link to the DunginX authentication callback. If the message expires, return to Login and use the resend option where available.

Open Forgot Password, submit the email associated with your account, and use the reset message to set a new password. DunginX does not display internal authentication errors or ask you to send your password to Support.

Open account settings and use the username control when it is available. Usernames must follow the platform rules and can be subject to uniqueness or update limits. Your email remains separate from your public username.

Your email is used for account and operational communication. It is not intended to be a public seller identity; public seller surfaces use the seller profile identity configured for the storefront.

Use a unique password, protect your email account, avoid suspicious links, and keep credentials out of messages, tickets, listings, and checkout fields. Report unfamiliar activity through Support.

Review the product description, region, delivery method, quantity limits, and seller information, then add the product to your cart and complete checkout. The server validates the final price, quantity, payment, and inventory state.

Checkout rechecks the cart against current product configuration, quantity rules, payment settings, and inventory. Review the final effective price and total before placing the order; the server, not a stale browser value, is authoritative.

Region describes the supported market, currency, or account area for the product. Select a product that matches the destination account or redemption environment; Global means the seller has marked it for broader supported use, not unrestricted use everywhere.

Some products offer a lower unit price when the requested quantity reaches the seller’s configured minimum and stays within its maximum. The final wholesale decision is made server-side and is stored in the order snapshot.

Auto-delivery products may be delivered from reserved inventory after payment verification. Manual or service products are fulfilled by the seller. Order emails do not contain digital codes; use the secure order view.

Review the delivered product using the legitimate supported game or service process. Confirm the order only when it is correct. If something is wrong, open a dispute instead of confirming.

The order remains in its delivery and confirmation workflow until the existing confirmation window or dispute process determines the next step. Do not confirm while a problem is unresolved; open a dispute when the order is not as described.

Use Become Seller and complete the current application requirements shown by DunginX. Approval is controlled by the marketplace team and seller capability is granted through the existing seller relationship.

Approved sellers can create listings in the Seller workspace, select a category, define pricing and region, choose the delivery method, and provide accurate fulfillment guidance. Never request a buyer’s password.

Seller earnings move through the existing order and escrow lifecycle. A completed order enters pending seller balance, remains pending for the configured period, and then becomes available balance when the settlement rules allow it.

Buyer-side fees are not seller earnings. The seller receives the applicable order amount minus seller platform fees, subject to completion, the pending period, and any active dispute or settlement hold.

Request a withdrawal from the Seller wallet. Administrator approval and payout completion are separate steps; approval does not by itself mean external funds were sent.

The order-specific dispute workflow pauses the relevant confirmation and fulfillment path while evidence and responses are reviewed. Keep the conversation in the dispute workspace and wait for the recorded resolution.

Open the order in your Buyer workspace and use the dispute action when the order qualifies. Explain the problem and attach relevant evidence without including passwords, recovery codes, or unrelated credentials.

Use the DunginX buyer–seller conversation linked to the order. Keeping communication on the platform preserves context and makes it easier to review delivery questions or evidence.

Provide clear screenshots, redemption errors, timestamps, and a short description of what you attempted. Do not provide account passwords or sensitive credentials.

DunginX reviews the order record, payment and delivery state, messages, evidence, and applicable marketplace rules. The recorded outcome may continue fulfillment, issue a refund, or handle an eligible replacement; no single outcome is guaranteed for every case.

An active dispute blocks normal confirmation and relevant fulfillment transitions while the case is reviewed. The resolution workflow determines whether escrow continues, a refund is issued, or an eligible replacement is handled.

DunginX uses payment verification, order snapshots, delivery states, authenticated messaging, dispute review, and escrow boundaries. These controls reduce risk but do not make an off-platform or unsupported trade safe.

Sellers get a recorded order, verified payment gate, private fulfillment context, order-authorized messaging, delivery state, and a defined dispute process. Sellers should provide accurate listings and proof of delivery while keeping their own account credentials private.

On-platform communication preserves the order context and gives the buyer, seller, and Support team a shared record. Be cautious when someone pressures you to continue through a private account or unfamiliar link.

Check the domain before signing in. DunginX links use `dunginx.com` or the appropriate canonical subdomain such as `dashboard.dunginx.com`, `admin.dunginx.com`, or `support.dunginx.com`. Do not use a link that asks for your password outside the normal authentication flow.

Never share your DunginX password, email password, recovery code, one-time authentication code, payment secret, or game account password in a listing, chat, ticket, or dispute.