MB WAY is the leading e-wallet in Portugal, with over 5 million users. The user base continues to grow steadily each quarter, and now 50% of Portuguese bank customers are using MB WAY. Learn more about MB WAY.

Payment method properties


Markets (consumer)	`PT`
Processing currencies	`EUR`
Consumer currencies	`EUR`
Authentication methods	`REDIRECT` `APP_NOTIFICATION`
Authentication timeout	1 hour
Minimum payment amount	0.01 EUR
Maximum payment amount	10,000.00 EUR
Payment instrument	`PASSTHROUGH_WALLET`
Recurring payments	No
Separate captures	No
Refund	Full - Partial - Multiple
Refund validity	120 days
Disputes	Yes
Settlement risk	No

Make an MB WAY payment

MB WAY payments follow our standardized REDIRECTand APP_NOTIFICATIONpayment flows. Enabling you to offer a seamless desktop or mobile handoff experience. We recommend including all relevant settings for any authentication methods you support.

To create an MB WAY payment, you'll need to provide the following data at minimum when calling our payment charges endpoint:

Field	Description
`paymentMethod`	`MBWAY`
`amount.value`	The amount to be paid in the smallest units of the currency used.
`amount.currency`	`EUR`
`consumer.country`	The country of residence of the consumer.
authenticationSettings: REDIRECT `settings.returnUrl`	Specify the URL to which the consumer should be redirected after completing the payment. This is required for the `REDIRECT` payment flow.

📘
Guidance
To improve the consumer experience and payment traceability, consider including the following fields. See the API Reference for full details.
Fields Description
paymentDescriptor A short descriptor that appears on the page during payment.

Fields	Description
`paymentDescriptor`	A short descriptor that appears on the page during payment.

Request

POST /v1/payment-charges

{
  "paymentMethod": "MBWAY",
  "amount": {
    "value": 1000,
    "currency": "EUR"
  },
  "consumer": {
    "country": "PT"
  },
  "authenticationSettings": [
    {
      "type": "REDIRECT",
      "settings": {
        "returnUrl": "https://www.webshop.com/order-results-page"
      }
    }
  ]
}

Response

You'll receive our standard payment charge response:

{
  "id": "charge_Y3JVzvEaJpvG53xd2R2Zt",
  "paymentMethod": "MBWAY",
  "paymentMedium": "ECOMMERCE",
  "scheduleType": "UNSCHEDULED",
  "instrumentId": "instr_Asu0ig2PXXZSiNrhY44A5",
  "currency": "EUR",
  "country": "PT",
  "status": "AUTHENTICATION_PENDING",
  "consumer": {
    "country": "PT"
  },
"authenticationMethods": [
    {
      "details": {
        "requestUrl": "https://redirection-target.ppro.com",
        "requestMethod": "GET"
      },
      "type": "REDIRECT"
    },
		{
      "type": "APP_NOTIFICATION"
    }
  ],
  "authorizations": [
    {
      "id": "authz_aPobet0FNZNU1bYqfexFd",
      "amount": 1000,
      "status": "AUTHENTICATION_PENDING",
      "createdAt": "2025-12-21T08:34:20.766Z",
      "updatedAt": "2025-12-21T08:34:20.766Z"
    }
  ],
  "captures": [],
  "refunds": [],
  "discards": [],
  "voids": [],
  "createdAt": "2025-12-21T08:34:20.114Z",
  "updatedAt": "2025-12-21T08:34:20.766Z",
  "_links": {
    "authorizations": {
      "href": "/v1/payment-charges/charge_Y3JVzvEaJpvG53xd2R2Zt/authorizations"
    },
    "captures": {
      "href": "/v1/payment-charges/charge_Y3JVzvEaJpvG53xd2R2Zt/captures"
    },
    "refunds": {
      "href": "/v1/payment-charges/charge_Y3JVzvEaJpvG53xd2R2Zt/refunds"
    },
    "discards": {
      "href": "/v1/payment-charges/charge_Y3JVzvEaJpvG53xd2R2Zt/discards"
    },
    "voids": {
      "href": "/v1/payment-charges/charge_Y3JVzvEaJpvG53xd2R2Zt/voids"
    }
  }
}

Pick the desired authentication method

REDIRECT

Redirect your consumer to the returned $.authenticationMethods[?(@.type == "REDIRECT")].details.requestUrl.
For example, with the value of https://redirection-target.ppro.com/ using the returned $.authenticationMethods[?(@.type == "REDIRECT")].details.requestMethod HTTP method.

APP_NOTIFICATION

Ask your consumer for the required identifier needed to initiate the push notification, often a phone or bank account number. For MBWAY payments, provide the consumer's phone number.
Issue the following request to POST /v1/payment-charges/{paymentChargeId}/authorizations

Request

{
  "authenticationResult": {
    "type": "APP_NOTIFICATION",
    "details": {
      "instrumentProviderIdentity": "+35100000000"
    }
  }
}

Response

{
    "id": "authz_DnmPEl6S51dS5NpyWqmGx",
    "amount": 1000,
    "status": "AUTHENTICATION_PENDING",
    "createdAt": "2025-12-28T07:42:48.450Z",
    "updatedAt": "2025-12-28T07:42:48.450Z",
    "_links": {
        "payment_charge": {
            "href": "/v1/payment-charges/charge_6vdN6WlenwhuDZNaPCVqG"
        }
    }
}

The consumer will receive a push notification to complete the payment process.

Handling the payment result

REDIRECT

After the consumer completes the payment, they are redirected to the returnUrl specified in the payment charge creation request.
Upon redirect back to your site, retrieve the latest payment status by performing a GET /v1/payment-charges/{paymentChargeId}. Use the returned status field to determine and display the final payment outcome to the consumer.
Additionally, webhooks are triggered to notify you of the payment result. This ensures you receive the outcome even if the consumer closes their browser or fails to return to your website.

APP_NOTIFICATION

The payment charge will remain in the AUTHENTICATION_PENDING state until the consumer confirms the payment.
Webhooks are sent to inform you of the payment outcome.
Alternatively, check the payment status by making a GET /v1/payment-charges/{paymentChargeId}. Use the Status that you received to display the payment outcome to the consumer.

Payment instrument

A PASSTHROUGH_WALLET instrument will be created for MBWAY, with no additional data provided.

Request

GET /v1/payment-instruments/{instrument-id}

Response

{
    "id": "instr_Asu0ig2PXXZSiNrhY44A5",
    "type": "PASSTHROUGH_WALLET"
}

Sandbox testing

MB Way uses PPRO's mock authenticator in sandbox. Learn more.