MB WAY via Checkout.com

Accept MB WAY payments from customers in Portugal with Checkout.com as the payment service provider (PSP). The customer approves each payment in the MB WAY app, and Checkout.com sends the result to Payrails as a webhook notification.

Supported workflows

Before you begin

Complete these steps before you send your first MB WAY payment through Checkout.com:

Set up a Checkout.com integration in your workspace. Follow the Checkout.com integration setup guide if you don’t have one yet.
Ask Checkout.com support to enable MB WAY on your Checkout.com account.
In the Payrails Portal, go to Settings → Integrations, open your Checkout.com integration, select MB WAY under Payment methods, and save.
Optional: turn on Direct under MB WAY in the same integration to use the direct flow. Leave it off to use the payment setup flow.
Add MB WAY as a payment option in your workflow.

Choose a flow

Payrails processes MB WAY through Checkout.com in one of two flows, set by the Direct option on your integration:

Payment setup flow (default): Payrails uses the Checkout.com Payment Setup API. If Checkout.com returns a redirect to a Checkout.com-hosted page, Payrails passes it on. Otherwise, the payment stays pending until the customer approves it in the app.
Direct flow: Payrails uses the Checkout.com payments API. The customer stays on your checkout and approves in the app, and the response includes a wait action instead of a redirect. The Payrails SDK collects the phone number through payer fields when the amount is in EUR or isn’t known yet.

Request fields for Checkout.com

Send these fields in the authorize request, in addition to the standard authorize fields. Payrails checks Required fields and returns an error when one is missing. Fields required by the PSP pass the Payrails checks but the PSP can decline the payment without them. Send the phone number either as payer fields or in meta.customer.phone. Payrails uses the payer fields when they carry a phone number.

Field	Status	Description
`paymentComposition[].paymentInstrumentData.payerFields.phoneCountryCode`	Required with payer fields	The dialing code of the customer’s phone, digits only, for example `351`.
`paymentComposition[].paymentInstrumentData.payerFields.phoneNumber`	Required with payer fields	The customer’s mobile number without the dialing code. Six to nine digits.
`meta.customer.phone.number`	Required without payer fields	The customer’s mobile number without the dialing code.
`meta.customer.phone.countryCode`	Required without payer fields	The dialing code of the customer’s phone, for example `351`.
`meta.customer.name`, `meta.customer.lastName`	Optional	Sent to Checkout.com as the customer name.
`meta.customer.email`	Optional	Sent to Checkout.com as the customer email.

Authorize an MB WAY payment

Call authorize a payment with mbWay as the paymentMethodCode.

Authorize request

{
  "amount": {
    "value": "25.00",
    "currency": "EUR"
  },
  "paymentComposition": [
    {
      "integrationType": "api",
      "paymentMethodCode": "mbWay",
      "amount": {
        "value": "25.00",
        "currency": "EUR"
      },
      "paymentInstrumentData": {
        "payerFields": {
          "phoneCountryCode": "351",
          "phoneNumber": "912345678"
        }
      }
    }
  ],
  "meta": {
    "customer": {
      "email": "ines.costa@example.com",
      "name": "Inês",
      "lastName": "Costa"
    }
  },
  "returnInfo": {
    "success": "https://example.com/success",
    "error": "https://example.com/error"
  }
}

The payment stays pending until the customer approves it in the MB WAY app. Confirm the result through webhook notifications or the execution status before you fulfill the order.

How Checkout.com handles MB WAY

Payrails checks the phone number before it calls Checkout.com, and sends it to Checkout.com on the customer.
In the direct flow, the wait action gives the client a 15-minute window to poll for the result.
Checkout.com sends the final result as a webhook notification after the customer approves or declines in the app.
Payrails doesn’t save the MB WAY payment method at Checkout.com, so Save Instruments and MIT aren’t available.

Getting Started

Payment Orchestration

Token Vault

Analytics & Reporting

Fraud Management

Chargebacks

Monitoring

Resources

Use Cases

Supported workflows

Before you begin

Choose a flow

Request fields for Checkout.com

Authorize an MB WAY payment

How Checkout.com handles MB WAY

​Supported workflows

​Before you begin

​Choose a flow

​Request fields for Checkout.com

​Authorize an MB WAY payment

​How Checkout.com handles MB WAY

Supported workflows

Before you begin

Choose a flow

Request fields for Checkout.com

Authorize an MB WAY payment

How Checkout.com handles MB WAY