MPGS — Mastercard Payment Gateway Services

Status: Active (solutions.yaml: solution 0006, status=active) Integration type: SPF (Single-Pass Framework)

Author required. The narrative overview of MPGS as a gateway has not been written. This section should explain: what MPGS is, why Astral uses it, what property types and regions it is deployed in, and any operational notes relevant to integration engineers. Source: conversations with the MPGS integration owner.

Quick Reference

Property Value
Gateway MPGS (Mastercard Payment Gateway Services)
Integration SPF — Single-Pass Framework
Solution IDs 0006 (active)
Payment Methods PM0 Bank Card, PM1 Token, PM4 Ecommerce
MPG Entries per Merchant 5 (PM0×1, PM1×2, PM4×2)
3DS / MPI Not confirmed — see Open Items
Status Active

How MPGS Fits into the Platform

SKU (e.g. C2C-ALL-0006-A-010010)
        ↓
    Solution 0006 → MPGS SPF
        ↓
    Merchant in MGMT
        ↓ ↓ ↓ ↓ ↓
  [PM0]  [PM1 sync] [PM1 async] [PM4 widget] [PM4 processing]
    ↓         ↓           ↓           ↓              ↓
  Sync      Sync        Async     HPP (browser)  Async (back-end)
 channel   channel    channel       channel        channel

Each channel routes to a different MPGS processing path. This is why MPGS provisioning requires five MPG entries — not because it is complex, but because different payment types use fundamentally different routing paths.

SKUs Using MPGS

SKU Industry Capability
FNB-ALL-0006-A-110000 Food & Beverage PM0 + PM1
C2C-ALL-0006-A-010010 C2C Ecommerce PM1 + PM4

In This Section

Page What it covers
Merchant Configuration Group and Merchant MGMT objects — identity, region, currency, credentials
Terminal Configuration Terminal and TerminalConfig objects — channel routing, async flag
MerchantPaymentGateway Configuration The five MPG entries — why they exist and how to configure each
Tokenisation STS token space, repository, and API user setup
Supported Transaction Types Which transaction types MPGS supports per payment method
Field Catalog Complete field reference with types, constraints, and sources

Author required. The following sections have not been written: Examples, Troubleshooting, FAQ.

See Also