MBWay
ID: mbway-eupago | Provider: Eupago | Region: Portugal
Overview
Portuguese mobile payment solution. The customer receives a push notification on their MBWay app to approve the payment.
paymentMethod Fields
| Field | Required | Description |
|---|---|---|
id |
yes | Must be mbway-eupago |
phone |
yes | Customer's mobile number in Portuguese E.164 format (+351XXXXXXXXX) |
No extra customer fields are required beyond customer.id.
Request Example
{
"paymentMethod": {
"id": "mbway-eupago",
"phone": "+351912345678"
},
"reference": "ORDER-12345",
"customer": {
"id": "cust_abc123",
"phone": "+351912345678"
},
"amount": "50.00",
"currency": "EUR",
"returnLinks": {
"default": "https://yourproduct.com/return",
"cancel": "https://yourproduct.com/cancel"
}
}
Response Action
MBWay uses a requisites action. The requisites object only contains a reference - the payment amount is already on the intent and is not duplicated here.
{
"type": "requisites",
"requisites": {
"reference": "123 456 789"
},
"expiresAt": "2025-11-18T15:30:00.000+00:00"
}
Display the reference to the customer; they will also receive a push notification on their MBWay app to approve the payment against that reference.
Status Flow
requires_action- reference issued, waiting for the customer to approve in the MBWay app.processing- Eupago is confirming the payment.succeeded- payment captured. Fulfill the order.canceled- the customer did not approve beforeexpiresAt.