Introduction
I launched a crypto-only store in 48 hours with zero merchant account approvals and no reliance on Stripe. The entire stack runs on Cloudflare Pages and Cloudflare Workers, with NOWPayments handling the crypto rails. This setup costs $0 to start and $20 per month at 1,000 orders. No third-party dashboards, no hidden fees, and your data stays yours. Below is the exact infrastructure I used and the real numbers that came with it.
Domain and DNS on Cloudflare
Buy your domain through Cloudflare Registrar. It costs $8.33 per year and keeps DNS management under one roof. Create a CNAME record pointing your store subdomain to your Cloudflare Pages project. Enable Universal SSL and set SSL/TLS encryption mode to Full. At this stage, your domain infrastructure is live, secure, and ready for the next layer.
Product Catalog in GitHub
Store products in a JSON file in your GitHub repo. Include fields for title, description, price in USD, crypto symbols accepted, SKU, and image URLs. This JSON file becomes your single source of truth for both the storefront and order processing. Push changes via GitHub Desktop or CLI—no complex CMS required. The repo becomes your product database without any external dependencies.
Cloudflare Pages Storefront
Create a Cloudflare Pages project connected to the same GitHub repo. Use the Pages configuration to set the build command to npm run build and the output directory to dist. Select the free Cloudflare Pages plan. In Settings > Functions, set Compatibility date to your current date and enable Fail open for Functions. This gives you serverless rendering for the storefront without cold starts.
Cloudflare Worker for Order Processing
Add a Cloudflare Worker as your order API endpoint. The Worker reads the product JSON from Cloudflare KV and generates NOWPayments invoices on the fly. Each invoice includes the product id, price in USD, crypto list, and callback URL back to your Worker. The Worker writes invoice details to KV with a 24-hour TTL. At 1,000 orders, this Worker costs $0.20 per month. The entire payment flow runs behind Cloudflares edge network with no server to maintain.
NOWPayments for Crypto Checkout
Sign up for NOWPayments. Go to Payment settings and add your stores callback URL. Use the fixed-rate invoice API endpoint: POST https://api.nowpayments.io/v1/invoice. Set the price_amount in USD and price_currency to USD. In the order form on your storefront, submit the product id to this endpoint. NOWPayments returns an invoice_id and pay_address. Redirect the customer to the NOWPayments checkout page. Customers pay in BTC, ETH, USDC, or any supported coin without needing a Stripe account.
Handling Payments and Fulfillment
When a payment is received, NOWPayments pings your Workers callback URL. Your Worker fetches the invoice from KV, verifies the payment amount, and updates the order status to paid. It then triggers a fulfillment workflow—send an email via SendGrid API, update inventory in GitHub JSON, and log the order in a separate KV namespace for analytics. At this stage, the order is complete and your code controls the entire flow.
Real Costs and Performance
In the first month with 72 orders, the total bill was $1.10: $0.90 for Cloudflare KV and $0.20 for Workers. The Pages project and domain remained on free tiers. Page load times averaged 250ms globally thanks to Cloudflares edge. No payment processor took a percentage cut. Your margins stay intact and you own the customer data.
Maintenance and Monitoring
Set up uptime monitoring with UptimeRobot pinging your Worker endpoint every 5 minutes. Use the Cloudflare dashboard to watch Workers metrics for errors and latency. In NOWPayments, enable email notifications for failed callbacks. Review the order log in KV weekly to reconcile any discrepancies. This setup requires under 30 minutes of maintenance per week at our scale.
Scaling Beyond 1,000 Orders
When orders exceed 1,000 per month, upgrade to the Cloudflare Workers Paid plan for $5 per month. This gives you higher KV read/write limits and priority during traffic spikes. NOWPayments scales automatically—no action needed on your side. Total infrastructure cost at 5,000 orders is $25 per month. Margins remain positive even with crypto price volatility.
Conclusion
This stack proves you can launch a crypto store without merchant accounts, Stripe approvals, or third-party dashboards. The infrastructure lives on Cloudflares free tiers initially, then scales predictably. Your code controls the flow, your data stays private, and your margins stay high. If you need a working template, I open-sourced the entire repo last month. Fork it, adapt it, and deploy it in one afternoon.