Refund and refill policy, in plain language.

Scope of this policy

This policy applies to eligible Discord member purchases made directly through DiscordBooster. It describes the standard process for offline-member and online-member orders.

Separate or custom services may have additional written conditions disclosed before payment. Where mandatory consumer law provides rights that cannot be excluded, those legal rights continue to apply.

Refill eligibility

An order may qualify for a refill when all of the following are true:

• The request is made within 30 calendar days after the order was marked complete.
• The delivered member count has fallen below the eligible delivered quantity.
• The customer provides the correct order ID, order email, and current member count.
• The original server remains available and the invite supplied for the refill works.
• The loss is not caused by an exclusion described below.

An approved refill replaces the eligible shortfall up to the amount covered by the original purchase. More than one eligible request may be reviewed during the original coverage window, but a refill does not restart or extend that window unless support explicitly confirms otherwise in writing.

Refill exclusions

A request may be ineligible when the shortfall cannot reasonably be attributed to the covered delivery. Common exclusions may include:

• The server was deleted, transferred, made inaccessible, or substantially reconfigured.
• The invite expired, reached its use limit, was revoked, or stopped working.
• Members were manually removed, banned, pruned, or affected by moderation settings.
• Another provider delivered members to the same server during the coverage period, making the source of the shortfall impossible to determine.
• The order involved unsupported content or violated the acceptable-use requirements.
• The request was submitted after the coverage period ended.
• The customer supplied inaccurate information or attempted to manipulate the count.

DiscordBooster should explain the reason when declining a request and retain the relevant order record.

Order cancellations

A cancellation request should be submitted immediately through support. An order may be cancellable when payment has cleared but delivery has not begun and no irreversible processing cost has been incurred.

Once delivery begins, the order may be partially or fully non-cancellable. If only part of an order can be stopped, any available refund is based on the undelivered portion of the purchase.

Refund eligibility

Subject to applicable law and this policy, a full or partial refund may be considered when:

• DiscordBooster cannot begin or complete the purchased service.
• An eligible cancellation is accepted before delivery starts.
• A duplicate charge is verified.
• A payment was taken for a service shown as available but cannot be supplied.
• Another remedy required by applicable consumer law applies.

A change of mind after delivery begins, dissatisfaction with organic engagement, failure to read the online/offline product distinction, or results outside the service description may not qualify by themselves.

Approved refunds are returned to the original payment method where technically and legally possible. For cryptocurrency payments, support will confirm the supported destination and refund amount before processing.

Payment disputes and processing

Customers should contact support before opening a payment dispute so the order can be investigated. This does not remove any legal right to dispute an unauthorized or incorrect charge.

DiscordBooster reviews refund requests after receiving the required order information. Once an approved refund is submitted, the time needed for funds to appear depends on the payment method, payment processor, and customer’s financial institution.

How to submit a request

Use the support form and choose the relevant order or refill topic. Include:

Never include a Discord password, token, two-factor code, full card number, private key, or wallet recovery phrase.

Policy updates

Material changes should be published with a new effective date. Unless applicable law requires otherwise, the version presented at the time of purchase should govern that order.

Previous policy versions should be retained internally and made available when reasonably required to resolve an older transaction.