[THK] B. Integration Flows – Plugin Integrations [Common Configuration]

This section describes configuration steps shared across all SIBS plugins, regardless of the platform.

These settings ensure secure communication with SIBS SPG and proper order lifecycle handling.

All plugins require authentication parameters provided during onboarding.

Terminal ID : Identifies the merchant terminal within SPG.
Client ID : Used for API authentication and request validation.
Authentication Token : Bearer token used for secure communication with SPG services.

Plugins support two environments:

Sandbox

Production

Always validate the integration in Sandbox before switching to Production.

SIBS plugins rely on asynchronous notifications to update order states.

These notifications ensure:

The plugin automatically processes notifications and updates the order lifecycle.

No manual webhook implementation is required.

Depending on the payment method, orders may transition through multiple states.

Typical lifecycle: Pending → Processing → Completed

For asynchronous methods (e.g., MB WAY, Multibanco): Pending → Awaiting Payment → Paid / Expired

Plugins handle transitions automatically.

Troubleshooting capabilities depend on the platform-specific plugin implementation.

If you encounter issues during integration:

Some platforms may provide additional diagnostic tooling depending on the plugin version.

Transactions created via plugins are processed through the SIBS Payment Gateway infrastructure.

As a result, transaction lifecycle management (status tracking, reporting, reconciliation) is handled through standard SPG channels, such as:

The exact visibility of transactions inside the e-commerce platform depends on the plugin implementation.