Overview The Virtual Terminal is designed to allow operators to manually initiate payment operations directly from the SIBS Backoffice interface. While the feature simplifies operational execution, it should be used with a clear understanding of its intended purpose, operational limitations, and relationship with broader integration models. This chapter provides operational guidance for using vTerminal effectively and safely. Intended Usage Scenarios The Virtual Terminal is typically used in scenarios where manual payment initiation is required. Common examples include: It may also be used when a merchant needs to manually initiate a payment directly through the Backoffice operational interface. When Not to Use vTerminal Virtual Terminal should not be treated as a replacement for automated payment integrations. High-volume payment operations should typically rely on: These models provide better scalability for large transaction volumes. For broader integration model guidance, refer to: Operator Access Control Access to Virtual Terminal should be restricted to authorized operational users. Merchants should ensure that only users with legitimate operational responsibilities can manually initiate transactions. This helps reduce: For broader Backoffice access management guidance, refer to: G.1 – Backoffice SPG Validate Information Before Submission Operators should always validate payment data before submitting transactions. This includes verifying: Incorrect information may […]

Overview After a vTerminal operation is submitted, the platform generates an operational result that allows the operator to understand whether the transaction was successfully initiated, completed, rejected, or remains pending. The exact result depends on: Different payment methods may produce different post-submission behaviors, including: This chapter explains how operators should interpret transaction results after submitting a vTerminal operation and how these transactions become part of the broader SIBS Backoffice operational ecosystem. Immediate Post-Submission Behavior After an operation is submitted, one of the following behaviors may occur: These immediate behaviors do not necessarily represent the final transaction outcome. Operators should always validate the final transaction state before considering the operation completed. Result Information Available to the Operator Depending on the operation type, the platform may display operational information such as: Additional payment-specific information may also be displayed depending on the transaction type. Reference Operations For reference-based transactions, additional information may include: Authorization Operations For authorization-based transactions, additional information may include: Final Transaction States The transaction may eventually reach one of the following final states. Success The operation completed successfully. Examples include: The transaction may proceed to the next operational stage depending on the payment model. Pending The transaction has not yet […]

Overview The MB WAY Authorized Payment flow in the Virtual Terminal allows an operator to manually initiate a customer authorization request directly from Backoffice. This operation is used when the merchant needs to obtain customer approval for future merchant-initiated MB WAY payment collections. This flow is: The authorization is only completed after the customer approves the request in the MB WAY application. This chapter describes the end-to-end operational flow, including: A successful authorization creates a reusable customer authorization that may later be used for future merchant-initiated payment collections, depending on the merchant’s payment model. This chapter explains how to manually create an MB WAY authorization through the Virtual Terminal interface. Step 1 – Access Virtual Terminal Navigate to: SIBS Payment Gateway 2.0 → vTerminal → Virtual Terminal When the page loads: The operator must review the screen configuration before proceeding. Step 2 – Select Authorization Operation In the Operation field: Change: Purchase To: Authorization This changes the transaction behavior from an immediate payment request to an authorization request. After this step: The platform prepares the transaction as an MB WAY authorization flow. Step 3 – Expand Customer and Billing Sections Expand: These sections allow additional customer information to be registered before […]

Overview The Multibanco Reference flow in the Virtual Terminal allows the operator to generate a payment reference that can be used by the customer to complete a payment through Multibanco channels (ATM, home banking, or mobile banking). This operation: The generated reference must be used by the customer within the configured validity period. Step 1 – Access Virtual Terminal Navigate to: SIBS Payment Gateway 2.0 → vTerminal → Virtual Terminal The Virtual Terminal screen is displayed. Step 2 – Select Multibanco Reference In the Payment Method section: This activates the form for Multibanco Reference generation. Step 3 – Configure Operation and Expand Payment Fields In the Payment Info section: This enables the required fields for reference creation. Step 4 – Fill Core Payment Fields and Select Entity Fill the required fields: Entity Selection A merchant may have one or more Multibanco entities configured. The selected entity determines: The operator must select the appropriate entity for the transaction. Step 5 – Define Validity Period Define: Validity Enforcement The payment can only be performed: Outside this interval: Step 6 – Complete Form and Submit Operation Optionally fill: Customer Reference Delivery Options Billing Address All required fields must be completed according to the […]

Overview The MB WAY One-Off Payment flow in the Virtual Terminal allows an operator to initiate a real-time payment request to a customer’s mobile device. This flow is: The payment is only completed after the customer approves the request in the MB WAY application. This chapter describes the end-to-end operational flow, including: Step 1 – Access Virtual Terminal Navigate to: SIBS Payment Gateway 2.0 → vTerminal → Virtual Terminal At this stage, the operator is presented with the payment form. Step 2 – Select Payment Method In the Payment Method block: This selection dynamically configures the form for MB WAY operations. Step 3 – Define Operation Type In the Payment Information block: This defines a one-off payment request. Step 4 – Fill Payment Information Provide the required payment details: Optional: Step 5 – (Optional) Fill Customer and Billing Data Expand and fill, if required: Customer Block Billing Address Block These fields: Step 6 – Submit Payment Click the “Payment” button. This action: Video Tutorial – MB WAY One-Off Payment The following video provides a practical walkthrough of how to initiate an MB WAY One-Off Payment through the vTerminal. Video – MB WAY One-Off Payment Step 7 – Session Handling (Conditional) […]

