Skip to main content

Maestro

Features
MethodDebit Card, Sync
Merchant countriesEurope
Consumer countriesEurope
Processing currenciesAll *
Increments✅
Captures✅
Partial/Multiple partial captures⚠️ (Only one partial capture is supported)
Cancels✅
Partial/Multiple partial cancels⚠️ (Only one partial cancel is supported)
Refunds✅
Partial/Multiple partial refunds✅
Recurring✅
Installments-
Credits-
Disputes✅
Min AmountN/A
Account verification✅
note

* Currencies with 0, 2, and 3 decimal places are supported. For currencies with 3 decimal places, the last digit of the amount must be zero; that is, the amount must be rounded to two decimal places.

Maestro cards (part of the Mastercard scheme) are widely accepted in e-commerce and physical environments. Card tokenization and consumer authentication (via the 3-D Secure protocol) improve the consumer experience and security of payments.

Strong customer authentication (SCA) exemptions​

The following SCA exemptions are supported:

  • delegated_authentication
  • low_value
  • secure_corporate
  • transaction_risk_analysis

Account verification (Zero auth)​

An account verification is an authorization request with an amount of 0.

Auto-cancellation​

Card schemes require a period of time within which the authorized amount must be captured. This period can vary depending on the Merchant Category Code (MCC), but is typically 30 days for Maestro. Automatic cancellation is not currently being performed for Maestro authorizations. Merchants are responsible for cancelling authorizations that remain uncaptured within the applicable period.

Scheme transaction reference​

Maestro supports two ways to link a merchant initiated transaction (MIT) to the initial cardholder transaction:

  • schemeTransactionId — the existing scheme transaction ID, returned in paymentMethod.scheme.transactionId.
  • schemeTransactionLinkId — the new Transaction Link Identifier (TLID), returned in paymentMethod.scheme.transactionLinkId.

For subsequent MITs, send the relevant identifier in the corresponding request field.

Payment flow​

Card flow

Payment​

Request​
{
"processingAccountId": "2HdN2jq6XWmlkhqRC2gDTNYCvNH",
"merchantReference": "B2A8734D-9450-4915-A63D-FE5C21F09550",
"amount": {
"value": 200,
"currency": "eur"
},
"paymentMethod": {
"type": "maestro",
"maestro": {
"account": {
"number": "6703444444444449",
"expiryMonth": "1",
"expiryYear": "2030",
"cvv": "333"
},
"capture": "manual",
"threedsPassThrough": {
"version": "2.1.0",
"eci": "02",
"transactionId": "fe7ecca3-3082-483c-880e-a06a3cf94545",
"authenticationValue": "kBGgt+19mPklgPfl9DQ9KWjOyBY="
}
}
}
}
Response​
{
"id": "2RkJWSysl7k2IsOUCGje1fnkhmg",
"merchantReference": "B2A8734D-9450-4915-A63D-FE5C21F09550",
"status": "succeeded",
"paymentMethod": {
"type": "maestro",
"scheme": {
"approvalCode": "11DCB0",
"cvvResult": "M",
"transactionId": "MCC792D1C0626",
"transactionLinkId": "A1B2C3D4E5F6G7H8I9J0K1L2M3N4O5P6Q7"
}
}
}