Stripe Payment Links vs Embedded WordPress Forms: Which Should You Use?

If you’re looking to process payments on your WordPress website without the need to set up a full store or manage inventory, there are two straightforward methods you can use. These options allow you to charge a card for services, deposits, donations, or singular items. You can either direct customers to a hosted checkout page or keep them on your site with an integrated form.

The first option is Stripe Payment Links, which operates entirely within your Stripe account. The second is an embedded form plugin like WPFullPay (part of the ThemeIsle family, just like this blog), allowing the entire checkout process to occur in your site’s design.

In this guide, we will examine both options regarding setup, branding, features, and actual costs, while also explaining the scenarios in which each option excels. Let’s jump straight into the brief overview.

The quick answer: which option suits your needs?

If that table satisfactorily answered your question, the remainder of this guide will elaborate on the details and trade-offs behind each choice.

Understanding Stripe Payment Links

Payment Links is a feature located within your Stripe Dashboard, and it’s not a WordPress plugin. You create a product with an associated price, and Stripe generates a fully hosted checkout page with a shareable URL, requiring no additional coding. ^[1]

You can use this URL anywhere a link can be pasted: on a button on your WordPress page, in your email signature, a WhatsApp message, or even a QR code on an invoice. This link can accommodate unlimited customers, and Stripe manages everything: the page, the card information fields, Apple Pay and Google Pay options, and even the receipt email if you opt for it.

Costs are straightforward: you simply pay Stripe’s standard processing fee (2.9% + 30¢ for domestic US cards, higher for international transactions), with no monthly subscription, per-link fees, or plugins taking their cut. ^[2]

The trade-off involves control; your customer leaves your site to complete payment. While you can brand the Stripe page with your logo and colours and include a buy button on your site, that button still requires redirection. For many situations, this is perfectly acceptable. However, for certain circumstances, this transfer could be a crucial aspect of the decision-making process, which is why the next section is invaluable.

What is an embedded WordPress form?

An embedded form plugin allows the entire checkout to be placed directly on your WordPress page, complete with your header, footer, fonts, and the payment form embedded within your content. The customer remains on your website, and their card information transmits directly to Stripe without involving your server.

This guide focuses on WPFullPay, which offers a free tier that includes one-off payments, subscriptions, goal-oriented donation forms, and the ability to save card details, while incurring a 5% application fee per transaction until a license is purchased. ^[3] Another well-known free alternative is WP Simple Pay Lite, which carries a 3% fee with more limited features in its free version. ^[5]

Using a plugin additionally grants you unique advantages that a link can’t provide: complete payment records within wp-admin, customizable notification emails, and forms that you can style, clone, and repurpose across various pages. If payments are a regular aspect of your site rather than sporadic events, these features quickly prove valuable.

Setup and Maintenance: Quick vs. In-Depth

Payment Links: If you already possess a Stripe account, you could be processing payments in under ten minutes. Create a product, assign a price, copy the link, and paste it into a WordPress button block. There are no updates to make or plugins at risk of breaking with a WordPress release, and no settings to second-guess.

Embedded form: Expect to allocate an afternoon to set up the first form. You’ll need to install the plugin, link Stripe using your API keys, create the form, embed it on a page, then conduct test payments in Stripe’s test mode followed by a real $1 transaction in live mode. While this is manageable, and guides like how to integrate Stripe with WordPress can simplify it, it’s a more involved project with components you will manage long-term.

PRO TIP: No matter which option you select, ensure to execute a real $1 transaction before sharing your form or link with others. A test run in live mode can uncover issues with webhooks and notifications that test mode does not reveal.

Branding and Checkout Experience

This aspect often has the most significant impact on customers. An embedded form feels seamless: the buyer remains within your environment from the initial contact through to the thank-you page. Payment Links, on the other hand, requires a small transition: as soon as money is involved, the URL shifts to a Stripe domain.

