How to accept payments through Gravity Forms

Gravity Forms needs a payment add-on to send a form total to a payment processor. Choose the gateway based on where your customers are located, which payment methods they expect and whether you need one-time payments, subscriptions or refunds.

The manual route is to install and configure the gateway add-on yourself. That is fine for a simple form, but every gateway has different connection screens, payment fields, webhooks and limitations. Gravity Forms itself does not provide a payment processor. An SSL certificate and a gateway account are required for common integrations such as Mollie and Stripe.

Create or edit the form in Forms and add the fields that determine the charge. Use Product, Option, Quantity, Shipping and Total fields as needed, then add customer details such as name, email and billing address.

Add the gateway's payment field when its documentation requires one. For example, Stripe's card collection method needs a Stripe field, while Stripe Checkout collects payment details on the hosted checkout screen instead. With Mollie, saving a form containing a Mollie field can create a payment feed automatically.

Open the relevant add-on settings under Forms → Settings. Choose test mode first, connect the gateway account and select the correct business profile, website profile or account where the add-on asks for one.

Do not start with live mode. Test mode prevents real charges while you check the form, and some gateways configure webhooks during account connection. If the site is private or blocked from receiving callbacks, payment status updates may not reach WordPress.

Open the form and go to Settings, then choose your payment add-on. Create or edit the feed and select the transaction type, usually Products and Services for a one-off payment. Set the payment amount to the form total or to a specific product field.

Map the email, name and billing fields required by the gateway. If you use more than one feed, enable conditional logic so only one feed runs for each submission. Without an active feed, the form can collect an entry but nothing is sent to the payment processor.

Decide which confirmation, notification or connected feed should run only after payment succeeds. This matters for account creation, file delivery, bookings, stock updates and other actions that should not happen after an unpaid submission.

Use payment status conditions or post-payment actions where the add-on supports them. Gravity Forms can record statuses such as Paid, Processing, Pending, Failed and Refunded, but the exact statuses depend on the gateway. A common Friday problem is treating a submitted entry as paid when the customer abandoned the gateway checkout or the payment is still pending.

Preview the form and submit several test orders, including a successful payment, a declined payment, an abandoned checkout and any conditional pricing paths. Check the entry, payment status, transaction ID, confirmation message and notification emails. Also confirm that your currency in Gravity Forms matches the currency accepted by the gateway.

When everything is correct, change the add-on from test to live mode and make one small real payment that you can refund. For the fast route in Europe, use the Gravity Forms Mollie Add-On when you need iDEAL, Bancontact, cards, refunds or partial refunds rather than PayPal. Mollie supports one-time payments through a payment feed, but recurring payments are not supported by its Gravity Forms add-on.