MB WAY Authorized Payments allow merchants to charge a customer multiple times after the customer grants prior authorization within the MB WAY application.

In a recurring payment scenario, the customer explicitly authorizes the merchant to perform future charges. Once the authorization is granted, subsequent payments can be initiated by the merchant without requiring customer interaction for each transaction.

This model is commonly used in subscription services, memberships, installment plans, and recurring billing arrangements within the MB WAY ecosystem.

How It Works

In a typical MB WAY Authorized Payments flow:

1. The merchant initiates an authorization request through the SIBS Payment Gateway.
2. The customer provides their mobile phone number associated with MB WAY.
3. An authorization request is sent to the customer’s MB WAY app.
4. The customer approves the recurring authorization within the app.
5. Upon approval, an authorization reference (mandate) is created.
6. The merchant stores the authorization reference securely.
7. Future recurring charges are initiated by the merchant using the stored authorization reference.
8. Each recurring transaction is processed through the MB WAY network.
9. The final transaction result is returned to the merchant system.

The customer interaction is required only during the authorization setup phase. Subsequent recurring charges are merchant-initiated.

Workflow Characteristics

The MB WAY Authorized Payments flow has the following characteristics:

• Explicit customer consent during setup
• Mobile-based authorization process
• Authorization reference generation (mandate-based model)
• Merchant-initiated recurring transactions
• Real-time response for each recurring charge
• No repeated customer confirmation per transaction (after authorization)

Recurring authorizations may be subject to limits, expiration, or customer revocation.

Transaction Lifecycle

The lifecycle of an MB WAY Authorized Payment typically includes:

• Authorization request
• Customer approval in MB WAY app
• Authorization reference creation
• Merchant-initiated recurring charge
• Authorized and captured (successful)
• Declined or revoked (if authorization is canceled or invalid)

If the customer revokes authorization or the mandate expires, further recurring charges will not succeed.

Use Cases

MB WAY Authorized Payments are commonly used in:

• Subscription-based digital services
• Membership platforms
• Installment plans
• Educational or institutional recurring fees
• Donation and contribution programs

This payment method is particularly suited for environments where:

• Customers prefer mobile-first payment experiences
• Strong customer authentication is required during setup
• Frictionless recurring payments are desired after initial consent
• Recurring billing is limited to the Portuguese market

Integration Context

Within the SIBS Payment Gateway, MB WAY Authorized Payments are implemented through:

• An initial authorization request (customer approval required)
• Authorization reference generation
• Server-to-server merchant-initiated recurring transactions

Each recurring charge is processed independently and returns its own transaction status.

Merchants should implement proper handling for:

• Authorization revocation
• Authorization suspension
• Authorization expiration
• Failed recurring charges
• Customer mandate cancellation scenarios

The following sections describe the technical integration flow, required parameters, authorization handling, and recurring charge execution for MB WAY Authorized Payments.