You do not need a full online store to sell one service, a few fixed-price offers, or a simple subscription from a WordPress site. In those cases, a focused sales page and a Stripe payment form may be enough.
The important word is payment. A lightweight form can collect customer details and complete a charge, but it does not automatically become a product catalog, shopping cart, inventory system, shipping tool, or fulfillment service.
This guide shows how to decide whether the lightweight approach fits, how to sell on WordPress without WooCommerce using WP Full Pay, and what you still need to handle after checkout. WP Full Pay is the Stripe payment plugin covered on this site.
Start with the transaction and the work around it. If buyers choose one clearly described offer, pay once, and receive the service or item through a process you already manage, a dedicated payment form can keep the setup pleasantly small.
| A lightweight form may fit when | Use a fuller commerce system when |
|---|
| You sell one offer or a small number of offers | You need a browsable catalog with many products and variants |
| Each page has one clear price or a short list of prices | Customers need a multi-item cart, bundles, or complex promotions |
| You can fulfill each purchase manually or through a separate workflow | You need automatic inventory, shipping, downloads, licenses, or order routing |
| You collect only the customer details needed for the transaction | You need advanced product options, quantity rules, or account-level order history |
| Your tax and receipt requirements fit the available Stripe and form settings | You need complex tax, invoicing, refund, or regional compliance workflows |
Good examples include a consulting session, workshop ticket, deposit, fixed-price service, small physical item with manual shipping, or a simple recurring service. The approach is less suitable when the operational work is already becoming a store.
💡 A useful test: If the payment succeeds, can your existing team or system reliably identify the buyer, deliver the offer, handle support, and reconcile the transaction? If not, checkout is only one part of the missing workflow.
What WP Full Pay handles, and what it does not
WP Full Pay is a standalone WordPress plugin that connects a site to Stripe. It is not a WooCommerce add-on and does not integrate with WooCommerce, although both plugins can run on the same site. The current compatibility guide confirms that boundary.
For a simple sale, you can create a one-time payment form for a physical product, digital product, or service. Depending on the form setup, the amount can be preset, selected from a short list, or entered by the customer. Subscription forms cover recurring offers, while donation and save-card forms serve different jobs.
You can show fields directly on the WordPress page with an inline layout or send the buyer to Stripe-hosted Checkout. The separate Stripe payment form guide explains the available form types in more detail.
- WP Full Pay can handle: payment-form configuration, eligible Stripe payment methods, customer fields, one-time or recurring charges, and the recorded transaction.
- You still handle: product-page copy, stock, shipping, file delivery, bookings, licenses, refunds, support, accounting, and any operational handoff not explicitly connected to the payment.
⚠️ Plan for fees: WordPress itself does not take a percentage of each sale. The free WP Full Pay version currently adds a 5% application fee per transaction, and Stripe processing fees still apply. A paid WP Full Pay license removes the plugin application fee. Verify the current terms on the official plugin listing before launch.
Prepare the offer and operations before building the form
A form is easier to configure when the commercial decisions are already settled. Write down the exact offer, price, currency, refund policy, and what happens after a successful payment.
- Offer: Give the product or service a clear name, scope, image, price, and delivery promise.
- Customer data: Collect only the contact, billing, shipping, or booking details needed to complete the sale.
- Tax: Decide whether the form needs no tax, Stripe Tax, or configured Stripe tax rates. Confirm the correct treatment for your business and buyer locations.
- Confirmation and receipt: Decide which success message, email, or receipt the buyer should receive, then test that exact path.
- Fulfillment: Assign the shipment, download, booking, onboarding, or service-delivery step to a person or connected system.
- Support: Publish a contact route and make the refund or cancellation process clear before customers pay.
WP Full Pay supports tax choices on one-time and subscription forms, but a setting does not decide your tax obligations. Stripe Tax can also add Stripe fees. The current tax configuration guide explains the available form settings.
How to sell on WordPress without WooCommerce
1. Install and connect WP Full Pay
In the WordPress dashboard, go to Plugins → Add New Plugin, search for WP Full Pay, install the plugin, and activate it. Then open Full Pay → Settings → Stripe account and connect the appropriate Stripe account.
Ordinary setup uses Stripe Connect, so you should not copy API keys from a legacy tutorial. Manual keys remain documented for customized code that uses the plugin’s internal API and for the WP Full Members add-on. Follow the current WP Full Pay connection guidance if either exception applies.
Go to Full Pay → Payment Forms and start a new payment form. For a single purchase, choose an Inline Payment or Checkout Payment form. Choose a subscription form only when the offer genuinely renews on a schedule.
Use the current form editor to configure the payment, appearance, fields, and notification settings.Configure the offer name, price, currency, and the customer fields you actually need. Then choose the layout. Inline keeps the fields on your page. Checkout redirects the buyer to a Stripe-hosted payment page. The right choice depends on the form type, customer workflow, and how much page space you have.
3. Build the sales page
Create a normal WordPress page for the offer. Explain what the buyer receives, who it is for, the price, delivery timing, important restrictions, refund terms, and how to get support. Add original product images or a concrete service description instead of relying on the payment form to sell the offer.
Insert the saved form with the WP Full Pay block or its shortcode. Keep the call to action close to the price and key terms so customers do not need to reconstruct the offer at checkout.
4. Configure the post-payment experience
Review the success message, confirmation page, notification, and receipt behavior available in your form and Stripe setup. A receipt confirms payment, but it does not ship a product, grant a download, reserve a seat, or schedule a service unless you have built that separate handoff.
If another system needs to react after payment, WP Full Pay can send a POST webhook after a transaction is successfully recorded. Treat that as an integration trigger, not as guaranteed fulfillment. Build logging, retries, duplicate protection, and a manual recovery path around the receiving system. The webhook documentation explains the supported event boundary.
5. Run a complete test purchase
Test mode should cover the entire buyer and operator journey, not just the green success message. Use Stripe’s documented test payment details and complete the form as a customer would.
- Check the page on desktop and mobile.
- Confirm the product name, amount, currency, and any calculated tax.
- Verify the successful payment appears in both WP Full Pay and the intended Stripe test environment.
- Check the success message, email, receipt, and return link that the buyer sees.
- Trigger the manual or automated fulfillment step and confirm the right order details arrive.
- Try a documented failed-payment scenario and confirm the buyer gets a useful next step.
After the test flow passes, switch the site and form to the intended live connection. Recheck every live product, price, tax choice, payment method, success URL, and notification before promoting the page.
Keep lightweight orders manageable
A small checkout still needs an operating routine. Create one place where the responsible person can match each successful payment to its delivery status, customer conversation, refund status, and accounting record. The Stripe payment ID or the transaction record in WP Full Pay can help connect those records without pretending that the payment log is a complete order-management system.
- Review successful and failed transactions on a defined schedule.
- Assign every successful purchase to a fulfillment owner.
- Keep availability, delivery timing, and prices on the sales page accurate.
- Document what happens after a duplicate payment, failed webhook, refund, or customer dispute.
- Reconcile gross payments, tax, Stripe fees, WP Full Pay fees, and refunds instead of treating the payout as the sale amount.
This routine is often enough for low order volume. If it becomes a patchwork of spreadsheets, inbox searches, and manual corrections, that is evidence that the business has outgrown the lightweight approach.
Choose the smallest checkout that fits
A form is not the only lightweight option. Match the checkout surface to how customers encounter the offer.
- Use a payment form when the buyer should remain on a detailed product or service page and you need a few customer fields.
- Use a payment button when a compact call to action is enough. See the payment button guide for the main button patterns.
- Use a Stripe Payment Link when you need a shareable hosted checkout URL for email, social media, or a simple landing page. The Stripe Payment Links guide covers that route.
- Use a commerce platform when customers need a cart, inventory, shipping rules, automated product delivery, or a larger order-management workflow.
Questions about selling without WooCommerce
Can you sell physical products with WP Full Pay?
Yes, when the payment form and a separate operational process cover the sale. WP Full Pay can collect the payment, but you still need to manage stock, packaging, shipping rates, tracking, returns, and customer support.
Can you sell digital products with a payment form?
Yes, if you provide a secure delivery process. The payment form does not automatically create expiring download links, issue software licenses, or revoke access after a refund. Add and test those capabilities separately if the offer requires them.
Does WP Full Pay replace WooCommerce?
No. It can replace the need for a full store in a narrow payment workflow, but it does not provide WooCommerce feature parity. It is a Stripe payment-form plugin with a different scope.
Are receipts and taxes automatic?
Do not assume so. Configure the form’s tax option and the confirmation or receipt behavior needed for your account, then test them. Your legal, tax, and invoicing duties depend on the business, offer, and buyer location.
Start simple and keep the boundary clear
Selling on WordPress without WooCommerce works best when the offer is simple and the surrounding operation already has an owner. Build a clear sales page, use the smallest payment surface that fits, and test every step from checkout to delivery.
Ready to build the payment step? Review WP Full Pay, define the handoff after payment, and create the first form in test mode before accepting a live order.