Introduction
Stripes email still sits in my inbox: We regret to inform you that your application was not approved. I knew the rejection wasnt about me; it was about my address. That serverless store on Netlify needed a database, an API, and a payments path that respected African rails. Supabase provided all three. I swapped Firebase for Supabase, connected NOWPayments for crypto and fiat rails, and deployed the storefront on GitHub Pages with a Cloudflare Worker proxy that masked my origin IP. The result: customers in Nairobi, Accra, and Johannesburg can buy without ever leaving their preferred payment method. This is how we did it.
A Standalone Order Database That Is Actually Yours
Supabase gave us a Postgres database under our control with Row-Level Security turned on. We created a stores table, an orders table, and a customers table—all linked by foreign keys. Row-Level Security rules meant only the store owner could read or write orders, and customers could only see their own records using a signed JWT from the Worker. No Firebase lock-in, no hidden query charges. We ran one SQL migration file in the Supabase SQL editor; the schema was live in seconds.
Indexes were critical. We added a GIN index on the order_items array to speed up product lookups. We created a partial index on orders(status, created_at) so the Worker could fetch only pending orders for webhook retries. The total cost? $0 for the first 2 GB of data. That alone saved us from paying Firebases $25 minimum for Firestore.
Frontend on GitHub Pages, Backend on Supabase Edges
GitHub Pages served the static storefront. Cloudflare Workers intercepted every request and rewrote URLs to the Supabase Edge Functions endpoint running in the same region (we chose Frankfurt). The Worker also attached the customers JWT token to each call, so Supabases RLS could enforce ownership.
We used htmx for the cart and checkout to keep the bundle under 20 KB. When a customer clicked buy, the Worker POSTed the line items to Supabases /orders edge function. The function validated stock against the products table, reserved inventory in a transaction, and returned a NOWPayments checkout URL. The entire round trip took 300 ms in Lagos traffic.
Payments That Skip Stripe: NOWPayments Is the Hack
NOWPayments supports M-Pesa, bank transfers, and 80+ cryptocurrencies. We generated a single checkout link per order using their Create Payment endpoint. We set the success and fail URLs to our Workers receipt handler, which updated the order status and fired a Supabase real-time broadcast so the customers cart refreshed instantly.
Mobile money was the highest-volume channel. We used NOWPayments auto-conversion off-ramp to bank accounts, so customers paid via M-Pesa USSD and we received naira in our Flutterwave wallet the same day. No Stripe means no fees on cards we cant accept; NOWPayments charges 0.5% for conversion plus the mobile operator fee. Still cheaper than PayPals 4.4% + $0.30.
Real-Time Inventory Without a Dedicated Socket Server
Supabases PostgreSQL LISTEN/NOTIFY runs on the Edge Functions runtime. When a Worker reserved stock, the edge function sent a notify to a TypeScript listener that updated the products table and broadcasted the change. We turned the inventory feed into an SSE stream that htmx listened to on the product page. Result: stock numbers update under a second even on 4G in Kumasi.
Deployment Playbook That Fits an Afternoon
1. Create Supabase project → Enable Edge Functions and realtime. 2. Run SQL migration in editor → copy connection string to Worker secrets. 3. Write Cloudflare Worker in Wrangler → bundle with esbuild. 4. Publish Worker → bind custom domain via Cloudflare DNS. 5. Push static storefront to GitHub → enable Pages → DNS to GitHub. 6. Add NOWPayments webhook secrets to Worker. 7. Test on WhatsApp with a customer in Tema. 8. Celebrate when the first order arrives 20 minutes later.
Total infra cost: $5 (Cloudflare Workers free tier + Supabase free tier). Total time from repo clone to live store: 6 hours on a Saturday.
Conclusion
We started this project because every payments guide assumed Delaware C-Corp and a Stripe blue check. We proved that an open-source stack—Supabase, NOWPayments, Cloudflare, GitHub Pages—can run a full digital store without Stripes approval. The infrastructure is ours, the fees are ours, and the slowness of legacy gateways is no longer ours to wait on. If youre in Lagos, Nairobi, or Accra and Stripe says no, this is the path to owning your storefront before Monday morning.