Stripe Payment Links are the fastest way to accept a card payment without writing code. They're also the source of more "is this really all Stripe does?" questions than any other Stripe feature. The Dashboard's Payment Link builder ships with deliberate constraints — single line items, fixed customization, a $10,000 cap on pay-what-you-want, no real customer portal, no email cadence beyond a basic reminder. For a SaaS selling a $29/month plan, none of this matters. For an agency invoicing variable amounts, a hosting reseller billing 50 clients a month, or a coach selling a 4-session package, the limits show up in the first week.
This post is the field guide. We list the nine most common Stripe Payment Link limitations we hear from customers who switched to PayRequest, what each one actually means in practice, and the workarounds — including which ones are worth the engineering time and which ones are easier to outsource. It pairs with our free payment-link guide, the product-free payment link post, and the customer-portal limitations breakdown.
Key Takeaways
- Stripe Payment Links default to fixed-price products. The product-free workflow ("Customers choose what to pay") caps at $10K and locks you to a single line item
- Customization is intentionally narrow — 20 preset fonts, 3 border-radius options, your logo and colors. No template control, no per-customer branding
- No real customer portal on free Payment Links. Your customers can't log in to see invoice history; that's a separate Stripe Billing feature
- Reminders are basic — Stripe sends a single email reminder for unpaid one-off invoices. No SMS, no WhatsApp, no escalation cadence, no dunning across multiple links
- Multi-provider is impossible. A Stripe link only accepts what Stripe processes — no PayPal balance, no Wero, no Bizum on the same checkout
- Pre-authorization holds beyond 7 days require Extended Authorization (Visa/Mastercard/Amex/Discover only, brand-restricted)
- No native file delivery for digital products. Stripe redirects to a thank-you page; you build the download flow elsewhere
- PayRequest is built on top of Stripe (and Mollie and PayPal) and fills these gaps without removing Stripe — your money still settles in Stripe
Why Stripe Payment Links Have So Many Limits
Stripe built Payment Links as a 5-minute "accept card payments without code" entry point — not as a billing platform. Every limit you'll hit traces back to that decision. The product was designed for a SaaS founder who needs to sell access to a beta, an indie hacker collecting course payments, or a Shopify store offering a one-off SKU. For *those* users, the simplicity is the feature.
The mismatch shows up the moment your business model needs more than a checkout page — recurring billing with custom amounts, deposits, dunning, customer self-service, multi-currency settlement, file delivery, taxes that aren't sales-tax-compatible. Stripe addresses some of these with separate products (Stripe Billing, Stripe Tax, Stripe Connect, Stripe Invoicing), each with its own integration and API surface. Stitching them together is the engineering work most small teams don't want to do.
The 9 Most Common Stripe Payment Link Limitations
We catalogued the questions PayRequest customers ask most often before switching. These are them, in order of how much pain each one causes.
Stripe Payment Links are product-centric. Every link points to either a Product object (with a fixed price) or a "Customers choose what to pay" link (with a $10,000 USD default ceiling). Variable-amount invoicing — agency retainers, custom quotes, deposits — forces you to either create a fake product per invoice (cluttering your dashboard) or live within the $10K cap.
Workaround: The Stripe API supports inline `price_data`, which generates a hidden product on the fly. Effective for technical teams. For non-developers, a hosted platform like PayRequest skips the product object entirely.
Stripe gives you a logo, brand colors, and a choice of 20 preset fonts and 3 border-radius options on the checkout page. That's the entire customization surface. You cannot change layout, add custom HTML/CSS, embed video, change the success page deeply, or remove "Powered by Stripe" on the standard plan.
Workaround: Stripe Checkout (the older, more flexible API) and Stripe Elements (full custom UI) both give more control — but they require building the front-end yourself. For a hosted-but-branded checkout, PayRequest's Smart Payment Links sit between the two: more design control than Stripe's defaults without the dev work.
Stripe's Customer Portal is a separate feature tied to Stripe Billing, not to standard Payment Links. Customers paying via a Payment Link have no way to log in later, see their invoice history, download receipts, or update their payment method without you sending them a brand-new link or portal session URL. For B2B businesses where the customer expects "let me check my invoices anytime," this is a dealbreaker.
We covered the full breakdown in Stripe Customer Portal Limitations. Short version: the Stripe portal supports subscription self-service but is not a complete billing portal.
Workaround: PayRequest ships a customer portal with every link — invoices, history, downloads, deposits, file delivery — included in the €20/mo plan.
Stripe sends one email reminder for unpaid one-off invoices, configurable in the Billing Settings. There is no SMS reminder, no WhatsApp reminder, no escalating cadence (2-day, 5-day, 14-day), no per-customer customization, and no resend if the link itself is unpaid (versus an invoice). For B2B billing where collections is the difference between profitability and a cash-flow squeeze, this is sparse.
Workaround: Build automation in Zapier/Make, or use a dunning platform (Churn Buster, Stunning, FlyCode). PayRequest's dunning system bundles email + SMS + WhatsApp reminders into the same plan, with a configurable cadence.
A Stripe Payment Link can only accept payment methods Stripe processes. That includes cards, Apple Pay, Google Pay, iDEAL, Bancontact, SEPA, Klarna, and others — but it cannot include the customer's PayPal balance, Wero, or anything routed through Mollie or another acquirer. So a Dutch agency wanting both iDEAL (best on Mollie) and PayPal balance pay (best on PayPal) on one checkout has to either pick one provider or send two separate links.
Workaround: PayRequest aggregates Stripe + Mollie + PayPal under one link. The customer sees all available methods on one checkout; the funds settle in the matching provider account. See Stripe vs Mollie vs PayPal.
Standard Stripe card authorizations expire after 7 days. Stripe's Extended Authorization feature stretches this to 30 days, but only on Visa, Mastercard, Amex, and Discover — and not all merchant categories qualify. For rentals, event prepayments, and security deposits where the hold needs to span weeks, this is restrictive.
Workaround: Switch to Mollie for pre-authorization holds (1–28 days, broader card brand support) — see Collect Rental Deposits Without Stripe API. PayRequest routes deposit links through Mollie automatically.
A Stripe Payment Link can sell a digital product, but it doesn't deliver the file. The customer pays, lands on a thank-you page, and you're responsible for emailing the download link, hosting the file, expiring the link, and preventing leaks. Stripe Tax handles VAT on the sale; Stripe doesn't handle the bytes.
Workaround: Use a separate digital-delivery service (SendOwl, Lemon Squeezy on the SaaS side) or build a webhook → email pipeline. PayRequest's digital products feature handles delivery, expiring URLs, and download tracking inline.
Stripe subscriptions need a Product → Price → Subscription chain with a fixed amount. You can't easily say "bill this customer €4,200 in May, €3,800 in June, €5,100 in July, all on the same recurring rail." Variable retainers force you to either create a new Price for every invoice (cluttered) or charge as one-off payment links (no auto-charge, no saved card, no automatic renewals).
Workaround: Stripe supports custom prices via the API and metered/usage-based billing for some scenarios. PayRequest treats every invoice as variable from the start — same customer, different amount each cycle, auto-charge on the saved payment method.
If a customer wants a refund, the Stripe Customer Portal doesn't let them request one. They email you, you log into Stripe, find the charge, click "Refund." For high-volume B2C businesses (course platforms, memberships, subscriptions), this is fine; the volume is low. For B2B service businesses with disputes over deliverables, the lack of a structured request flow turns email into a chaotic queue.
Workaround: Build a custom request form, or use a billing platform with refund-request workflows. PayRequest's customer portal includes a refund-request inbox attached to each invoice.
A Quick Decision Matrix: When Each Limit Actually Bites
Not every limit matters to every business. Use this matrix to spot which ones will hit you first:
| Business type | Limits that bite first |
|---|---|
| SaaS (single fixed-price plan) | None — Stripe Payment Links are excellent |
| Agency / consulting | #1 (variable amounts), #4 (reminders), #8 (variable retainers) |
| Hosting / WHMCS replacement | #1, #3 (portal), #4, #8, #9 |
| E-commerce / digital products | #2 (customization), #7 (file delivery) |
| Rentals / events | #6 (hold duration), #1 (deposit amounts) |
| Coaching / course creator | #3 (portal), #7 (delivery), #5 (PayPal alongside cards) |
| B2B service business | #1, #3, #4, #5, #8, #9 — basically all of them |
The pattern is consistent: the more your billing diverges from "fixed-price product, one-off card payment, US/UK customer," the faster Stripe's Payment Links alone start needing scaffolding around them.
How PayRequest Sits On Top of Stripe (Without Replacing It)
A common misconception: PayRequest is *not* a Stripe alternative for the payment processing itself. The funds still settle in your Stripe account. The card is still tokenized by Stripe. The PCI compliance, the fraud detection, the chargeback flow — all Stripe.
What PayRequest adds is the billing platform around Stripe — the layer Stripe doesn't ship by default:
- Variable-amount invoicing without products
- A customer portal for invoice history, downloads, deposits, file delivery, refund requests
- Multi-channel dunning (email + SMS + WhatsApp, configurable cadence)
- Multi-provider checkout (Stripe + Mollie + PayPal on one link)
- Native deposits with pre-auth holds (routed through Mollie when needed)
- Bank reconciliation to match incoming SEPA/ACH transfers to invoices
- File delivery for digital products with expiring URLs
The result: you keep Stripe for what it's great at (processing), and stop building the billing layer yourself. The math works at €20/month flat for the platform; Stripe's transaction fees are unchanged.
When Stripe Alone Is Still the Right Answer
To be fair: Stripe Payment Links by themselves are the right answer in a real set of cases. If you're a SaaS selling a single fixed plan, an indie maker with a one-off course, a small e-commerce store with three products, or a content creator collecting tips, you do not need PayRequest. The setup is faster on Stripe alone, the cost is lower (no monthly subscription), and none of the limits in this post will hit you.
The crossover point is roughly: once you're sending more than 5 payment links a week, billing variable amounts, or handling B2B clients who expect a portal, the build-vs-buy math flips toward a hosted platform. That's where PayRequest pays back.
Frequently Asked Questions
The questions below come from real PayRequest support tickets and "People Also Ask" data on Stripe Payment Link queries.
Pick the Layer You Need
Stripe Payment Links solve the smallest, fastest version of "accept a payment online." They are excellent at that. They also stop where most billing software starts — variable amounts, customer portals, dunning, multi-provider, deposits, file delivery. None of these are "broken" in Stripe; they're just not in the Payment Links product, and stitching them together is engineering work.
If you're already feeling 3+ of the limits in this post, try PayRequest free. It connects to Stripe in 3 minutes via OAuth, your money still settles in Stripe, and the billing layer above is finally there. For the specific limits, see our product-free payment-link guide, the customer-portal post, and the extended-auth deposit guide.