Custom fields let you collect additional info in your payment forms. You can add as many as you want for all four plan types.

How do I add custom fields?

In the plan creation or edit screen, you will see a toggle to switch on custom fields. Switch this on to see additional options. You can configure each custom field to have only the label, or add an optional description and placeholder text. Custom fields are optional by default but you can make them required if you prefer.


What will customers see when I add custom fields?

Your customers will see these fields in the payment form along with the required email, name and card number fields. Here's an example:

Custom fields also automatically adjust how they look based on whether you've only added a label, or a label, description, and placeholder text.

Where does the data from custom fields go?

Answers to custom fields are visible to you and other logged in admins via the customer summary page (accessed via the "i" icon on the customers page in your Paythen dashboard).

Here's an example of what you and other logged in admins will see:


When your customers view this same summary page as non-logged in users, they will not see this entire "Additional info" section.

What type of custom fields can I create?

Currently, you can only create text input custom fields. You can make them required or optional. In a future update, we will add dropdowns, multiple choice questions and more. If you need these field types, click on the chat icon and let us know.

Can I send custom fields data into other systems, like my CRM?

Not at this point, but with our Zapier integration in active development, you will be able to very soon.

Can I change a customer's answers to custom fields?

No. Currently you can only view answers to custom fields that your customers provided on the payment page. You can't change these answers. We will be adding the ability to update and edit custom field answers in a future update.

The Paythen team is here to answer any questions or feedback you might have. We'd love to hear from you.

Did this answer your question?