---
title: "Onboarding Requirements Checklist"
slug: "onboarding-requirements-checklist"
updated: 2026-01-16T22:00:03Z
published: 2026-01-16T22:00:03Z
---

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

# Onboarding Requirements Checklist

This Implementations resource explains boarding form definitions and requirements.

To provide a frictionless and expedited merchant onboarding experience, the following information and fields must be provided, completed, or assigned by each respective partner, as described.

## Signup Form General Requirements

The following table describes the high-level requirements of the Signup Form. See [Signup Form Definitions](/v1/docs/signup-form-definitions) for a complete list of all Signup Form field values.

| **Requirement** | **Description** |
| --- | --- |
| **Beneficial Ownership Requirements** | Partner to require and pass all application required data fields in compliance with FinCEN’s Beneficial Ownership Information which includes: 1. Ownership Prong Info: Personal information on all Owners with 25% or more ownership interest 2. Control Prong Info: Personal information on the individual with controlling/significant responsibility |
| **Terms and Conditions** | Partner to pass/provide the merchant’s accepted Terms and Conditions attributes to include the following: 1. Terms and Conditions - Version 2. Terms and Conditions - Date Accepted 3. Terms and Conditions - Time Accepted |
| **Merchant IP Address** | Partner to pass/provide the merchant’s IP address in the **T&C IP Accepted** field |
| **Bank Account Validation** | Complete one of the following: - [Plaid Integration](/v1/docs/plaid-integration-guide) - [Document upload](/v1/docs/adding-a-bank-account#manual-bank-account-validation) of voided check, signature card, or bank statement |
| **Merchant Website** | Partner to pass/provide the merchant’s website link. If the merchant will be processing online transactions, the partner must pass/provide the website link used to process the online transactions. Partner websites or generic websites used for multiple merchants are not permitted. |
| **Payment Parameters** | Partner to pass/provide the merchant’s expected processing parameters to include the following: 1. Annual Processing Volume 2. Average Transaction Amount |
| **MCC Assignment** | Partner to pass the merchant category code (MCC) based on the merchant’s actual processing activity and to implement a Quality Control (QC) process to ensure the most accurate MCC Code is selected. If a merchant processes transactions not covered by a single MCC assignment, an additional MID setup might be required |
| **Cardholder Verification** | Partner to integrate its referred merchants to prompt for the entry of address verification service (AVS) and CVV fields (for applicable merchants/transactions) |
| **Transaction IP Address** | Partner to pass/provide the cardholder’s IP address with all transactions |
| ***Transaction*** ***Processing Method*** | Partner to confirm the one or more of the following transaction processing method: - PayFields - Terminals - API: Requires partner to pass TMX session ID |
| **Partner PCI Compliance** | Partner to provide an up-to-date PCI AOC document if responsible or involved in passing, touching, or housing cardholder data |
| **Merchant PCI Compliance** | Partner to request and provide PCI status on referred merchants level 3 or above (processing 20,000 transactions or more annually). |
| **Screenshots of Application Process** | Partner to provide screenshots of all pages in the application process. |
| **Final Visual Walkthrough of the Sign Up Process** | Partner to provide Payrix Pro Risk with a visual walkthrough of the sign-up process. To be scheduled prior to the launch of merchant submissions. |

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

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

A partner entity in the Payrix Pro system that receives fees collected from merchants. Also known as a *Vendor* or a *Referrer*

A four-digit number that describes a merchant's primary business activities. This classification is based on the International Organization for Standardization (ISO) and Standard Industrial Classification (SIC) codes for different types of businesses. Card brand networks use the MCC to identify a merchant’s business type and nature of operations at a high level.

The verification of a cardholder’s billing address in a transaction against the issuing bank’s address information for the cardholder. AVS is primarily used as a fraud prevention tool for eCommerce transactions.

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