The Console is the administration interface for the payment infrastructure.

It enables teams to configure, monitor, and operate their payment environment from a unified interface, including routing, risk controls, merchant configuration, and operational workflows.

This documentation explains how to use the Console consistently across all modules.

Access and scope

• The Console operates on a hierarchical structure that defines how objects such as companies, merchant accounts, and configurations are organized. To understand how environments are structured and how objects relate to each other, see Structure.
• Objects (Lists, Contracts, Routing rules, etc.) always belong to a Company.
• When you open an object, the header shows the Company context and the object location using breadcrumbs.

Navigation structure

The Console interface relies on two main navigation components:

• a left sidebar for global navigation across modules
• breadcrumbs for local navigation within a module and between objects

The sidebar allows users to switch between major Console sections such as Payments, Analytics, Payment Network, and Company settings.

Breadcrumbs indicate the current object location in the hierarchy and allow users to navigate back to parent collections.

In most modules:

• table pages display collections of objects or records
• clicking a row opens the object detail page
• detail pages allow users to inspect an object safely
• edit mode allows users to modify the object configuration

This navigation model is consistent across the Console.

Permissions

Actions shown in the UI are permission-aware.

Depending on your role, you may or may not see:

• Create
• Edit
• Delete
• Import
• Delete all
• Save / Reset

If an action is not available to your role, it is not displayed.