Pay Mullvad VPN with Crypto (Including Monero)

The privacy stack

Mullvad is the only major VPN that doesn’t require an email, a username, or any identity to register — you get a 16-digit account number and that’s the entire credential. Pay them, add time to the number, use the number to authenticate. The model is designed to minimize what they know about you so they can credibly state they don’t log it.

uSwap’s payment side matches that design. There’s no uSwap account either — you send crypto, you get the account-number credit, the bridge URL is the only artifact. The two stacks layer cleanly: the crypto you pay with can be Monero (best on-chain privacy), the routing is engine-side (no card, no IP-attribution to a wallet), and Mullvad receives a credit attached to nothing but the 16-digit number you give them.

What you can buy

• 1 month — most expensive per-month rate; useful for one-off testing or short trips.
• 3 months — common starter plan.
• 6 months — middle-ground.
• 12 months — best per-month rate for most users.
• 24 months — the lowest per-month if you’re committing for the long haul.

The duration tiers are Mullvad’s standard. uSwap doesn’t mark them up beyond the platform’s normal model (small retail markup on the spend side; 0% on the crypto leg).

Why pay through uSwap instead of Mullvad directly?

Mullvad already accepts BTC and XMR directly. If you hold either of those, going direct is fine — there’s no reason to add a layer.

The case for uSwap is when you don’t hold either. If you have USDT, ETH, SOL, BNB, LTC, TON, or anything else, Mullvad’s direct payment doesn’t accept it. You’d need to swap to BTC or XMR first, send to Mullvad, wait for confirmation, then add time. uSwap collapses that into one step: send what you hold, the engine routes to a payment the Mullvad API accepts, account gets credit.

For users specifically in the privacy crowd, the XMR → uSwap → Mullvad path is roughly equivalent to XMR → Mullvad direct, with one extra non-custodial intermediary. The privacy properties are preserved on the XMR side either way; the difference is whether uSwap also sees the credit happening (it does briefly, doesn’t retain).

What happens after you pay

1. You send the crypto. Bridge page shows the chain confirmation count.
2. The engine routes. You see one rate; the engine does whatever’s needed to land a payment Mullvad’s API will accept.
3. Time gets credited. Mullvad’s API returns the new account expiration; the bridge page shows it. You can verify by logging into Mullvad with your account number and seeing the new time.

Typically under 10 minutes from deposit-confirmed to time-credited. The bridge URL stays available so you can return to verify or initiate the next renewal.

Recovery

Same recovery model as everything on uSwap. If you sent the wrong amount, the engine re-quotes; you pick market-replace, hold, or refund. If Mullvad’s side rejects the credit (account number doesn’t exist, etc.), the intent moves to hold and you can either provide a corrected number or refund.

Practical note on jurisdiction

Mullvad is based in Sweden and complies with Swedish law. The combination of Mullvad’s no-account model and uSwap’s no-account payment doesn’t change that — if a Swedish court ordered Mullvad to retain logs for a specific account number, they would. The “no logs” claim is policy + technical-architecture, not magic.

What this stack does give you is that there’s no easy chain from “this VPN account” to “this real person” because there’s no email, no name, no credit card, no IP-traceable wallet relationship in the payment trail. That’s the design goal of both halves of the stack.