How to accept online payments on a WordPress site

Use a hosted payment link when you need one fixed charge, such as a deposit, donation, consultation, or event ticket. Stripe creates the checkout page and handles the card details away from your WordPress site. Payment Links can contain products, prices, customer fields, and completion settings.

Use WooCommerce when you need products, stock, shipping, taxes, customer accounts, or orders. Use a dedicated payment-form plugin when you need a payment form without building a full shop, particularly for one-time or recurring payments.

Create and verify your Stripe account, or choose the payment processor supported by your chosen setup. Complete the business, identity, payout, and tax details requested by the processor before switching to live payments.

Keep test mode separate from live mode. Do not put secret API keys in a WordPress page, Custom HTML block, theme file, or browser-side JavaScript. A payment integration should keep sensitive credentials on the server or inside the trusted plugin connection.

For the no-plugin route, create a Payment Link in Stripe, set the product, amount, currency, customer information, and confirmation behaviour, then copy the generated URL. Add a WordPress Button block to the payment page and paste the URL into its link field. WordPress documents the Button block as a way to link a button to an external URL.

This route is genuinely fine for a small number of fixed payments. Its drawbacks are important: the form is hosted by Stripe, WordPress does not create a native order record, and you have limited control over conditional fields, custom workflows, and on-site confirmation. A Custom HTML block can also hold payment markup, but WordPress may remove scripts or iframes for users without the required unfiltered HTML capability.

For a branded form inside WordPress, install and activate WP Simple Pay Pro Plugin, then follow its setup wizard to connect your Stripe account. Create a form for a one-time or recurring payment, set the currency and amount, and add the customer fields you actually need.

Insert the generated form on a page using the plugin’s available WordPress editor or page-builder integration. Do not collect card numbers in an ordinary WordPress form. Let Stripe-hosted fields or checkout handle payment details instead.

Set the success message or return page, payment receipt options, and the email address that should receive payment notifications. Make the confirmation state clear: tell the customer whether the payment succeeded, failed, or needs another attempt.

If the integration uses webhooks for recurring payments, fulfilment, or payment records, confirm that the webhook status is enabled or configured. Webhooks can fail when a firewall, security plugin, cache layer, REST restriction, or staging URL blocks Stripe’s request.

Run a complete test on desktop and mobile: open the page, submit the form, complete the payment, check the success message, confirm the receipt, and verify the transaction in Stripe and WordPress. Test a declined payment and, where relevant, a recurring payment or 3D Secure authentication.

Use Stripe test mode and test payment details rather than real card numbers. Stripe specifically warns against testing live mode with real payment details, and its test cards can simulate successful payments, declines, refunds, and authentication flows.

When the test succeeds, connect the live Stripe account or switch the plugin from test mode to live mode, then repeat the checkout once with a real low-value payment if appropriate. Check the payout account, confirmation email, refund process, and the page customers see after payment.

The fast route is a payment-form plugin such as WP Simple Pay Pro Plugin: connect Stripe, build the form, place it on a page, and test it. It is a better fit than WooCommerce when you need standalone one-time or recurring payment forms rather than a complete online shop.