btc / usdt‑trc20 / xmr only · btcpay self‑host · no fiat in the loop.
On-chain BTC. Pseudonymous, universally accepted, settled via self-hosted BTCPay.
1-conf accepted on amounts under $500, 3-conf between $500 and $5,000, 6-conf above. Receiving address rotated per invoice — never reused.
USD-pegged stablecoin on Tron. Cheapest stablecoin rail, USD-stable across the cycle.
Tron network, ~$1 in TRX gas, ~3 minutes to 19-conf finality. Sending TRC-20 to an ERC-20 address is irrecoverable — verify the network on both ends.
Privacy-by-default rail. Stealth addresses, hidden amounts, ring signatures.
Subaddress rotated per order, view-key only on the receiving side. View key shared on request for transaction proof — read-only, does not authorise spends.
Operator runs BTCPay Server on isolated infrastructure — no third‑party processor in the loop. Invoices are generated server‑side, paid client‑side. No KYC handoff at the payment step.
# Server-side, against the operator's self-hosted BTCPay instance:
POST ${BTCPAY_URL}/api/v1/stores/${storeId}/invoices
Authorization: token ${BTCPAY_API_KEY}
Content-Type: application/json
{
"amount": "32.00",
"currency": "USD",
"metadata": { "orderId": "ord_<id>" },
"checkout": {
"paymentMethods": ["BTC", "USDT-TRC20", "XMR"],
"redirectURL": "https://bullethost.io/order/success",
"expirationMinutes": 60
}
}Self‑hosted BTCPay means the operator owns the funds end‑to‑end — no Coinbase Commerce, no Card2Crypto, no OxaPay sitting between buyer and operator. Funds settle directly to operator‑controlled wallets.
P2P and atomic‑swap only. Centralized KYC exchanges leak the holdings‑to‑identity link.
P2P-first for fiat-to-BTC. Atomic-swap for crypto-to-BTC.
Tron-specific. Verify TRC-20 (not ERC-20) on the destination address before sending.
P2P for fiat-to-XMR. Atomic-swap for BTC-to-XMR / ZEC-to-XMR.