Purchase policy

One account and one license

A purchase belongs to the Discord account authenticated during checkout. It creates or extends one Mavis license. Concurrent-session add-ons increase the simultaneous session allowance on that license; they do not create additional licenses. An active or paused license renews at its current session count; a new count may be selected after expiry.

Crypto network responsibility

The invoice identifies both the asset and network. BTC on Bitcoin, ETH on Ethereum, USDT on TRON (TRC-20), and USDT on Ethereum (ERC-20) are separate payment rails. Send only the exact asset on the exact selected network to the exact displayed destination.

Quotes and expiry

Every invoice has a durable order reference, exact crypto amount, and expiry. Do not send after expiry. If funds arrive late, the order enters reconciliation; keep the reference and do not pay a replacement invoice for the same purchase. If an older timely payment is discovered after you create a newer invoice, the older payment is held for support review so two orders cannot race the same license.

Underpayment and overpayment

An underpayment cannot be topped up automatically. Do not send a second transfer; keep the order reference and contact support. Overpayments are recorded for reconciliation and never grant arbitrary extra license time or sessions.

Confirmation and delivery

Blockchain detection is not final payment. Mavis waits for the configured confirmation and finality policy. Once paid, license activation retries automatically and idempotently. A delivery delay must not be paid again.

Support and refunds

Contact support with every relevant order reference and transaction hash if automated reconciliation does not resolve an order. Refund availability depends on the payment facts, delivered access, applicable law, and the published terms. Never send private keys or seed phrases to support.