DEV Community

ChecklistStack
ChecklistStack

Posted on Edited on AI-assisted

Accepting USDT TRC-20 Payments on a 100% Static Site (No Backend, $0/Month)

Most crypto checkout tutorials assume you're running a server. Here's how I accepted USDT TRC-20 payments on a 100% static site — no backend, no API keys exposed, no payment processor. It's been running for 11 days.

The architecture

Visitor → Landing page (static HTML)
       → QR code + wallet address + copy button
       → Pays in their wallet app
       → Gets instant download link (honor system)
Enter fullscreen mode Exit fullscreen mode

That's it. The "payment verification" is the buyer's own honesty: after sending USDT, they click through to the product download. Sounds naive — but for a $19 product with a trust-building free sample, conversion matters more than fraud prevention.

Why honor system works at low price points

  1. Friction kills crypto conversion already. Adding a server-side verification step (waiting for 1 confirmation ≈ 30s+) would drop completion rates further.
  2. The product is software. Worst case leak: a leaked ZIP worth $19. Rate-limit by rotating the download URL token if abuse appears.
  3. The free sample does the trust work. I give away checklist #5 in full. Buyers who want the other 29 have already validated the quality.

The implementation pieces

1. Generate the QR client-side (no external QR API):

// qrcode.min.js bundled locally (~20KB)
QRCode.toCanvas(document.getElementById('qr'), walletAddress, {
  width: 220,
  margin: 1,
  color: { dark: '#000000', light: '#ffffff' }
});
Enter fullscreen mode Exit fullscreen mode

2. Copy button with fallback:

async function copyAddress() {
  await navigator.clipboard.writeText('TA4LE...cFM');
  // visual feedback: change button text for 2s
}
Enter fullscreen mode Exit fullscreen mode

3. The TRC-20 warning (critical):

USDT exists on Ethereum (ERC-20), Tron (TRC-20), and BSC (BEP-20). Send to the wrong network = funds lost. My checkout has a red banner: "TRC-20 network ONLY. Sending via ERC-20 or BEP-20 will result in permanent loss."

4. Instant download via obfuscated URL:

The ZIP lives at a random token path (/dl/RtWqwz_sBcvppMRh.zip) on static hosting. Not security — obscurity. If the link leaks, I rotate the token in one redeploy.

5. Product schema for SEO:

{
  "@type": "Product",
  "name": "30 Business Checklists (PDF Bundle)",
  "offers": {
    "@type": "Offer",
    "price": "19",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock"
  }
}
Enter fullscreen mode Exit fullscreen mode

Verifying payments without a server

I don't — the buyer self-reports by clicking through. But I verify sales via the TronGrid API polled by a cron watchdog:

curl -s "https://api.trongrid.io/v1/accounts/$WALLET"
# parse data[0].trc20["TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t"] / 1e6
Enter fullscreen mode Exit fullscreen mode

Zero-cost sale detection. If I ever need per-order matching, I'd generate a unique "cent suffix" per checkout session (e.g., charge $19.01, $19.02...) so the payment amount itself identifies the order — still no backend, just amount math.

Honest results after 11 days

  • Checkout: live, zero downtime, zero payment errors (also zero payments so far — traffic is the bottleneck, not checkout)
  • Cost: $0/month
  • Build time: ~2 hours including QR generation and copy-paste polish

When you SHOULD graduate to a real processor

  • Price > $50 (fraud risk justifies verification)
  • Refunds needed (crypto doesn't do refunds gracefully)
  • Tax invoices required
  • Buyers expect card payments (crypto-only shrinks your market hard)

For validation-stage digital products though? Static + USDT + honor system gets you selling on day one with no approvals, no KYC, no monthly fees.


The live example is my shop — free sample at the link in my profile if you want to see the funnel flow. Questions about the QR/network-warning details welcome in comments.

Top comments (0)