MB WAY is a mobile-based payment method that allows customers to authorize payments directly through the MB WAY application linked to their bank account or card.

In a one-off payment scenario, the transaction is initiated and completed in a single step. The payment is immediately authorized and captured upon customer confirmation, without requiring a separate settlement action by the merchant.

How It Works

In a typical MB WAY one-off payment flow:

1. The merchant initiates a payment request through the SIBS Payment Gateway.
2. The customer provides their mobile phone number associated with MB WAY.
3. A payment authorization request is sent to the customer’s MB WAY app.
4. The customer confirms the transaction within the app.
5. Upon confirmation, the payment is immediately authorized and captured.
6. The transaction result is returned to the merchant system, potentially followed by asynchronous lifecycle updates.

The customer interaction is mandatory, and payment completion depends on real-time user approval.

If the customer rejects the authorization request or does not interact with the MB WAY application within the allowed timeframe, the transaction will not be completed successfully.

Workflow Characteristics

The MB WAY one-off flow has the following characteristics:

• Customer-initiated payment
• Real-time confirmation
• Authorization and capture occur within the same operational flow
• No separate authorization and capture steps
• Synchronous response with possible asynchronous status updates

Merchants should ensure that expired or abandoned payment attempts are handled correctly in the merchant application flow to avoid inconsistent order states or duplicate payment attempts.

Although MB WAY transactions are typically completed in near real-time, merchants should implement webhook processing and, where needed, Status Inquiry mechanisms to support reliable final-state handling, operational reconciliation, and asynchronous payment lifecycle monitoring.

The SPG transactionID should be treated as the authoritative identifier for transaction monitoring, webhook correlation, reconciliation, refund operations, and Status Inquiry requests throughout the transaction lifecycle.

Transaction Lifecycle

The following diagram illustrates the operational lifecycle of an MB WAY one-off payment within the SIBS Payment Gateway, including customer confirmation, transaction processing, asynchronous status monitoring, final-state notifications, and merchant reconciliation flows.

The lifecycle of an MB WAY one-off payment typically includes:

• Payment creation
• Pending customer confirmation and asynchronous transaction progression
• Successfully authorized and captured
• Declined, Error, or Timeout outcomes

Once successfully confirmed, the transaction is considered completed and settlement is performed according to the merchant’s operational agreement with the financial partner.

Use Cases

MB WAY one-off payments are commonly used in:

• E-commerce checkout flows
• Mobile applications
• Digital services with immediate activation
• Ticketing and event purchases

This payment method is particularly suited for environments where:

• Customers expect fast mobile authorization
• Strong customer authentication is required
• Immediate confirmation of payment is necessary

For transaction lifecycle monitoring, reconciliation, and Status Inquiry usage, refer to E.2 – Status Inquiry / Get Status.

For webhook delivery and asynchronous transaction notifications, refer to E.1 – Webhooks (Notifications).

Practical implementation examples, Postman collections, MB WAY payment scenarios, and integration examples are documented in F. Technical Examples and Best Practices.

The Sandbox Payment Simulator may also be used to validate MB WAY customer confirmation behavior, transaction lifecycle progression, and operational request/response payloads in the sandbox environment.

Example sandbox simulator entry point

Particularities in the SIBS Context

When working with MB WAY one-off payments in SIBS SPG, several platform-specific aspects should be considered:

• Customer interaction through the MB WAY mobile application is mandatory
• Payment confirmation depends on real-time customer approval
• Transaction expiration handling must be implemented correctly
• Webhook notifications should be implemented for reliable lifecycle monitoring, with Status Inquiry used where needed for monitoring, recovery, or reconciliation
• Mobile phone number validation and formatting should be handled consistently
• Temporary pending states may occur before final transaction confirmation
• Proper transaction lifecycle monitoring is critical to guarantee operational consistency and accurate reconciliation.

Integration Context

Within the SIBS Payment Gateway, MB WAY is supported under the one-off payment model, meaning that authorization and capture occur in a single operation.

The following sections describe the technical integration flow, required parameters, and notification handling for MB WAY payments.