Payment-method icon

MB WAY Component

Add MB WAY to an existing Components integration.

On this page, you can find additional configuration for adding MB WAY to your Components integration.

Before you begin

This page assumes you have already:

MB WAY is supported as of Components version 3.7.0. For more information, refer to Release notes.

API reference

Include fields for the endpoint you integrated:

You must include the following additional field when making a /sessions request with MB WAY:

Parameter name Required Description
paymentMethod.telephoneNumber -white_check_mark- The shopper's mobile phone number.

For a full list of optional fields that you can send for all payment methods, see /sessions.

Component configuration

v5.0.0 or later

If your integration uses iOS Components v5.0.0 or later, configure and create an instance of the MB WAY Component:


If your integration uses an earlier version of iOS Components:

There are no configuration steps specific to MB WAY required for Components.

Test and go live

To test your MB WAY integration, you can use any telephone number; for example +351234567890.

You can check the status of MB WAY test payments in your Customer Area > Transactions > Payments.

Before you can accept live MB WAY payments, add MB WAY in your live Customer Area.

Trigger a resultCode

To trigger a specific resultCode value, append a code to the shopperStatement value in your /payments request:

resultCode Code to append to shopperStatement
(default test response)
Pending -c3
Refused -c5

For example, to receive resultCode: Refused, include the following in your /payments request: "shopperStatement": "MBWay shopper statement-c5"

See also