Introduction

The SIBS Backoffice is the operational and administrative platform of the SIBS Payment Gateway (SPG), providing Merchants and operational teams with access to transaction monitoring, operational actions, reporting capabilities, and payment-related management functionalities.

This chapter focuses on the operational usage of the SIBS Payment Gateway (SPG), providing a structured overview of the Backoffice and vTerminal components and their role within the SPG operational ecosystem.

In addition to API-based integrations, SPG includes operational tools that allow users to consult transactions, perform financial operations, monitor activity, and support operational processes. These tools are used in day-to-day activities, including transaction management and operational handling.

The Backoffice centralizes operational visibility across transactions initiated through different integration models, including Server-to-Server integrations, Form Integration, plugin-based integrations, and manually triggered vTerminal operations.

The Backoffice provides access to transaction information, filtering capabilities, and detailed views of operations, with access and available functionalities defined by user profiles. Available functionalities, operational actions, and transaction visibility may vary according to the permissions associated with each Backoffice user profile.

Transaction statuses, operational states, and payment lifecycle semantics presented in the Backoffice follow the concepts described in C. Meta Information, Codes and Transaction States.

Complementing the Backoffice, SPG includes the vTerminal, a virtual operational interface that allows authorized users to manually initiate selected payment-related operations through dedicated forms and operational workflows, namely MB WAY and Multibanco Reference operations.

The objective of this chapter is to present these operational components in a structured and practical way, providing clear operational guidance for their use.

For additional information regarding transaction status synchronization, webhook notifications, and asynchronous transaction processing, refer to E. Notifications and Transaction Status.

Operational Components of the SIBS Payment Gateway (SPG) Environment

The following diagram illustrates the relationship between SPG integration models, operational tools, and centralized transaction visibility.

Scope

This chapter covers the operational aspects of SPG related to the Backoffice and vTerminal, including:

• Navigation and core concepts of the SPG Backoffice
• Consultation and management of transactions, including search and detailed views
• Monitoring of transaction lifecycle progression and operational status visibility
• Execution of operational actions, according to user permissions
• vTerminal usage, including available functionalities and configuration requirements
• Execution of manual operations through vTerminal forms
• Presentation of operational procedures based on Backoffice and vTerminal functionalities
• Operational usage of SPG tools complementary to API-based integrations

Objective

The main goal of this chapter is to:

• Enable efficient and correct use of the SPG Backoffice and vTerminal
• Reduce operational errors through clear usage guidance
• Improve onboarding of merchants and operational users
• Provide structured guidance for common Backoffice and vTerminal operations
• Provide operational teams with a consistent reference for transaction consultation, operational workflows, and manual payment-related procedures

This chapter serves as a practical operational reference for the use of Backoffice and vTerminal functionalities within the SIBS Payment Gateway environment.

Summary

The SIBS Backoffice provides a web-based interface for the management and monitoring of payment-related activities, with functionalities defined by user profiles and permissions.

Within this platform, the vTerminal enables the manual execution of financial operations through the completion of dedicated forms, where each form corresponds to a single transaction.

Together, these components enable transaction consultation, operational actions, monitoring of payment-related activities, and manual execution of payment operations within the SPG environment.

These operational components complement the API integration capabilities of SPG by providing centralized operational visibility, transaction consultation, and manual operational workflows within the same payment ecosystem.