Refund policy

Define when an order is considered accepted and how failed or duplicate supplier operations are handled. A payment capture must not be treated as proof that a domain was registered. Refund or reversal timing must match the payment provider and applicable law.

Domain registration and renewal fees may be subject to registry, supplier and statutory rules. Specify the cases in which cancellation or a refund can be requested, any unavoidable third-party charges, and the process for correcting an error. Do not promise a universal refund or a universal no-refund rule.

Explain the renewal cut-off, payment authorization, expiry notices, grace and redemption periods for each registry, where available. Exact dates and fees depend on the TLD and supplier and must be surfaced from current provider data.

Marketplace checkout and settlement are disabled until a compliant supported settlement service is configured. Publish the buyer and seller cancellation, transfer-failure, dispute and payout rules only after that flow has been tested and reviewed.

Contact Support with the order reference and a description. Never include full card details or domain authorization codes in a support message.