How to accept payments through WordPress forms

Decide whether the customer must pay inside the form or can be sent to a hosted checkout page. A hosted payment link is suitable for a fixed price, such as a consultation booking or simple donation. The form can collect contact details first and then send the visitor to the payment page.

For variable totals, recurring payments, payment confirmations or fulfilment that should happen only after payment, use a payment add-on. WordPress core and ordinary contact forms do not provide payment processing by themselves.

Add the fields needed to identify the customer and understand the order: name, email address, product or service choice, quantity and any required notes. If the amount changes according to the visitor's choices, use product and total fields supplied by your form plugin rather than allowing the visitor to type an unchecked amount.

Make the email field required and explain what happens after submission. Do not ask customers to enter unencrypted card details into ordinary text fields.

For a fixed amount, create a payment link or buy button in your payment provider's dashboard, then configure the form confirmation to redirect to that hosted checkout page. PayPal's payment links and buttons send buyers to a PayPal-hosted checkout and can be configured with a return URL.

This route is quick, but it has an important limitation: the form submission and payment are separate events. Unless you add custom server-side matching or webhook handling, you cannot reliably tell which form entry was paid, and it is unsuitable for changing totals or subscriptions.

For payments tied to the form, install and activate the payment integration supported by your form plugin. In Gravity Forms, the PayPal Checkout Add-On is the current PayPal integration for one-time payments and subscriptions. Add a PayPal field or pricing fields to the form, then connect the form to your PayPal account through the add-on settings.

Create a payment feed for the form and choose whether the transaction is a one-time product or service payment, a donation-style payment or a subscription. Map the payment amount to the form total or the relevant product field. Subscription settings include the recurring amount and billing cycle.

Configure the confirmation message and email notifications separately from the payment feed. If you have more than one payment method or payment feed, add a required payment-method field and use conditional logic so only the matching feed runs. Payment add-ons process only one feed per submission; without conditions, the first feed may be used.

Delay fulfilment where possible. For example, do not send a download, create a paid account or release a booking merely because the form was submitted. Use a post-payment action or payment-status check so the action occurs only after the processor confirms payment.

Connect the payment account in sandbox or test mode first, submit the form with successful and failed payment scenarios, and check the entry, confirmation, notification and payment status. Then make a small real payment and verify the transaction in the payment provider's dashboard before promoting the form.

Check the site uses HTTPS, the total is correct, the return page works and cancelled payments are not treated as completed. If the integration reports that its webhook is inactive, fix that before launch; webhooks communicate events such as completed, failed or cancelled payments back to the form system.

The fast way: use Gravity Forms with the Gravity Forms PayPal Checkout Add-On, add the pricing and PayPal fields, connect PayPal, create a one-time or subscription feed, and test it in sandbox. It avoids building the payment and payment-status connection yourself while keeping the checkout attached to the form.