The impact of this transition depends on your customer demographic. Clients who are paying an invoice already possess a level of trust, and Stripe’s page is generally more trustworthy than that of many small businesses, which may cause the redirect to be perceived as professional rather than suspicious. However, individuals encountering a $29 product for the first time on your site may be more hesitant, and keeping them on your domain can reduce reasons for doubt.

Stripe allows for some branding: you can customise the hosted page with your logo, colours, and a custom domain on paid plans, and the page itself is designed to be polished and mobile-responsive. “Ugly checkout” is not a valid reason to avoid Payment Links; rather, “it’s not my checkout” is the honest concern.

Feature Comparison: What Each Option Offers

The main pattern to note: Payment Links effectively handles the transaction itself, including recurring payments and promotion strategies, but stops there. Everything surrounding the payment (donation campaigns, customer self-service, and your own record-keeping) is where a plugin demonstrates its value. The WPFullPay feature set offers even deeper capabilities, with a detailed WPFullPay review available on this blog for further exploration.

Actual Cost Comparison

Both methods incur Stripe’s standard processing rates; thus this part is equal. The difference arises from what is added on top. Payment Links has no additional fees, while a free embedded plugin incurs a 5% transaction fee for WPFullPay and a 3% fee for WP Simple Pay Lite.

At lower transaction volumes, these fees may be justified for the features provided: 5% of $100 in sales each month amounts to $5, which is still less than any subscription. However, as sales volume rises, acquiring a license (with WPFullPay Basic currently at €79.50 per year introductory pricing, renewing at €159) becomes the more economical choice. ^[4] The complete break-even analysis, including a worksheet for your specific figures, is contained in the companion guide on the real costs of Stripe on WordPress.

Receipts, Refunds, and Record-Keeping

Following the arrival of your initial payment, three administrative questions arise: Who sends the receipt? Stripe can automatically send one for both techniques, while a plugin can offer customizable notifications. Where do refunds get processed? All refunds occur via Stripe, regardless of which payment option initiated the transaction. And where should you check if a customer queries, “did my payment go through?” For Payment Links, you refer to the Stripe Dashboard. Conversely, with an embedded plugin, the payment records are readily accessible in wp-admin alongside everything else you oversee.

None of these factors stand alone as a reason to switch methods; however, the record-keeping question grows with increased transaction volumes. Searching a separate dashboard for a single monthly payment is easy, but cross-referencing fifty payments a week across two systems can lead to the birth of tedious bookkeeping processes.

Important Note: Neither option discussed here makes Stripe’s fees disappear. Anyone claiming “zero-fee payments” is simply passing on the costs, not eliminating them.

Which is Best for You?

• Opt for Payment Links if you process sporadic transactions, are already using your Stripe Dashboard, desire minimal maintenance, or need to accept payments from platforms your website doesn’t cover (emails, social media, print materials).
• Opt for an embedded form if payments are a constant feature of your site, if collecting donations or subscriptions is your goal, if you want to maintain payment records within WordPress, or if you feel your brand cannot afford a redirect page during checkouts.
• Utilise both if applicable: many websites incorporate an embedded donation form on their campaign page while keeping a payment link in their email signature for one-off invoices. The two options share the same Stripe account, ensuring no conflicts.

If your future plans involve a shopping cart, multiple products, or shipping, neither option will suffice; that’s when a complete e-commerce solution, like WooCommerce, becomes advantageous. Until then, aim to maintain a streamlined setup and a simpler checkout process than this guide.

Do you have a successful setup that works for your site? Please share it in the comments below.

Sources

1. [1] Stripe Payment Links: -code payment pages
2. [2] Stripe pricing: processing rates and fee structure
3. [3] WPFullPay on WordPress.org: free-tier features and application fee
4. [4] WPFullPay pricing: licensing options that eliminate the fee
5. [5] WP Simple Pay Lite vs Pro: the 3% free-tier fee

FREE GUIDE

4 Essential Steps to Speed Up Your WordPress Website

Follow the simple steps in our 4-part mini series and reduce your loading times by 50-80%.

Well done! You’ve reached the end of the article!