If you are using Android Drop-in v5.0.0 or later:
This payment method requires no additional configuration.
Follow the Drop-in integration guide.
This page explains how to add MB WAY to your existing Android Drop-in integration.
Requirements
| Requirement | Description |
|---|---|
| Integration type | Make sure that you have built an Advanced flow Android Drop-in integration. |
| Setup steps | Before you begin, add MB WAY in your Customer Area. |
MB WAY is supported as of Drop-in version 3.7.0. For more information, refer to Release notes.
API reference
You do not need to send additional fields for MB WAY. To see optional fields that you can send for all payment methods, see /payments.
Drop-in configuration
There are no configuration steps specific to MB WAY required for Drop-in.
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 |
|---|---|
| Authorised (default test response) |
-c1 |
| Pending | -c3 |
| Refused | -c5 |
For example, to receive resultCode: Refused, include the following in your /payments request: "shopperStatement": "MBWay shopper statement-c5"