If your product is a static site (no backend), you can still accept Stripe payments. The trick is Stripe Payment Links.
What Stripe Payment Links are
A URL like https://buy.stripe.com/cN2bJj... that opens Stripe Checkout with a pre-configured product, price, and success/cancel URLs. You generate them in the Stripe dashboard, paste them into your HTML, done.
Step 1: Create a product
Stripe dashboard → Products → Add product. Set name, price, recurring (yes/no).
Step 2: Generate a Payment Link
Click product → "Create payment link" → configure:
- Quantity adjustment? Y/N
- Custom fields? (Email, phone, custom Q)
- Success URL: https://yourdomain.com/thank-you.html
Click "Create". Copy the URL.
Step 3: Use it
<a href="https://buy.stripe.com/cN2bJj...">Buy now — $19</a>
That's it. Click → opens Stripe-hosted checkout → on success → redirected to your thank-you page.
What you give up (vs full integration)
- Dynamic pricing (each product needs its own Link)
- Pre-filled email from your auth (no client-side context)
- One-step UX (it's a redirect, not embedded)
When Payment Links are enough
- Single-product sales
- Donations
- Boost tiers / fixed-price subscriptions
- E-books, courses, templates
- Newsletter paid tiers
We use Stripe Payment Links for our Boost tiers on Nexora — works perfectly, zero backend code.
When you need a backend (Edge Function)
- Dynamic cart with variable line items
- Discount codes from your own DB
- Buyer's address required for international tax
- Subscription with custom seat counts
For those, a Supabase Edge Function or Vercel API route is 30 lines of code.
Need this built for you?
Hire a vetted Nexora expert. Escrow-protected. Fixed price. From $65.
Browse automation services →