Supported Transaction Types — MPGS

Generated page — source of truth is capabilities/mpgs.yaml. Do not edit this file directly.

Overview

MPGS (Mastercard Payment Gateway Services) supports a range of transaction types across card-present, token MOTO, and ecommerce payment methods. Not all transaction types are available to every merchant — the active SKU determines which payment methods (PM slots) are provisioned, and only provisioned payment methods can process transactions.

For example, a merchant provisioned with PM4 (Ecommerce) can process Authorization and Sale via the HPP, but Tip Adjust is not supported for any payment method on MPGS.

Payment Methods

MPGS supports three payment method slots:

PM Slot	Name	Description
PM0	Bank Card	Card-present transactions through a physical terminal
PM1	Token	Tokenised MOTO or card-on-file transactions
PM4	Ecommerce	Browser-based payments via the MPGS hosted payment page

See Payment Methods Reference for an explanation of PM slots, the capability bitmap, and how they map to MPG array entries.

Transaction Type Support Matrix

Source: capabilities/mpgs.yaml

Code	Transaction Type	PM0 Card Present	PM1 Token	PM4 Ecommerce
01	Authorization	✅	✅	✅
04	Sale	✅	✅	✅
05	Tip Adjust	❌	❌	❌
07	Void Auth	✅	✅	—
10	Refund	✅	✅	✅
11	Capture	✅	✅	✅

Notes: - Tip Adjust is not supported on MPGS. Confirm with the MPGS integration owner before quoting this to customers. - Void Auth is not applicable to ecommerce (PM4) — ecom transactions use capture/refund rather than void.

Capabilities

Beyond individual transaction types, MPGS supports the following platform-level capabilities:

Capability	Supported	Notes
Partial Authorisations	✅	Controlled via `terminalConfig.extData1` (`partial_auth`). When `true`, the gateway may approve a lower amount than requested.
Async Processing	✅	PM1 async entry + PM4 ecom processing use async channel routing (`asyncFlag=1` on terminalConfig). See Terminal Configuration.
Ecom HPP (Widget)	✅	PM4 ecom widget — hosted payment page served by MPGS. No host credentials required at MPG layer. See MPG Configuration.
Card BIN Routing	✅	`extData10` on PM4 ecom processing entry. Pipe-separated BIN range rules route transactions to the correct card network.
3DS / MPI	⚠️ UNCONFIRMED	Not present in the UAT template. Confirm with the MPGS integration owner. See OI in Open Items.
DCC	⚠️ UNCONFIRMED	Confirm with integration owner.
Tipping	⚠️ UNCONFIRMED	Confirm with integration owner.

Which Transaction Types Apply to My SKU?

The industry associated with a SKU defines its expected transaction profile. For example, a C2C Ecommerce SKU expects Auth, Capture, Sale, Void, and Refund flows. A FNB SKU additionally expects Top-Up.

See the specific SKU page for the transaction types applicable to that product:

Open Items

#	Item
OI (capabilities)	3DS / MPI support not confirmed for MPGS
OI (capabilities)	DCC support not confirmed
OI (capabilities)	Tip Adjust — confirmed unsupported, but confirmation source not documented