# Payment Forms

Funnelish includes two widget options that you can use to collect customer information, create gateways, and process payments. These widgets are called [2 Step form](/start/funnel-builder/editor-forms/2-step-form.md) and [Payment form](/start/funnel-builder/editor-forms/payment-form.md). In this article, we show you how to configure those widgets on a step.

### Before you start

Make sure you place a payment form widget on a **Checkout** step. Payment widgets do not work on other types of steps (e.g. Upsell or Landing). If you need to change the step type of your current page, you can [change it from the step settings.](https://docs.funnelish.com/start/creating-a-funnel/steps#changing-step-types-url)

If you are working with a blank step, choose **Checkout** type. If you are working with a template, select the **Order** page.

<figure><img src="/files/PFhOAw5zpHkqJiAeVjWY" alt=""><figcaption></figcaption></figure>

To test and preview the forms, you must add products to your funnel.&#x20;

* To learn more, see [Add Products](/start/creating-a-funnel/products.md).

## Forms

There are two widget options. Click a link to learn more.

* [**2 Step form**](/start/funnel-builder/editor-forms/2-step-form.md) gives you a template to collect user information and integrate payment gateways.
* [**Payment form**](/start/funnel-builder/editor-forms/payment-form.md) provides a template tool to integrate payment options.

![Form widgets](/files/bgU1I74YGjnPydojAQMt)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.funnelish.com/start/funnel-builder/editor-forms.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.