Concepts & Workflows
Overview
This section explains the fundamental concepts and workflows that define how the Merchant Portal operates.
It provides a structured understanding of key elements such as transaction lifecycles, account hierarchy, user roles, and system interactions, helping users build a clear mental model of how different components are connected.
Use this page when you need to understand how the platform works, how processes relate to each other, and how configuration and structure impact day-to-day operations.
Key topics covered include:
- Transaction lifecycle and related operations
- Account Tree structure and hierarchy design
- User roles, permissions, and access control
- Core workflows such as payment processing and reporting
Key Concepts
Transactions Lifecycle
Transactions in the Merchant Portal follow a defined lifecycle depending on the transaction type and subsequent actions performed by operators. A transaction typically starts as an initial request, such as a debit or pre-authorization, and can then evolve through additional back-office operations.
For pre-authorizations, the lifecycle usually includes a capture or reversal. For debit transactions, the lifecycle can include refunds or chargebacks. Each action creates a new related transaction entry, allowing users to track the complete history of a payment flow within the system.
The transaction history view links related operations within the same payment session, enabling users to understand how a transaction evolves over time and how individual actions impact the overall outcome.
Account Tree
The Merchant Portal is structured using a hierarchical account tree that organizes entities into multiple levels. This structure allows customers to represent their business model and operational setup within the platform.
The hierarchy includes several levels, typically representing PSP, division, merchant, and channel. Each level serves a specific purpose, such as grouping entities by region, brand, or technical configuration. The structure is flexible and can be adapted to align with different organizational models.
Entities within the account tree have statuses that directly impact transaction processing. For example, disabling an entity prevents processing temporarily, while closing an entity is a permanent action. Navigation within the hierarchy is supported through breadcrumbs and drill-down functionality.
The structure of the Account Tree depends on the business setup and hierarchy design. See Account Tree for guidance on how to define your hierarchy.
User Roles and Permissions
Multi-Factor Authentication
Workflows
Payment Processing Flow
Refund Flow
Reporting Flow
The transaction search is designed primarily as a reporting tool. It allows users to retrieve and analyze transaction data based on defined criteria, rather than serving as a real-time monitoring or analytics solution.
Users define a search using mandatory filters such as time frame, transaction type, and environment mode (for example live or test). Additional filters can be applied to refine the search further, enabling precise reporting across large transaction datasets.
Search results are displayed in a tabular format, where users can review transaction details, navigate to individual transaction records, and access related operational actions where applicable.