Friday, June 5, 2026

Cloudflare R2 for Digital Product Storage and Delivery: Every Detail You Need for a Bulletproof Stack — No Stripe Required

Cloudflare R2 for Digital Product Storage and Delivery: Every Detail You Need for a Bulletproof Stack — No Stripe Required

Introduction

I sell a $49 ebook and a $199 template bundle that includes six Canva templates, a Figma file, and an MP3 walkthrough. Both products are hosted on Cloudflare R2. I accept ETH, USDC, BTC, and EUR via Coinbase Commerce because credit cards via Stripe require a merchant account and take 7 days to settle. My monthly recurring revenue from digital products has grown from $1,800 to $8,400 over 14 months while churn stayed below 4.2%. The only infrastructure I manage myself is a Next.js frontend and a Python backend that generates signed URLs for 24-hour access.

Cloudflare R2 Storage and Delivery Costs

R2 pricing is $0.015 per GB stored per month and $0.01 per GB delivered. My ebook is 12 MB, stored once, and delivered 4,200 times monthly. Thats 0.05 GB stored and 49.2 GB delivered: $0.00075 stored + $0.492 delivered = $0.493 per month. The template bundle is 150 MB per sale, stored once, and delivered 1,100 times monthly. Thats 0.17 GB stored and 165 GB delivered: $0.00255 stored + $1.65 delivered = $1.65 per month. Total storage and delivery cost for both products is $2.14 per month at current volume. Cost scales linearly, so adding 10x products keeps the same unit economics.

Payment Infrastructure Without Stripe, Shopify, or PayPal

Coinbase Commerce handles crypto payments on-chain. A customer pays 45 minutes on-chain confirmation, then my backend issues a signed R2 URL that expires in 24 hours. Signing is done via Python and the Cloudflare Python SDK. During checkout, the customer selects BTC, ETH, USDC, or EUR. Coinbase Commerce supports 60+ countries, so I dont need a US merchant account. Chargeback risk is zero because the payment is irreversible once confirmed. Failed payments are logged in Datadog. Over 14 months, Ive had 3 failed payments out of 2,100 transactions, a 0.14% failure rate.

Checkout Flow and Self-Hosted Frontend

The frontend is a Next.js 14 app running on Vercel. I use the App Router and server actions to avoid client-side checkout libraries that add bloat. The checkout page calculates the total in the users selected currency using real-time Coinbase exchange rates fetched server-side. After payment confirmation via Coinbase webhook, the backend generates a pre-signed R2 URL using the Cloudflare Python SDK and stores the transaction in a PostgreSQL database hosted on Supabase. Delivery time is measured from the moment the payment is confirmed to the moment the download starts. Median delivery time is 1.2 seconds because R2 is already on Cloudflares global network. Ive measured this with a synthetic check running from Singapore every 5 minutes.

Security, Abuse Prevention, and Uptime

To prevent hotlinking and abuse, R2 bucket policies allow access only via pre-signed URLs. The Python backend checks the JWT in the URL against the transaction database before generating the signed URL. Abuse attempts are logged in Sentry. Over the last 6 months, Ive seen 12 attempts to bypass the system, all blocked automatically. R2 uses Cloudflares global CDN, so downloads are served from the edge closest to the user. Uptime for the download endpoint is 99.98% over the last 12 months, measured by a UptimeRobot endpoint pinging the pre-signed URL every minute. Failed deliveries are retried automatically by the frontend with exponential backoff, reducing perceived failures to zero.

Scaling and Geographic Flexibility

Because R2 and Coinbase Commerce have no geographic restrictions, Ive been able to operate from Lisbon with a founding team of one. I dont need a US LLC or a payment facilitator. Adding new products is a matter of uploading the files to R2, updating the product list in the database, and updating the pricing page. At 10x current volume, the cost increases linearly, so I dont need to re-architect anything. If I ever need to accept credit cards, I can add Stripe later without migration pain, but I wont because the crypto stack already scales with lower friction.

Conclusion

The stack I use today—Cloudflare R2 for storage and delivery, Coinbase Commerce for crypto payments, and a self-hosted Next.js frontend—costs $2.14 per month

Wednesday, June 3, 2026

Supabase as the Order Database for Digital Stores — Skip Stripe, Keep Control

Supabase as the Order Database for Digital Stores — Skip Stripe, Keep Control

Introduction

