On this page, you can find additional configuration for adding MB WAY to your Drop-in integration.
Before you begin
This page assumes you have already:
API reference
You don't need to send additional fields for MB WAY. To see optional fields that you can send for all payment methods, choose the endpoint you integrated:
- /sessions: This is the default with Drop-in v5.0.0 or later.
- /payments: If you implemented an additional use case.
Drop-in configuration
There is no required MB WAY specific integration for Drop-in.
Test and go live
To test your MB WAY integration, you can use any telephone number, for example +351234567890.
You can trigger a specific resultCode value by appending a code to the shopperStatement value in your /payments request:
resultCode |
Code to append to shopperStatement |
|---|---|
| Authorised default test response |
-c1 |
| Pending | -c3 and wait 15 minutes after making the /payments request |
| Refused | -c5 |
For example, to receive resultCode: Refused, include the following in your /payments request:
{
// Produce a REFUSED payment result.
"shopperStatement": "MBWay shopper statement-c5"
}You can check the status of MB WAY test payments in your Customer Area > Transactions > Payments.
Before you can accept live MB WAY payments, you need to add MB WAY in your live Customer Area.