Payment-method icon

MB WAY Drop-in integration

Add MB WAY to an existing Drop-in integration

This page explains how to add MB WAY to your existing Web Drop-in integration.

Requirements

Requirement Description
Integration type Make sure that you have built your Web Drop-in integration.
Setup steps Before you begin, add MB WAY in your test Customer Area.

Import resources for v6

If you are using Web Drop-in v6, import the resources you need for MB WAY:

Copy code
import { AdyenCheckout, MBWay} from '@adyen/adyen-web'

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

API reference

Include fields for the endpoint you integrated:

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

/sessions request
Expand view
Copy link to code block
Copy code
Copy code
curl https://checkout-test.adyen.com/v70/sessions \
-H 'x-api-key: ADYEN_API_KEY' \
-H 'content-type: application/json' \
-d '{
"merchantAccount": "YOUR_MERCHANT_ACCOUNT",
"reference": "YOUR_ORDER_REFERENCE",
"amount": {
"currency": "EUR",
"value": 1000
},
"returnUrl": "https://your-company.com/checkout?shopperOrder=12xy.."
"shopperStatement": "MB WAY shopper statement"
}'

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"

See also