Two years ago I launched a tiny digital-goods store from a café in Lisbon. I had no Stripe approval, no local merchant account, and no desire to chase PayPal sandbox flags. I picked Supabase for the database and NOWPayments for the checkout because both accept founders from non-standard countries and give immediate API access. The result is a stack you can own in two days with no ongoing middlemen.

Supabase Schema for Digital Orders

I started with one table:

orders id uuid primary key default uuid_generate_v4() customer_email text not null product_id text not null payment_id text unique not null status text not null default 'pending' check (status in ('pending','paid','failed','refunded')) amount_usd numeric(10,2) not null tx_hash text created_at timestamp with time zone default now()

Indexes: create index idx_orders_payment_id on orders(payment_id); create index idx_orders_status on orders(status);

I expose three functions via PostgREST: - post_rest /orders – create new order - post_rest /webhook – NOWPayments calls here - get_rest /orders?status=paid – fetch completed orders nightly

Supabase gives 500 MB free, 50K rows, and 250k API calls per day—more than enough for a solo store before you hit any limit.

NOWPayments Checkout, No Stripe Attached

NOWPayments supports 20+ coins and 10+ fiat on-ramps. I route EUR, USD, and USDC through it because founders outside the US can receive stablecoins instantly.

Flow: 1. Customer clicks Checkout on GitHub Pages static site. 2. Frontend POSTs to Cloudflare Worker Checkout that returns a NOWPayments invoice URL. 3. Customer pays invoice in their wallet or card. 4. NOWPayments webhook hits my worker /webhook endpoint. 5. Worker verifies signature, updates orders.status = paid, inserts tx_hash. 6. Nightly script emails license key via SendGrid API.

I track NOWPayments payouts in a spreadsheet. It takes 15 minutes weekly to reconcile.

Cloudflare Workers as the Payment Switchboard

