---
title: "Set Up Entity Custom Fields"
slug: "set-up-entity-custom-fields"
updated: 2026-01-30T17:43:26Z
published: 2026-01-30T17:43:26Z
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://resource.payrix.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set Up Entity Custom Fields

Create and access Entity Custom Fields through the Payrix Pro Portal to ensure seamless risk reviews and external data integration. The following sections describe how to create custom fields, assign them to merchants, and use field values to automate risk decisions.

## Prerequisites

Before creating and assigning Entity Custom Fields, decide on the following details for each custom field:

- **Field:** The name of the actual field. This can be between 1 and 500 characters. See the next section for best practices.
- **Label:** The label the merchant sees for the field while signing up. This can be between 1 and 500 characters.
- **Required:** A yes or no value on whether to make the custom field mandatory during signup.
- **Default:** An optional default value to prefill the field.

#### Field Naming Best Practices

Entity Custom Fields use a key-value approach, similar to standard coding languages, to uniquely identify each field and its value. Follow these industry best practices to ensure all members of your team can easily find, identify, and duplicate the field as needed for each entity:

- **Use simplicity:** Avoid unnecessary complexity and be descriptive with your name.
- **Set field formats:** Choose one format: camel case (`yourField`), snake case (`your_field`), or kebab case (`your-field`). We recommend camel case.
- **Be consistent:** Match field names to those used in your CRM or other system, where applicable, for easier visibility and integration.
- **Use full words:** To avoid ambiguity among developers, use full words for names (for example, `quantity` instead of `qty`).
- **Use verbs for Booleans:** For fields that accept a Boolean value (`yes`/`1` or `no`/`0`), use verb prefixes (such as `hasAccess` or `isVIP`).

## Create and Assign Entity Custom Fields

After deciding which Entity Custom Fields you want to add, assign them to individual merchants. Because the portal doesn’t offer dropdown menus, duplication function, autocomplete options, or predefined lists to select previously created Entity Custom Fields, you must adhere precisely to your field naming conventions. This precision is vital to prevent any complications concerning fee application, risk policies, or decisions configured around this new field.

> [!NOTE]
> Notes
> 
> - You must manually set each custom field because we do not provide a dropdown menu of previously added custom fields or an autocomplete feature.
> - You must match your custom field exactly to ensure your risk policies, decisions, and fee rules will apply to that entity.

### Send Custom Fields with Merchants During Signup

You can include Entity Custom Fields on your Merchant Signup Form. To add these fields for merchants to complete during signup:

1. Open an [Implementation Services](https://wp4p.zendesk.com/hc/en-us/requests/new?ticket_form_id=28459221652627) ticket.
2. Provide the **Fields**, **Label**, **Required**, and **Default** values for each custom field.

After the Implementations team adds your Entity Custom Fields, the signup form displays each field to merchants during onboarding.

### Assign New Custom Fields to a Merchant

You can assign custom fields to store merchant‑specific values. You can then use those values to apply fee configurations, risk policies, and automated risk decisions.

Follow these steps in the portal to create and assign new Entity Custom Fields for an existing merchant:

1. Select **Merchants** under Management in the main side bar.
2. Select the merchant to go to their profile page.
3. Scroll down to the Custom Fields section on the Business tab.
4. Click **Add Custom Field** to open the Add Custom Field dialog.
5. Enter the field and the value that you want to assign.
6. Click **Add** to finish creating the custom field.

The merchant receives the new custom field for storing unique values. These values can be applied for fee configurations or risk policies and decisions.

## Trigger Risk Policies with Entity Custom Fields

Use Entity Custom Fields with risk decisions or policies to enhance risk management automations. This integration provides entity-specific data insights and improves boarding rates by aligning compliance-related information with your risk practices.

Complete the following procedure to use an Entity Custom Field as the rule condition for a policy or decision. To simplify the setup, this procedure includes only the high-level action items. For more detailed setup steps and information on risk policies, see [Use the Risk Management Page](/v1/docs/use-the-risk-management-page) and [Policies](/v1/docs/policies-partners).

To configure a risk policy using a custom field as criteria to trigger the risk:

1. Select **Risk** then **Policies** under Admin in the main side bar.
2. Click **Add Policy** to create a new policy.
3. Define the **Name**, **Stage**, **Target**, and **Status**components.
4. Click **Add Policy**.
5. Select the new policy from the table to add decisions.
6. Click **Add Decision**.
7. Select the primary Decision from the list available, then click **Next**.
8. Select **ENTITY_CUSTOM** from the dropdown menu as your sub-decision.
9. Enter your custom field name and set your **Value**.
10. Set your **Operator** and **Action**, then click **Next**.
11. Add any **Rules**, **Dependencies**, and **Failover Dependencies**.
12. Click **Create** to complete the process.

A PayFac-as-a-service platform. Software companies can act as payment facilitators without taking on the associated risks, compliance burdens, and investment.

The web portal offered by the Payrix Pro platform to accomplish tasks for their business through a web-based user interface rather than the API. The Payrix Pro portal contains general settings, payment processing options, reporting, fee settings, group assignments, user management, and much more.

An entity that can process transactions and has been onboarded through a Payrix Pro partner.

A risk automation configuration available to be set on Groups of entities to apply a review, and action/inaction of specified risk criteria as a decision rule, using the outcome of the risk review to determine whether to execute the decision action.

A comprehensive risk management system that automates and streamlines risk decision-making processes for entire portfolios or individual entities. Similar to decisions, policies use a rule-and-action logic; however, policies also integrate third-party risk services like GIACT, LexisNexis, and Equifax for more comprehensive risk review. (Note: Policies contain a component called decisions, which is different than Group risk decisions set from the Group profile.)