WP Full Pay

What WP Full Pay is

WP Full Pay is a Stripe payment plugin for WordPress. It is a form tool with one job: you create payment forms in the WordPress admin, connect your Stripe account, and place the forms on your pages and posts. The site's headline says it is loved "by businesses and not-for-profits", and the audience it names is exactly that: small businesses and nonprofits that already run WordPress and want to take payments, subscriptions and donations without building a shopping cart. The home page puts it plainly: "accept one-time and recurring payments and donations on your WordPress site without setting up a shopping cart. No code required." The footer carries a 2026 copyright for paymentsplugin.com and the line "Powered by VertiStudio".

The company's promise is speed and no code: "Start accepting Stripe payments in less than 30 minutes. No coding skills required." It adds that the plugin makes it easy "whether you process" 100 or 100,000 a week, with the currency shown as either a dollar or a euro sign. The closing banner describes it as a Stripe plugin that "allows you to add various Stripe products, such as one-off and recurring payment forms to your WordPress pages or posts."

What you build and how

The workflow is four steps, and the home page numbers them. Install the WP Full Pay plugin in your WordPress site. Connect your Stripe account. Create a payment form for your business model. Add the form to a WordPress page and start accepting Stripe payments. You choose the type of payment form from your WordPress admin panel, customize it, and start "with a few clicks." The home page calls the result "ready-to-customize payment forms," so you start from a form type rather than a blank canvas.

The form types, each with its own feature page on the site, are these.

• One-off payment forms for physical or digital goods and services. The home page lists software, tickets, info products and physical goods as examples.
• Subscription forms for recurring payments, which the site pitches as collecting subscription payments for all kinds of services.
• Donation forms to accept monetary support for a nonprofit or organization. The menu describes them as forms "for fundraising or digital projects."
• Save card forms that securely store a customer's card details so you can charge later.
• Buy now buttons, which let you create multiple checkout buttons and add them to a pricing table.

Two more items sit alongside the forms. Digital wallets are listed so customers can "pay easily on their mobile devices", and custom design lets you adjust the look of the payment forms to match your website.

For access control, the company sells a separate WP Full Members add-on. The site's menu describes the Members Only Website feature as a way to "make WordPress content private and sell memberships," and the home page says that bundling WP Full Pay with WP Full Members produces "members only, paid access, premium content" on your WordPress site. Put together, a subscription form takes the recurring payment and the add-on decides which pages a paying member can read. For the forms category this makes WP Full Pay a specialist: it builds payment forms and a paywall rather than surveys or contact forms. For the WordPress plugin category it is a payments plugin that can double as a basic membership layer.

The company's own blog gives a fuller picture of the form layer than the home page does. Citing the current documentation, a post on the blog says WP Full Pay lists one-time, donation, subscription and save-card forms, "with supported settings varying by form type," along with shared features such as custom fields, email notifications and redirects. It puts the business-field limit at up to 10 custom fields per form, plus billing, shipping, email, redirect and notification options. That is enough to collect, say, a ticket holder's name and dietary choice, or a shipping address for a physical product, on the same form as the card.

The same post explains placement. You can choose inline fields on the WordPress page, or a button that redirects the customer to Stripe-hosted Checkout, and the layout guide separates those two as inline forms and Checkout forms. Because the form sits on an ordinary WordPress page, you can "surround the form with the page's own product copy, media, FAQs, and navigation," and then "share the WordPress page URL or place the form around the site." The post describes the plugin as "the stronger fit when the page content, form placement, WordPress data, and post-payment path need to work together."

From the paying customer's side, the experience depends on the layout you pick. With an inline form they pay on your site's page, next to whatever product description, images and questions you put around it. With a Checkout form they click a button and finish on a Stripe-hosted page. Either way the money lands in the Stripe account you connected in step two, so payouts, refunds and disputes are handled in Stripe.

The blog doubles as a Stripe manual for site owners. Recent posts cover what Stripe refunds really cost and how to handle them, when Stripe actually pays you out (payout schedules, holds and instant payouts), and how to migrate recurring subscribers from PayPal to Stripe without losing revenue. Another post covers selling products on WordPress without WooCommerce when a focused payment form is enough, which is the plugin's core use case.

Plans, pricing and support

The site offers two entry points, "Buy License" and "Get Free Version", so there is a free version as well as a paid license, and one reviewer mentions buying "the Pro version". The site links a Pricing page, but the home page and blog state no prices or plan limits.

The navigation lists Support, Documentation, FAQ, Blog, About Us and Contact. Reviews on the home page, from users who go by lostmypassword, milanbulatovic and sorinexu, give the plugin five stars. One calls it "a great plugin for managing recurring payments in WordPress" and praises the "exceptionally fast, friendly and helpful support" that made the decision to buy the Pro version easy. Another says the plugin is easy to work with and will be complete "once they update more payment methods". The third says they "managed to implement it successfully very quickly". These are three users' comments, not a measured satisfaction figure.

Who it suits and who it does not

WP Full Pay suits a WordPress site owner who wants to sell one product, collect donations, charge a monthly fee or gate a few pages without installing a full e-commerce platform. A nonprofit that wants a donation form with Stripe behind it, a club that charges an annual subscription, or a seller of software, tickets, info products or physical goods matches the plugin's own example list. Inline forms keep the customer on a page that carries your own branding and explanation, and the 10 custom fields cover the extra details most small sellers need.

The limits are structural. It is a Stripe plugin, so it helps only if Stripe is your payment provider, and one reviewer asks for "more payment methods", so check the method list against your audience. It lives inside WordPress, so a landing page outside WordPress has no use for it. And it is built around its payment form types rather than a product catalog or cart, so a shop with dozens of products and a basket is better served by a full e-commerce plugin, with WP Full Pay reserved for the focused offers, donations and subscriptions it was designed for.