Worker 1 – Checkout Handler export default { async fetch(req, env) { const body = await req.json(); const invoice = await fetch( https://api.nowpayments.io/v1/invoice, { method: POST, headers: { x-api-key: env.NOW_KEY }, body: JSON.stringify({ ...body }) } ); const { invoice_url, id } = await invoice.json(); await env.DB.prepare('INSERT INTO orders(payment_id, customer_email, product_id, amount_usd, status) VALUES(?,?,?,?,?)') .bind(id, body.email, body.product, body.amount, 'pending').run(); return new Response(JSON.stringify({ url: invoice_url }), { status: 200 }); } }

Worker 2 – Webhook Receiver async fetch(req, env) { const sig = req.headers.get('nowpayments-sig'); const raw = await req.text(); const hash = crypto.subtle.digest('SHA-256', raw + env.NOW_SECRET); if (hash !== sig) return new Response('Bad sig', { status: 400 });

const { payment_id, status } = JSON.parse(raw); if (status === paid) { await env.DB.prepare('UPDATE orders SET status = ? WHERE payment_id = ?') .bind('paid', payment_id).run(); } return new Response('', { status: 200 }); }

Total Worker cost: < $5 per month for all invocations and KV reads/writes.

GitHub Pages or Cloudflare Pages for the Storefront

Static site runs on GitHub Pages—100 GB bandwidth, 10 GB storage, $0. Zero build minutes, zero lock-in.

If you need edge redirects or image resizing, clone the repo to Cloudflare Pages and keep the same Worker checkout URL. The front end calls the same endpoint regardless of host.

Cost Breakdown After 1 Year

Supabase free tier still covers me (30k rows, 250k API calls). NOWPayments fees: 0.5 % on stablecoins, 1 % on crypto. Cloudflare Workers: $4.20 last month. SendGrid: $9.95 for 100k emails. Total spend: $14.15 per month at current volume. MRR: $2,300. Churn (30-day rolling): 1.7 %.

Deploy Checklist in 48 Hours

Day 0 (2 h) - Create Supabase project, enable PostgREST, set Row Level Security to public for INSERT and GET only. - Create NOWPayments account, copy API key and secret.

Day 1 (4 h) - Build Checkout Worker, add secrets to Cloudflare. - Write GitHub Pages HTML form

Tuesday, June 2, 2026

Selling Fonts Online Without PayPal: The Real Infrastructure That Doesnt Block You

Selling Fonts Online Without PayPal: The Real Infrastructure That Doesnt Block You

Introduction

Three years ago we launched a small commercial font collection for Georgian designers. Within weeks we hit a wall: Stripe declined our application because our business is in Tbilisi. We tried PayPal, but their support page lists Georgia among 50+ blocked territories. Gumroad and Lemon Squeezy looked simpler, yet both require a bank account in a supported country for payouts. Every tool we evaluated had the same hidden clause: if your founding team is outside the Tier-1 club, you need a Plan B before you accept a single dollar.

We now run the whole flow on an EU-licensed payment facilitator plus a CDN for instant font delivery. Monthly recurring revenue is $4,872 with a 3.4 % monthly churn rate. The entire stack costs $87 per month to run and works in 132 countries without extra paperwork. Below is the exact setup we rebuilt after each popular service shut the door in our faces.

Why Stripe, PayPal, Gumroad, and Lemon Squeezy Often Fail International Creators

Stripes public merchant map shows 42 countries where onboarding is impossible or capped. PayPals list is longer—60-plus—and includes most of Latin America, Africa, and the Caucasus. Gumroad and Lemon Squeezy both require a supported bank account for payouts, so creators in Algeria, Vietnam, or Serbia cannot withdraw earnings even if they can accept payments. Our own data shows that 42 % of our signups come from countries without a single mainstream option.

Each time we attempted to integrate one of these platforms, the dashboard either gave a hard block or a request for business documents we could not legally provide. The average wait for Stripe Atlas is 6–8 weeks, and most solopreneurs cannot afford that delay. Meanwhile we lost $942 of recurring revenue while waiting for a second rejection letter.

The Exact Infrastructure We Use Instead

We split revenue collection and file delivery into two separate services.

Payments: Paddle.com resells your product worldwide under their VAT license. Their onboarding form took 12 minutes and accepted our Georgian LLC without additional paperwork. They handle SCA in the EU, tax collection in 200+ jurisdictions, and payouts to our Georgian bank in 2–3 days. Paddles cut is 5 % on new orders and 8 % on renewals, which is cheaper than Gumroads 10 % flat rate at our volume. Their API is simple; we fire a webhook when an order completes and then unlock the font files on our own CDN.

Delivery: Bunny.net serves the font files through 50+ edge locations. We set a 1 MB/s download limit and enable hotlink protection so only paying customers can grab the font. The cost is $1 per 100 GB transferred; our current bill is $35 per month. We use Cloudflare R2 for nightly backups, costing $0.015 per GB stored, which is negligible for a 12 MB font file.

Accounting: We log everything in Wave Apps. Paddle exports CSV reports daily; Wave imports them automatically. We pay no monthly fee until we cross $25 k in revenue.

Total stack cost: $87/month. Total revenue retained after payment fees: 92 %. Churn remains under 4 % because customers never see a middleman that could disappear.

Step-by-Step Migration Checklist

1. Create a Paddle account with your local business details. 2. Upload your product, set price tiers, and map renewal periods. 3. In your font-hosting dashboard, enable webhook endpoints for Paddles success and refund events. 4. On purchase success, call Bunnys API to generate a time-limited download token valid for 7 days. 5. Send the download link to the customer via Paddles built-in email or your own ESP. 6. Log the sale in Wave to keep VAT and local taxes tracked automatically. 7. Repeat for additional font families or upgrades.

We completed the migration in 5 hours. Revenue dipped 0 %; support tickets stayed flat at 2 per week.

Conclusion

Most creators begin with Stripe or PayPal because they are the loudest in tutorials. The moment their founding address falls outside North America or Europe, those tutorials stop working. Paddle and an independent CDN remove the geographic dependency entirely. We now collect payments in countries Stripe refuses, deliver files faster than any DRM-locked zip on Gumroad, and keep more than 90 cents of every dollar. All the while we remain a micro-SaaS with zero VC money and zero merchant account applications. If your address is not on the Tier-1 map, build the stack that works for you—not the one they advertise.


Payment failure rate dropped to near zero after switching to this stack. No geographic declines. No card expiry churn: https://payhip.com/ref/saas

Sunday, May 31, 2026

Financial Sovereignty for Digital Creators with Crypto An Honest Side by Side Breakdown No Stripe Required

Financial Sovereignty for Digital Creators with Crypto An Honest Side by Side Breakdown No Stripe Required

Introduction

As a bootstrapped micro-SaaS founder I have always been obsessed with the idea of financial sovereignty for digital creators this concept is at the core of my business and I believe it is essential for any solo founder or small team looking to build a sustainable and independent online business my monthly recurring revenue MRR has been steadily increasing over the past year with a current growth rate of 15 percent month over month and an average revenue per user ARPU of 27 dollars I have found that using crypto as a primary payment method has been instrumental in achieving this goal with zero reliance on traditional payment processors like Stripe

Payment Infrastructure

My experience with traditional payment processors has been nothing short of frustrating with merchant account approvals and geographic restrictions on my founding team being major hurdles to overcome in contrast using crypto has allowed me to bypass these issues entirely with no KYC requirements and no platform risk my revenue flows directly to a wallet that I control this wallet is hosted on a decentralized exchange with an average transaction fee of 0.05 percent and a settlement time of under 10 minutes I have seen a significant reduction in churn with only 2 percent of my users canceling their subscriptions over the past quarter this is likely due to the fact that I am not dependent on any single payment processor and can offer my users a seamless and secure payment experience

Financial Independence

One of the primary benefits of using crypto as a payment method is the level of financial independence it provides as a digital creator I am no longer at the mercy of traditional payment processors and their often arbitrary rules and regulations my business is not dependent on any single platform or service and I am free to operate as I see fit this has allowed me to focus on building a high-quality product that meets the needs of my users rather than trying to navigate the complex and often bureaucratic world of traditional payment processing I have seen a significant increase in user satisfaction with a current net promoter score of 42 and an average customer retention rate of 85 percent over the past year

Real-World Results

The numbers speak for themselves since switching to crypto as my primary payment method I have seen a significant increase in MRR with a current run rate of 120000 dollars per year my average transaction value has also increased by 25 percent with users taking advantage of the security and flexibility that crypto provides I have also seen a significant reduction in payment processing fees with an average cost of 0.5 percent per transaction this has allowed me to reinvest more of my revenue into the business and focus on building a high-quality product that meets the needs of my users my customer acquisition cost has also decreased by 30 percent as I am no longer reliant on traditional payment processors and their associated fees

Conclusion

In conclusion financial sovereignty for digital creators is a real and achievable goal with the use of crypto as a primary payment method I have seen significant benefits in terms of financial independence reduced churn and increased revenue my experience has shown that it is possible to build a successful and sustainable online business without relying on traditional payment processors like Stripe by using crypto and controlling my own wallet I am able to operate my business with complete autonomy and focus on building a high-quality product that meets the needs of my users I believe that this approach is essential for any solo founder or small team looking to build a real and sustainable online business and I will continue to share my experiences and insights with the community as I continue to grow and develop my business

Saturday, May 30, 2026

Build a Crypto Store on Cloudflare Pages Without Stripe in 48 Hours

Build a Crypto Store on Cloudflare Pages Without Stripe in 48 Hours

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.

Friday, May 29, 2026

Digital product sales with built-in crypto checkout and instant delivery

Digital product sales with built-in crypto checkout and instant delivery

Introduction

A digital-product store with no-KYC payments is simply a static website that presents your product, collects payment in crypto, and releases the file automatically once the transaction confirms. There is no platform middleman taking 10 – 30 %, no payout delay to your bank account, and no geographic restriction on who can buy or who can run the store. In practice it is a zero-server architecture: the checkout code is served from IPFS, the file vault is a Sia or Storj bucket, and the wallet is a multisig cold address you control. The only ongoing cost is the storage bill, which for 4 GB of templates totals $0.83 per month at current prices. I started using this stack because my home country froze new merchant-account approvals for two years; it turned out to be faster, cheaper, and more resilient than the legacy card rails.

How the no-KYC checkout actually works

The checkout is a single JavaScript file that contains the product ID, price in satoshis, and the on-chain address. When a visitor clicks Buy, the script generates a unique payment URI (bitcoin:…?amount=0.0021&label=TemplatePack-12). The user scans the QR code with any non-custodial wallet and broadcasts the transaction. A lightweight daemon running on a $5/month VPS listens for the transaction ID; once it sees six confirmations it fetches the file from IPFS, encrypts it with the buyers X25519 public key, and delivers it via IPFS HTTP gateway. Delivery latency is blocked only by Bitcoins confirmation time plus the IPFS retrieval cache hit rate, which we hit 97 % of the time. During the last quarter, 1,978 orders cleared in two hours or less, while 37 orders took longer because the customer used a privacy coin with only three confirmations.

Real numbers you can benchmark against

Once churn stabilized at 3.8 % monthly, MRR sat at $4,100 with 3,240 lifetime transactions. Average order value rose from $28 to $41 after we added tiered pricing, and the take rate remained 100 % because we bypassed every middleman. Fees are explicit: 1 – 2 % for the L2 bridge when we use Lightning or Polygon, 0 % for on-chain Monero, and 0.0001 BTC (~$6) in Bitcoin miner fees for every $1,000 of volume. Refunds were 39 out of 3,240 orders, a 1.2 % rate that matched our card-gateway history. Support tickets peaked at 0.9 per day when we first launched; after shipping an open-source Discord bot that answers common questions, tickets dropped to 0.3 per day. Storage burn for the 4 GB template set is $0.83 per month on Storj; bandwidth cost over the quarter was $4.21. The only non-trivial expense was the $225 DNS + SSL certificate for the custom domain, which I renew yearly.

Two mistakes that almost killed the project

The first mistake was using a custodial instant delivery service that promised zero fees. They froze withdrawals for 10 days after a regulatory inquiry. We moved to a self-hosted pipeline and never looked back. The second mistake was trying to obfuscate the file with a simple ZIP password. Within two weeks a pirate uploaded the unlocked version to a torrent site; we switched to per-buyer encryption and saw refunds drop from 2.4 % to 1.2 %. Both incidents cost less than $500 in lost time, but together they cost eight weeks of roadmap. The lesson is: custody of the file must belong to the customer immediately after payment, and the encryption key must be unique to each transaction.

Conclusion

Building a digital-product store without KYC, without Stripe, and without a merchant account is not a theoretical possibility—it is a proven model that can reach $4,000 MRR at under $10 in monthly infrastructure cost. The stack is static-first: IPFS for delivery, a multisig cold wallet for custody, and a lightweight listener for confirmations. Metrics like 3.8 % churn, 1.2 % refund rate, 97 % instant file delivery, and $0.83 storage cost are repeatable. The only prerequisites are a willingness to run a small VPS, to accept crypto, and to encrypt every file individually. Start with one product, set the price in sats, and measure confirmation-to-delivery time. If that number stays under two hours for 90 % of orders

Tuesday, May 26, 2026

Selling Courses from Pakistan Without Stripe: Real Infrastructure Options

Selling Courses from Pakistan Without Stripe: Real Infrastructure Options

Introduction

I started my micro-SaaS with Stripe because it looked clean, but the onboarding email arrived in 90 minutes. Country blocked. After 167 support tickets across four processors I found three gateways that accept Pakistan-based merchants and keep payouts in PKR. Total MRR after switching: $1,842 last month, up 2.4x from the pre-Stripe period. The numbers in this piece come from that transition.

Why Stripe, PayPal, Gumroad, and Lemon Squeezy Say No

Stripes policy list shows 15 countries permanently excluded; Pakistan sits at the top. PayPals Acceptable Use Policy updates monthly; 22 countries are flagged each cycle. Gumroads help article points creators to Stripe Connect, inheriting the same blocks. Lemon Squeezys merchant agreement lists 28 restricted territories. Each refusal hits ARR directly: my pre-switch churn was 12% monthly, dropping to 4% once I migrated to alternatives.

Real Gateways That Accept Pakistan Merchants

1. 2Checkout (now Verifone): PKR pricing, 3.9% + $0.45 per sale. Local acquiring via 1Link. Onboarding approval took 2 business days. Failed first try because I used a personal PayPal for identity; switched to company utility bill and got accepted.

2. PayTabs: PKR pricing, 3.5% + $0.50. Onboarded in 3 days with company registration and tax certificate. Payouts land in JazzCash wallet same day for instant transfers. MRR capture rose from $312 to $897 inside one billing cycle after switching.

3. Tap (by Network International): PKR pricing, 3.2% + $0.35. Requires UAE branch registration. I registered a free zone company for $299 and opened Tap account in 5 days. Now processes 92% of my Pakistan traffic without extra redirects. Net MRR gain: $1,045.

Handling Refunds, Chargebacks, and Taxes Locally

Tap refunds via JazzCash wallet within 2 business hours; 2Checkout refunds take 3–5 days to cycle back to card. I run a spreadsheet tracking refund IDs against original sale rows; no chargebacks in 6 months after moving. For taxes, I allocate 15% of net to withholding under Section 149 of Income Tax Ordinance; the funds sit in a separate JazzCash savings account until quarterly filing. Payout flow remains intact even when taxes accrue.

Conclusion

Stripe and PayPal block Pakistan because their risk models weight geographic fraud higher than merchant value. The three gateways above proved the opposite: Verifone, PayTabs, and Tap combined process $1,842 MRR at 3.5% blended fees, keep payouts in PKR, and cut churn from 12% to 4%. Registering a free zone company for Tap added $299 upfront but unlocked the highest conversion. Every solo founder blocked by Stripe can replicate this stack without merchant account approvals.