Themeisle Docs

Appearance

Custom Fields in WP Full Pay Forms ​

Custom fields let you collect additional information from customers during checkout. This article explains which field types are available, what layout limits apply, and what data is sent to Stripe as metadata.

Custom field and layout limitations ​

WP Full Pay supports text input custom fields only. You can add up to 10 custom text fields per form.

To add custom fields to a form:

  1. Open WP Full Pay → Forms and select the form you want to edit.
  2. Go to the Form Fields section of the form editor.
  3. Under Custom fields, click Add field and enter a label for each field.
  4. Optionally set Make custom fields required? to "Yes" to prevent submission without a response.
  5. Save the form.

You can reorder custom text fields within the Custom fields list, but you cannot add other custom field types such as:

  • checkboxes
  • radio buttons
  • dropdowns
  • optional consent fields

Custom fields and built-in fields follow the supported form layout and editor options. You cannot place a custom field or checkbox in an arbitrary location on the form.

Supported text custom field values are stored with the transaction as Stripe metadata. See What metadata is sent to Stripe for details.

What metadata is sent to Stripe ​

Supported text custom field values are stored as Stripe metadata on the transaction.

Where you find metadata depends on the form type:

  • Donation and one-time payment forms: metadata is on the Stripe charge (visible in Stripe Dashboard → Payments).
  • Subscription forms: metadata is on the Stripe subscription (visible in Stripe Dashboard → Customers → Subscriptions).
  • Save card forms: metadata is on the Stripe customer (visible in Stripe Dashboard → Customers).

The built-in Terms of Service checkbox should not be treated as guaranteed Stripe metadata. If you relabel that checkbox for a checkbox-style opt-in, test the resulting Stripe object in test mode before going live.

If you must store checkbox-style consent in Stripe, WP Full Pay does not provide a built-in custom checkbox field for that purpose. Use a custom integration or automation workflow to record the consent where you need it.

For step-by-step screenshots of each location, see Where are custom fields on the Stripe dashboard?

If you need to attach metadata that comes from URL parameters rather than form fields, see Adding custom metadata to payments.

When to use Stripe settings instead ​

Custom fields are only for collecting extra text input. If you are trying to configure recurring billing behaviour or customer emails, use the related WP Full Pay and Stripe settings instead:

  • For recurring receipts, upcoming renewal emails, failed payment emails, and installment-plan notifications, see How to configure email notifications?. Some notifications are sent by WP Full Pay, while others must be enabled in Stripe.
  • For subscription product names, transaction descriptions, installment limits, and Billing cycle starts behavior, see Creating a subscription form.