---
title: "Overview of Entities"
slug: "overview-of-entities"
updated: 2026-02-12T22:10:38Z
published: 2026-02-12T22:10:38Z
---

> ## 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.

# Overview of Entities

Understanding entities is crucial for enhancing portfolio management and streamlining operations, including merchant onboarding and payment facilitation services. Knowing various entity types and processes enables you to customize solutions with control over various capabilities. Fees, billing, automated risk decisions, white-label customization, onboarding workflows, and secure URL redirection hosting are some of the capabilities you can configure.

> [!NOTE]
> Note
> 
> Some terms apply at a facilitator level only and do not apply to partners and below. To request updates to your Division, Host, or Workflow configuration as a Payrix Pro partner, submit an [Implementation Services ticket](https://wp4p.zendesk.com/hc/en-us/requests/new?ticket_form_id=28459221652627).

## Entity Types

These entity types represent the types of business entities that interact with the Payrix Pro platform either directly or through a white-labeled offering:

- **Facilitator:** A payment facilitator (PayFac) offering products and capabilities of the Worldpay platform to their Payment Facilitation-as-a-Service partners, assuming all risk and underwriting liabilities as a payment facilitation business.
- **Partner:** A Payrix Pro partner, offering merchants the products and capabilities available through the Payrix Pro platform as a white-labeled referral of Payment Facilitation-as-a-Service.
- **Merchant:** A business successfully onboarded to the platform through a partner to accept payment transactions for products and services sold to customers.

## Entity Hierarchy

To illustrate the complex relationships among facilitators, partners, and merchants, this flow diagram provides a clear and detailed representation of the entity hierarchy within the platform ecosystem:

[Embedded content](https://lucid.app/documents/embedded/b666b097-82f6-49d3-9ba0-25449c2475bf)

## Entity Management Terms

These are technical terms for describing logical groupings of various processes, entities, and their relevant portfolio data on the Payrix Pro platform:

- **Partition:** A representation of a facilitator’s portfolio on the Payrix Pro platform, housing all partners, merchants, and user data, Host settings, and other platform-wide settings. Partitions can be further divided into Divisions, to create strategic separations for individual partner portfolios within.
- **Division:** A representation of a partner’s portfolio contained within a Payrix Pro Partition or the Partition of another facilitator-level entity that contains all merchant and user data, Host settings, and Workflow configurations. These settings and configurations can be modified on an individual basis without affecting other Divisions or merchants under a Partition.
- **Host:** A configuration of white-label branding configurations and platform-wide settings that can be applied at a Partition and Division level.
- **Group:** A collection of partner or merchant entities with same configurations applied for fees, billing, risk decisions, withdrawal flows, and other parameters.
- **Workflow:** An automated process configuration that assigns new merchants to an existing Group when they submit a completed signup form hosted under a Partition or Division.

[Embedded content](https://lucid.app/documents/embedded/48f299a3-d622-4b79-bf42-a87f58758acd)

### Divisions

A Division represents a partner’s portfolio within the Payrix Pro platform. During implementation, a Division is created for you to house all merchant and user data, Host settings, and Workflows associated with your portfolio.

The following diagram illustrates the relationship between Divisions and merchant entities. The Implementations team can apply white-label configurations (through Host settings) and merchant onboarding automation (through Workflows) for your Division. These configurations facilitate the seamless onboarding of merchants under your white-labeled portfolio.

> [!NOTE]
> Note
> 
> To access certain features, such as downloading 1099-K forms directly from the portal, you must white label your Payrix Pro portal and API. These features are enabled under your white-label configurations, and they will be unavailable if you choose not to white label.

[Embedded content](https://lucid.app/documents/embedded/a09d2e3b-6613-4e50-b7d6-b7948783e846)

### Groups

A Group is a collection of entities set up by a parent entity. The parent entity can configure fee settings, risk decisions, and other parameters that apply to all Group member entities. Groups can be configured by facilitators for partners, by partners for merchants, or by merchants for their sub-merchants.

Groups are useful because a parent entity can apply the same logic for various parameters and settings to multiple Group members at once. This saves a great deal of time and effort versus manually configuring each entity individually.

For step-by-step instructions on creating a Group and adding members to the Group, see [Set Up a Group](/v1/docs/set-up-a-group).

> [!NOTE]
> **Note**
> 
> The following describes the difference between Groups, Divisions, and Teams:
> 
> - **Group:** A collection of entities where you can configure fees, risk decisions, and setup parameters that apply to all entities in the group. This is sometimes called an *Org*.
> - **Division:** This is where workflows are set up to automatically add merchants to Groups when created, and also where the white label is configured.
> - **Team:** A collection of Payrix Pro users that share roles and similar user properties to access the portal or API.

### Workflows

A Workflow****represents a process configuration that automatically assigns new merchants to an existing Group when they submit a signup form hosted by a facilitator or partner. Workflows can be applied at a Partition (facilitator) and Division (partner) level.

Workflows can automatically add merchants to Groups with pre-established fee and billing settings, automated risk decisions, withdrawal schedules, and more as they are onboarded. Workflows can also move high-risk merchants to a group that applies more aggressive fees to help offset chargebacks, refunds, and other losses associated with high-risk entity action.

Division Workflow configurations override Partition Workflow configurations. If no Division Workflow configuration is set up, the merchant offering will default to the Partition-level Workflow configuration.

> [!NOTE]
> **Note**
> 
> Only facilitators can enable Workflow configurations at any level.
> 
> - For partners under the Payrix Pro Partition, submit an [Implementations Services ticket](https://wp4p.zendesk.com/hc/en-us/requests/new?ticket_form_id=28459221652627) to enable your unique Division Workflow.
> - For partners under another facilitator’s Partition, contact their implementation team with the preferred information below to have them create the Workflow on your behalf.

A Workflow consists of a trigger and an action. The trigger is the event that initiates the action to add or remove the specified merchant from specific Groups.

#### Workflow Triggers

Workflow Triggers are the events that occur that initiate the automated Workflow Action. The following triggers are available:

- **Create:** When a new merchant account is created, but not fully boarded.
- **Low:** When a new merchant account is reviewed and rated as a low-risk entity.
- **High:** When a new merchant account is reviewed and rated as a high-risk entity.
- **Board:** When a new merchant account has been approved and onboarded to the platform.

#### Workflow Actions

- **Add:** Adds the merchant account to one or more designated Groups.
- **Remove:** Removes the merchant account from one or more designated Groups.

## Entity User Login Capabilities

Users from each entity can log in to their respective portal accounts and perform actions based on their roles and access granted through Teams. Higher-level entities can access the accounts and portal views for their boarded entities unless manually restricted. For example, a partner-level user can typically log into and view their merchants’ accounts in the portal.

> [!NOTE]
> **Note**
> 
> In common scenarios where one merchant needs to log in to another merchant account as a result of multiple locations under the same business, a multilocation merchant structure is required. See [Multilocation Merchant Structure](/v1/docs/overview-of-users#multilocation-merchant-structure) for more information about multilocation structure setups.

## Entity Custom Fields

Entity Custom Fields provide a way to tailor how you manage custom data for merchant entities. This feature supports the collection of data requested for risk reviews, enhancing the risk management process. Using Entity Custom Fields also ensures your software integrates seamlessly, helping to increase onboarding rates.

With Entity Custom Fields, you can:

- **Streamline risk data requests:** Provide MCC-specific information requested from the Payrix Pro Merchant Onboarding and Risk teams to streamline reviews and reduce wait times.
- **Store external identifiers:** Link a merchant to an external CRM or ERP system using a unique ID.
- **Set custom risk flags:** Add internal risk scores or flags that influence automated decision-making.
- **Customize fee rules:** Apply specific fee structures based on custom field values, such as *High Volume Merchant*.
- **Set operational tags:** Tag entities with operational metadata like *Beta Tester*, *Seasonal*, or *VIP*.
- **Collect merchant metadata:** Capture data unique to a merchant’s workflow, such as sales rep ID, onboarding channel, or campaign source.

See [Set Up Entity Custom Fields](/v1/docs/set-up-entity-custom-fields) for instructions on creating and using custom fields.

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

The process of adding clients (merchants) to the Payrix Pro platform to use the Payrix Pro payment solutions. Also known as *boarding*.

1. Any merchant or partner account operating on the Payrix Pro platform.
2. In API terms, the top-level resource for any merchant or partner account.

In a Payrix Pro context, charges set by partners to monetize payment services for merchants. Partners can customize fees for specific merchants or set portfolio-wide fees using Groups.

By default, fees are applied to the merchant and paid to the partner account. A processed entry deducts the fee from the entity paying the fee. This fee is reflected in the entity's Available Balance and can be reviewed on the Balance Details page.

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 partner entity in the Payrix Pro system that receives fees collected from merchants. Also known as a *Vendor* or a *Referrer*

The portfolio associated with a partner. Every merchant is associated with a partner Division, where workflows are set up to automatically add new merchants to groups. This is also where white-label settings are configured.

A configuration of white-label branding configurations for each entity-hosted portal and platform-wide settings that can be applied at a Division (partner) level to maintain a consistent merchant experience.

Automation on a division, team, or user that seamlessly adds or removes an entity from specific groups when it is created by a login, added to a division, or added to a team. Also known as *Org Flow*.

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

A type of merchant services company that provides business owners with a way to accept electronic payments. Worldpay for Platforms is a payment facilitator.

A process that primarily focuses on the following key elements of the merchant’s application and the data provided when signing up for Payrix Pro:

- Validating the merchant’s business, known as *Know Your Business (KYB)*
- Validating the owners, known as *Know Your Customer (KYC)*
- Preventing illegal and fraudulent activity
- Validating the merchant’s bank account

The process of creating a disbursement of account balance funds to an entity’s registered deposit account. This process is also known as a *payout*.

A collection of entities where you can configure fees, decisions, and parameters that apply to all entities in the group. Also known as an *Org*.

The configuration that determines when balances from any entity’s account balance (available balance) will be withdrawn to their registered deposit or operating account and how much. It can be either one-time or recurring. Also known as *payout flow*.

A setting determining whether an entity is added or removed from the Group specified in its associated workflow. Also known as *Org Flow Action*.

The process of assessing and mitigating potential risk associated with transactions and merchant boarding and activity, including fraud prevention, anti-money laundering compliance, and monitoring chargeback rates.