Billing

Billing exists so sync and server features can run. It does not gate the software itself.

The tiers

Falling out of Pro does not delete anything. It pauses the parts of the product that cost us money to run.

Price and what the page shows

The pricing page renders from a published price snapshot with a revision number and an effective date, not from hand-typed numbers. If no snapshot has been published, the page says so instead of showing a stale figure. The buy flow restates the amount before you send anything: both supported assets are USD-pegged USDT, so the figure does not wobble with a conversion rate — but the network, the destination address and the confirmation target all depend on which asset you pick.

Paying

Pro is paid in crypto: USDT on TRC-20 or BEP-20, both USD-pegged. A checkout creates an invoice with its own payment address and amount, and the invoice walks through visible states:

  1. Pending — the address and amount are shown; nothing has been seen yet.
  2. Seen — the transfer appeared on-chain with too few confirmations to credit.
  3. Credited — the required confirmations for that network were reached and your Pro time was added.
  4. Expired / canceled — the window closed; nothing was credited, and a new checkout is cheap.

Under- and overpayments are classified rather than absorbed silently, and the required confirmation count for the network you chose is shown on the invoice. Reorg windows mean a credited payment can, very rarely, need to re-appear; the invoice state is the authority, not your wallet's spinner.

Practical notes that prevent most support tickets:

Renewals, refunds, invoices

There is no auto-renew: a period is exactly 30 days and ends. Crypto transfers are final and non-refundable, which is why the trial exists and why the buy flow repeats the terms before you send anything. Receipts are transactional emails; support tickets opened from a paid account carry their context.