FNB-ALL-0006-A-110000
Status: In Development
Applies To: Gateway=MPGS | Integration=SPF | Solution=0006-A | Variant=A | Industry=FNB
Source files: schema/mpgs.yaml · capabilities/mpgs.yaml · data/industries.yaml
Prerequisites: Payment Methods Reference · SKU Naming Convention · MPGS Overview
1. What Is This Product?
FNB-ALL-0006-A-110000 is the Food & Beverage (Infrasys Complex) product using MPGS SPF integration. It provisions card-present and tokenised MOTO payment flows for F&B merchants using Infrasys as the point-of-sale system.
Active payment methods: PM0 (Bank Card / Card Present) and PM1 (Token). There is no ecommerce channel in this product — PM4 is absent from the bitmap.
The FNB transaction profile includes Top-Up in addition to the standard Auth → Capture → Sale → Void → Refund flows, reflecting F&B-specific business requirements such as topping up prepaid dining credits.
⚠️ Transaction flows are SEED values sourced from
data/industries.yaml. Confirm with the MPGS integration owner before quoting to customers.
2. SKU Breakdown
| Position | Value | Meaning | Reference |
|---|---|---|---|
| Industry | FNB |
Food & Beverage (Infrasys Complex) | Industry Codes |
| Region | ALL |
All regions (global) | Region Codes |
| Solution | 0006 |
MPGS SPF solution | Solution IDs |
| Variant | A |
Variant A (baseline) | SKU Naming |
| Bitmap | 110000 |
PM0 + PM1 active | Payment Methods |
Bitmap decoded:
| Position | PM Slot | Name | Active |
|---|---|---|---|
| 1 | PM0 | Bank Card (Card Present) | ✅ |
| 2 | PM1 | Token (MOTO / card-on-file) | ✅ |
| 3 | PM2 | QR MS | ❌ |
| 4 | PM3 | QR GS | ❌ |
| 5 | PM4 | Ecommerce | ❌ |
| 6 | PM5 | Gift | ❌ |
3. How This SKU Fits Into the Platform
Industry: FNB (Food & Beverage — Infrasys Complex)
└── Solution: 0006 (MPGS SPF)
└── Gateway: MPGS (Mastercard Payment Gateway Services)
└── Variant: A
└── Bitmap: 110000
├── PM0 → bank_card entry (card-present via terminal)
└── PM1 → token_sync entry (defaultFlag=1, asyncFlag=0)
└── token_async entry (defaultFlag=0, asyncFlag=1)
This SKU serves F&B merchants with physical POS terminals (PM0) and card-on-file or MOTO capabilities (PM1). The absence of PM4 means there is no Hosted Payment Page and no browser-based checkout — all transactions originate from the physical or integrated terminal environment.
4. Supported Transaction Types
Source:
capabilities/mpgs.yaml+data/industries.yaml(SEED)
| Transaction | PM0 Card Present | PM1 Token | Notes |
|---|---|---|---|
| Authorization | ✅ | ✅ | |
| Capture | ✅ | ✅ | |
| Sale | ✅ | ✅ | |
| Void Auth | ✅ | ✅ | |
| Refund | ✅ | ✅ | |
| Top-Up | ✅ | ✅ | ⚠️ FNB-specific. Confirm with integration owner. |
| Tip Adjust | ❌ | ❌ | Not supported on MPGS. |
See MPGS Supported Transaction Types for the full gateway capability matrix.
5. Payment Methods Active
| PM Slot | Name | Role in This SKU | MPG Entries |
|---|---|---|---|
| PM0 | Bank Card | Card-present transactions via physical terminal | 1 |
| PM1 | Token | MOTO / card-on-file via sync or async channel | 2 (sync + async) |
PM1 has two entries because the terminal's asyncFlag selects which entry is used:
- asyncFlag=0 → routes to the token_sync entry (defaultFlag=1)
- asyncFlag=1 → routes to the token_async entry (defaultFlag=0)
There is no PM4 in this SKU. No ecom widget, no ecom processing entry, no HPP.
6. MerchantPaymentGateway Array
This SKU requires 3 MPG entries: one for PM0 and two for PM1.
| # | PM | Role | defaultFlag | Purpose |
|---|---|---|---|---|
| 1 | PM0 | bank_card | — | Card-present via physical terminal |
| 2 | PM1 | token_sync | 1 | Synchronous token channel (asyncFlag=0 on terminal) |
| 3 | PM1 | token_async | 0 | Asynchronous token channel (asyncFlag=1 on terminal) |
See MPGS MPG Configuration for full field definitions and the defaultFlag/asyncFlag routing explanation.
7. Configuration Workflow
Provision endpoints in this order. Each step depends on the previous.
Step 1 — Group (Optional)
If deploying under a group:
| Field | MGMT Field | Required | Sample |
|---|---|---|---|
GROUP_ID |
groupId |
Conditional | GRP-FNB-001 |
GROUP_NAME |
groupName |
Conditional | FNB Group |
Step 2 — Merchant
| Field | MGMT Field | Required | Sample (UAT) |
|---|---|---|---|
MERCHANT_NAME |
merchantName |
Mandatory | FNB Test Merchant |
REGION_ID |
regionId |
Mandatory | ⚠️ UNCONFIRMED |
COUNTRY_CODE |
countryCode |
Mandatory | ⚠️ UNCONFIRMED |
SECRET_DATA1 |
secretData1 |
Mandatory | <secret> |
MERCHANT_ID |
extData4 |
Mandatory | ⚠️ UNCONFIRMED |
STORE_ID |
extData5 |
Conditional | ⚠️ UNCONFIRMED |
EXTDATA7_RETENTION |
extData7 |
Conditional | 1m |
SKU_STAMP |
extData10 |
Conditional | FNB-ALL-0006-A-110000 |
Step 3 — MPG Entry 1 (PM0 Bank Card)
| Field | MGMT Field | Required | Sample (UAT) |
|---|---|---|---|
HOST_URL |
extData1 |
Mandatory | <secret> |
HOST_KEY |
extData2 |
Mandatory | <secret> |
HOST_PASSWORD |
extData3 |
Mandatory | <secret> |
MPGS_SYNC_CHANNEL |
channelId |
Mandatory | ⚠️ UNCONFIRMED |
GATEWAY_ID |
gatewayId |
Conditional | ⚠️ UNCONFIRMED |
Step 4 — MPG Entry 2 (PM1 Token Sync, defaultFlag=1)
| Field | MGMT Field | Required | Sample (UAT) |
|---|---|---|---|
TOKEN_SYNC_HOST_URL |
extData1 |
Mandatory | <secret> |
TOKEN_SYNC_HOST_KEY |
extData2 |
Mandatory | <secret> |
TOKEN_SYNC_HOST_PASSWORD |
extData3 |
Mandatory | <secret> |
TOKEN_SYNC_CHANNEL |
channelId |
Mandatory | ⚠️ UNCONFIRMED |
Step 5 — MPG Entry 3 (PM1 Token Async, defaultFlag=0)
| Field | MGMT Field | Required | Sample (UAT) |
|---|---|---|---|
TOKEN_ASYNC_HOST_URL |
extData1 |
Mandatory | <secret> |
TOKEN_ASYNC_HOST_KEY |
extData2 |
Mandatory | <secret> |
TOKEN_ASYNC_HOST_PASSWORD |
extData3 |
Mandatory | <secret> |
TOKEN_ASYNC_CHANNEL |
channelId |
Mandatory | ⚠️ UNCONFIRMED |
Step 6 — API User
| Field | MGMT Field | Required | Notes |
|---|---|---|---|
USER_EMAIL |
partnerEmail |
Conditional | STS API user. Required if tokenisation is active. |
Step 7 — Terminal
| Field | MGMT Field | Required | Notes |
|---|---|---|---|
TERMINAL_ID |
terId |
Mandatory | <secret> Supply via secrets manager. |
ASYNC_FLAG |
asyncFlag |
Mandatory | 0 = sync (token_sync MPG), 1 = async (token_async MPG) |
TERMINAL_CHANNEL_ID |
channelId |
Mandatory | ⚠️ UNCONFIRMED |
8. Environment Values (UAT)
⚠️ UAT only — UNCONFIRMED. All values below are from
values/*.yamland have not been independently verified. Do not use in SIT or PROD without confirmation.
| Field | UAT Value | Notes |
|---|---|---|
EXTDATA7_RETENTION |
1m |
Token retention period. Confirm format. |
SKU_STAMP |
FNB-ALL-0006-A-110000 |
Written to merchant extData10. |
| All channel IDs | ⚠️ UNCONFIRMED | See OI-003: channels.yaml is empty. |
| All host credentials | <secret> |
Supply via secrets manager. |
9. Comparison With C2C-ALL-0006-A-010010
Both SKUs use Solution 0006 (MPGS SPF) but differ in industry and active payment methods:
| Feature | FNB-ALL-0006-A-110000 | C2C-ALL-0006-A-010010 |
|---|---|---|
| Industry | Food & Beverage | C2C Ecommerce |
| Bitmap | 110000 |
010010 |
| PM0 Card Present | ✅ | ❌ |
| PM1 Token | ✅ | ✅ |
| PM4 Ecommerce | ❌ | ✅ |
| MPG entries | 3 (PM0 + PM1×2) | 4 (PM1×2 + PM4×2) |
| Top-Up flow | ✅ | ❌ |
| HPP / Drop-in | ❌ | ✅ |
See C2C-ALL-0006-A-010010 for the ecommerce variant.
10. Open Items
| # | Item | Impact |
|---|---|---|
| OI-003 | data/reference/channels.yaml empty |
All channel IDs UNCONFIRMED |
| OI-004 | data/reference/regions.yaml missing |
REGION_ID value unavailable |
| OI-009 | FNB industry flows are SEED values | Top-Up and other flows unconfirmed |
| OI-TERMINAL | TERMINAL_ID + ASYNC_FLAG + CHANNEL_ID not in values file | 3 MISSING required field warnings at build time |
11. See Also
- Solution 0006 Overview
- MPGS MPG Configuration
- MPGS Terminal Configuration
- MPGS Transaction Types
- C2C-ALL-0006-A-010010 — same solution, ecommerce variant
- Payment Methods Reference