--- updatedAt: 2026-09-03T10:39:18.000Z agentTools: projectIndex: https://docs.corefy.com/llms.txt --- # Initiate Route configuration **Routes** establishment and configuration is a feature that enables creating specific **Routing strategies** and distributing the payment/payout flow in the most pertinent way. ### For your information! **Routes** are the lower-level elements that function within a particular **Method** and work at the core of processing. ## Configure Routes 1. Go to **Processing** and choose the **Payment scheme** you previously created on the grid. 2. Navigate to the **Payment methods** or **Payout methods** tab of the specific **Payment scheme** and click the specific **Method** on the grid. 3. Then, go to the **Routes & Configuration** tab. The page is divided into two parts. On the left side, you can review the list of **Routes** incorporated into the particular **Method**. You can also sort the **Routes** using the **Filter** icon or initiate a search of the desired **Routes** according to certain criteria via a **Search** icon. 4. Each **Route** possesses a definite status: {`

Status	Description
Enabled	The Route configuration requires the Route to be Enabled within the given Method. It becomes Enabled after you click its corresponding toggle.
Inactive	The Route becomes Inactive after you switch off the corresponding toggle.
Disabled	The Route becomes Disabled only when you switch it off in the Provider account settings. It cannot be used in processing.

`} 5. You can review the **Route configuration** parameters by clicking the side chevron, which contains the following: * **Processing fields** that are required or optional for this specific **Route** (e.g. Card Number, CVV, etc.); * **Features** the **Route** supports (e.g. Payment with 3DS, etc.); * **Limits** of the amount for a given **Route** (minimum and maximum values). 6. On the right part of the page, you can review the **Configuration** that presupposes aggregating **Routes parameters** into one list based on similar peculiarities of each **Route**. 7. The **Configuration parameters** are divided into three categories, namely **Fields**, **Currencies** and **Features**. {`

Category	Description
Processing fields	Each field contains the Data type, Included routes, Action icon, and Validation type. The Validation type contains two options: Required and Optional. The Required option is chosen on condition that at least one Route sets this field as required. If all the Routes mark this field as Optional, it automatically becomes Optional after the Configuration. You can preview the data each field contains. Click the Action icon, choose Settings and the system should open the sidebar with the corresponding data. Also, you can change the Validation type for the chosen field. If you select the Optional type for the field, the system enables the Data generator. It is a tool that fills the field with randomly generated data.
Currencies	You can review the amount limits aggregated automatically from the Routes. The system shows you the upper and lower limits by enclosing all the Routes.
Features	You can overview the possible features and the Routes that support them.

`} 8. You can **Include** or **Exclude** the specific field. Click the **Action** icon and choose the corresponding action: * The **Include** option switches on the **Inactive Route**. Beware that it does not refer to the **Disabled Routes**. * The **Exclude** option simply cuts off the related field.

9. Then, you can save the new [Version](/docs/discover-versions#/) and use the **Payment scheme** that was previously configured or the **Default Payment scheme** in further interactions. 10. You can also proceed with establishing the [Routing scheme](/docs/employ-routing-actions-cascading#/). ## Troubleshooting 1. Check the status of the associated **Provider account**. 2. Only **Routes** connected to active **Provider accounts** can participate in **Routing**. 3. If the **Provider account** is disabled, enable it in the **Provider account settings**. 1. The **Route** may be archived. Archived **Routes** are hidden from the list by default. 2. To include the archived **Routes** to the grid, click the filter icon in the **Configuration** tab. 3. Switch off the **Hide Archived entities** toggle and click **Apply**. 4. The system then shows both enabled and archived **Routes** on the grid.

1. Check both the **Route** and **Provider account** statuses. 2. A **Route** must be enabled, and its associated **Provider account** must be active to participate in **Routing**.