Which Usenet providers take Bitcoin — and which actually keep it private
"Accepts Bitcoin" tells you nothing on its own. The processor behind the checkout decides whether you stayed anonymous or just handed your ID to BitPay.
People pick Bitcoin for Usenet for one reason: to pay without tying a real name and card to a download account. So it is worth saying plainly — a “we accept Bitcoin” badge does not deliver that on its own. What decides it is who sits between you and the provider at checkout.
The processor is the whole story
There are two very different ways a provider can “accept Bitcoin.”
Directly — the provider shows you a native BTC address (often through self-hosted, open-source BTCPay Server) and you pay it. No third party, no account, usually nothing asked of you beyond an email for the receipt.
Through a hosted processor — the checkout hands you off to a company like BitPay or CoinPayments, which takes the coins, does compliance, and settles fiat to the provider. That middleman is where your anonymity goes to die.
The coin is identical. The privacy outcome is not.
Why BitPay defeats the point
BitPay is a licensed money-services business, so it runs full AML/KYC. It collects information on shoppers as a matter of policy, and above modest thresholds — or for any refund — it requires a verified BitPay ID: government photo ID plus a selfie. Its enhanced due-diligence and transaction-monitoring rules only tightened under the 2026 crypto regulations.
Read that back against why you reached for Bitcoin. You wanted no name attached to the account. Pay through BitPay and you have handed a regulated US company your identity and the exact merchant, amount, and date — a cleaner record than a credit card would have left. The provider sees less; the processor sees everything. For a privacy-motivated payment, that is strictly worse than nothing.
CoinPayments is lighter than BitPay but still a custodial intermediary with its own data retention and policy surface. The rule of thumb: any party that takes custody of the coins can be made to talk about who sent them.
Telling them apart at checkout
You do not need the provider’s marketing copy — the payment page tells you everything:
- Redirect to
bitpay.com(or it asks for your email/identity to “verify the payment”) → hosted processor, treat it as KYC. - A raw BTC address or QR shown on the provider’s own domain, or a BTCPay Server instance → direct, anonymity intact.
- “Crypto via our partner …” → assume hosted until you see otherwise.
When in doubt, start the checkout in a throwaway session and watch where it sends you before paying a satoshi.
Where things stood at the time of writing
Payment plumbing changes quietly, so verify at checkout rather than trusting any list — including this one. As of writing:
Tend to take Bitcoin directly: Usenet.Farm (long known for anonymous, email-only accounts), XS News, Frugal Usenet, ViperNews, Blocknews, UsenetNews, CheapNews.
Route Bitcoin through BitPay: Astraweb, UsenetExpress, NewsDemon, NewsgroupDirect, Newsgroup.Ninja, HitNews, theCubeNet, StingyUsenet.
Note that a provider can switch processors without changing a word on its pricing page, and several brands above sit on shared backends, so the checkout flow is the only source of truth.
The other half: where the coins came from
A clean payment rail does not fix coins bought with your name. If the BTC came straight off a KYC exchange and went wallet-to-provider in one hop, the chain still links your verified identity to the payment. If anonymity is the goal, the acquisition side — non-KYC sourcing, a little distance between purchase and spend — matters as much as avoiding BitPay. That is a longer topic, but worth holding in view: the privacy of a payment is only as strong as its weakest end.
The takeaway is small and durable. The question is never “do they take Bitcoin.” It is “do they take it without a middleman who quietly undoes the only reason you’re paying in Bitcoin.”