WordPress payment form

Quick answer: If you need to collect a one-time payment inside WordPress, GriffinForms lets you build that flow directly in a form with Stripe or PayPal, payment totals, and payment status tracking. It is a better fit than a full store when the job is a registration fee, donation, service deposit, course payment, or a simple order form.

WooCommerce is the right tool for a catalog or store. A payment form is the right tool when there is a single payment step attached to a workflow, not a product archive.

This page covers what GriffinForms payment forms support, the most common use cases, and the simplest setup path.

GriffinForms payment forms are built around a shared Review & Pay workflow that now supports both Stripe and PayPal:

• Stripe and PayPal support. Offer inline Stripe card entry, PayPal popup approval, or both from the same payment form.
• Payment field. Use products, quantities, live totals, and a Review → Pay step.
• Test and live credentials. Validate with Stripe test keys or PayPal sandbox credentials before switching to live mode.
• Submission payment status. The submission record stores the payment summary and status for support follow-up.
• Confirmation flow. Users receive a clear end-of-flow confirmation after checkout, and admins can review payment details later.
• Conditional logic. Adjust the flow or totals based on earlier selections when the payment path depends on the user’s answers.

Current scope is one-time payments attached to a form workflow. That makes this a strong fit for fees, deposits, donations, and simple checkout-style forms without turning the site into a full catalog store.

Common scenarios for a WordPress payment form include:

Event registration with a fee

Collect attendee details and payment in a single flow.

Membership sign-up

Charge an initiation fee or intake fee before the account is created.

Donation collection

Use a simple payment form for one-time donations without a store checkout.

Service booking deposits

Take a deposit at the point of booking and keep the rest of the workflow in one place.

Course enrollment fees

Collect a registration or enrollment payment alongside the rest of the form fields.

For a deeper look at the payment mechanics, see the Payment field documentation, the Stripe gateway setup guide, and the PayPal gateway setup guide.

To set up a payment form in GriffinForms:

1. Install GriffinForms. Activate the plugin and open the form builder.
2. Connect a gateway. Use the Stripe or PayPal setup guide to add your test, sandbox, or live credentials.
3. Add the Payment field. Build your product, fee, or donation structure and set the payment flow.
4. Review the submission view. Check payment status and totals in the admin submission screen after a test checkout.
5. Publish the form. Embed it with the Gutenberg block or shortcode, then run a real frontend test before launch.

That is the shortest path. If you need the precise configuration screens, the Stripe, PayPal, and Payment field docs are the better place to follow the step-by-step UI.

Questions that come up most often:

Does GriffinForms support Stripe or PayPal?

Yes. GriffinForms supports both Stripe and PayPal for one-time payment forms, and each gateway is configured through its own integration settings.

Can the payment amount be variable?

Yes. The Payment field supports product-style entries with quantities and can be used in flows where the total changes based on the user’s selections.

Is test mode available before going live?

Yes. Set up Stripe with test keys or PayPal with sandbox credentials first, validate the flow, and then switch to live credentials when you are ready.

Does GriffinForms send a payment confirmation email?

Yes. The form can send confirmation messaging, and the submission record keeps the payment details and status for later review.

Can I combine a payment form with user registration?

Yes. If the form also needs account creation, GriffinForms supports registration workflows in the same flow.