Overview The Virtual Terminal operation form is the central interface used to manually initiate payment operations within the SIBS Backoffice. It provides a structured and guided data entry model, ensuring that all required information for a given payment flow is captured with consistency and validation. The form is dynamically adjusted based on the selected payment method and operation type, exposing only the fields that are relevant for the specific scenario. Across all supported flows, the form is organized into logical blocks: While the structure remains consistent, the field set and validation rules vary depending on whether the user is performing: This chapter details: The following vTerminal subchapters provide step-by-step operational procedures for MB WAY payments, MB WAY Authorized Payments (Mandate Creation), and Multibanco Reference generation using these forms. Understanding these forms is essential to correctly execute operations in the Virtual Terminal, as incorrect or incomplete data directly impacts transaction processing and transaction reconciliation. Common Fields (All Payment Methods) The following fields are present across all payment methods and operations. Payment Method Block Payment Information Block Customer Block (Optional) These fields enrich the transaction context and may support operational or reconciliation processes. Billing Address Block (Optional) These fields are optional and […]

Overview This section describes how to access and navigate to the Virtual Terminal (vTerminal) within the SIBS Backoffice. This section describes the operational access flow used to execute manual payment operations within the vTerminal environment, including MB WAY Payments, Multibanco Reference, and MB WAY Authorized Payment operations. 1. Backoffice Access The user starts from the SIBS Backoffice main interface after successful authentication. 2. Navigation to vTerminal From the main Backoffice interface: This action opens the vTerminal module. 3. Opening the vTerminal Once inside the vTerminal module: At this stage: 4. Initial Interaction Considerations When accessing the vTerminal: Summary Accessing the vTerminal consists of: This establishes the operational entry point for the manual payment procedures and operational workflows described in the following vTerminal sections of this documentation.

Overview The Virtual Terminal (vTerminal) is a functionality available in the SIBS Backoffice that allows users to manually execute payment operations through a web-based interface. It is designed for operational use, enabling transactions to be created directly through the SIBS Backoffice interface as part of the SPG operational environment. Through the vTerminal, users can initiate supported operations such as MB WAY Purchase, MB WAY Authorization (Mandate Creation), and Multibanco Reference generation by completing and submitting the corresponding form. vTerminal Configuration Before using the vTerminal, the merchant environment must be appropriately configured in the SIBS Backoffice for the payment operations to be performed. Depending on the merchant configuration and the payment operation, this configuration may include: The services and payment methods available in the vTerminal depend on the configuration enabled for the merchant account. Video Tutorial – Configuring the vTerminal The following video provides a practical walkthrough of the initial configuration associated with the vTerminal in the SIBS Backoffice. Video – Configuring the vTerminal Functional Description The vTerminal operates as a form-based transaction tool, where each submitted form corresponds to a single operation. Users access the vTerminal from the Backoffice and, depending on the configuration, may be required to select a […]

Overview The vTerminal is a functionality available within the SIBS Backoffice that allows Merchants and operational users to perform payment-related operations manually. It provides a set of forms through which transactions can be manually created and processed through the Backoffice interface. Each operation performed through the vTerminal results in the creation and processing of a transaction within the SIBS Payment Gateway environment. Purpose The vTerminal is intended to support operational scenarios requiring direct transaction initiation through the Backoffice interface. It enables Merchants and operational users to perform payment-related operations manually within the SPG environment, supporting operational workflows, assisted transactions, and administrative payment procedures. Access and Availability The vTerminal is accessible through the SIBS Backoffice, and its availability depends on the services configured for the Merchant account and the permissions associated with the user profile. Only users with the appropriate permissions can access and use the vTerminal functionalities. Operation Model The vTerminal operates through the completion of forms corresponding to specific payment operations. Each form represents a single transaction and requires the input of the necessary data for the execution of that operation. The submission of a form results in the creation of a transaction in the SIBS Payment Gateway, which […]

Overview The Common Interface Features described in this chapter are shared across multiple areas of the SIBS Backoffice. Rather than being specific to a particular module or payment service, these features provide a consistent user experience when navigating, organizing, and exporting tabular information displayed throughout the platform. Depending on the operational area being used, these common interface capabilities allow users to: These interface features behave consistently across the various Backoffice modules, allowing users to work efficiently with operational information regardless of the functional area being accessed. Pagination Many Backoffice pages display information in tabular format. When the number of available records exceeds the number of items configured for a page, the Backoffice automatically organizes the information into multiple pages. The Items per page option allows users to select how many records are displayed on each page. The available options are: Figure 1 – Setting the Number of Items per Page When the total number of records exceeds the selected page size, pagination controls are displayed below the table, allowing users to navigate through the available pages. Figure 2 – Example of Pagination The SIBS Backoffice loads records in blocks of 50 items. When additional records are available, users must navigate […]