# PAMP Pay PAMP Pay is the central payment processing subsidiary of the Fintech Division and the financial backbone of the entire PAMP ecosystem. It provides a unified payment gateway that enables all 31 other subsidiaries to accept and process payments through a single integration. Built on the Nedbank gateway partnership for South Africa and extending to mobile money, card networks, and EFT across all Wave-1 markets, PAMP Pay handles the full payment lifecycle — authorization, capture, settlement, refunds, and payouts. As a **Payments Enablement** platform, PAMP Pay is a Phase 1 MVE subsidiary and the first fintech capability activated during country rollout. ## Business Model PAMP Pay operates a **transaction fee model** with tiered pricing based on payment method and volume: - **Transaction Fees**: 1.0–2.5% per transaction depending on payment method and merchant tier - **Gateway Access Fees**: Monthly SaaS fee for external merchants using PAMP Pay outside the ecosystem - **Cross-Border Surcharge**: Additional 0.5–1.5% for cross-border currency conversion - **Value-Added Services**: 3D Secure authentication, tokenization, fraud scoring, and recurring billing as premium add-ons - **Float Income**: Interest earned on settlement float (funds held between capture and merchant payout) (Visa/MC/Amex)"] EFT["EFT / A2A
(Bank Transfer)"] MM["Mobile Money
(M-Pesa, MTN MoMo)"] WALLET["PAMP Wallet"] COD["Cash on Delivery"] end subgraph "PAMP Pay Gateway" AUTH["Authorization
+ 3DS v2"] CAPTURE["Capture &
Settlement"] LEDGER["Double-Entry
Ledger"] PAYOUT["Merchant
Payout"] end subgraph "Settlement Partners" NED["Nedbank
(South Africa)"] MPESA["M-Pesa
(Kenya)"] MOMO["MTN MoMo
(West Africa)"] LOCAL["Local Banks
(Per Country)"] end CARD --> AUTH EFT --> AUTH MM --> AUTH WALLET --> AUTH COD --> AUTH AUTH --> CAPTURE CAPTURE --> LEDGER LEDGER --> PAYOUT PAYOUT --> NED PAYOUT --> MPESA PAYOUT --> MOMO PAYOUT --> LOCAL style AUTH fill:#10b981,stroke:#059669,color:#fff style LEDGER fill:#3b82f6,stroke:#2563eb,color:#fff style PAYOUT fill:#f59e0b,stroke:#d97706,color:#fff `} /> ## Total Addressable Market (TAM) ## Pricing Structure **Volume Discounts**: Merchants processing >$50K/month qualify for negotiated rates (typically 0.3–0.5% reduction). Enterprise merchants with >$500K/month receive custom pricing. ## Operating Model PAMP Pay operates as the **shared payment infrastructure** for the entire PAMP ecosystem: - **Gateway Layer**: Unified API (RESTful, OpenAPI 3.x) abstracting multiple payment providers behind a single integration - **Nedbank Integration**: Primary gateway for South Africa — cards (Visa/MC/Amex), EFT (A2A), 3D Secure v2, tokenization - **Mobile Money**: Direct integrations with M-Pesa (Daraja API), MTN MoMo, Airtel Money, and Orange Money - **Ledger**: Double-entry accounting via ledger-svc ensuring every transaction is balanced and auditable - **Fraud Prevention**: Real-time fraud scoring, velocity checks, device fingerprinting, and 3DS v2 challenge flows - **Settlement Engine**: Automated merchant payouts on configurable schedules (daily, weekly, bi-weekly) - **Webhook System**: Real-time event notifications — payment.authorized, payment.captured, payment.settled, payment.chargeback, refund.processed ### Nedbank Integration Details The Nedbank partnership provides the following API categories for South Africa: 1. **Authorisation API** — OAuth 2.0 token management for all API calls 2. **ePay Solutions Enterprise** — Card payments, 3D Secure v2, tokenization for recurring payments 3. **Payments API** — EFT/A2A transfers with track & trace capabilities 4. **Wallet API (MobiMoney)** — Mobile wallet integration for Nedbank customers 5. **Value-Added Services API** — Airtime, data, and voucher purchases 6. **Rewards API** — Greenbacks and Amex Membership Rewards integration 7. **Customers API** — Profile prefill and consented data sharing ### Payment Flow >Checkout: Select payment method Checkout->>PaymentSvc: POST /intents (create intent) PaymentSvc->>Nedbank: Authorize payment Nedbank-->>PaymentSvc: 3DS v2 challenge (if required) PaymentSvc-->>Checkout: Redirect to 3DS Buyer->>Nedbank: Complete 3DS challenge Nedbank-->>PaymentSvc: Authorization result PaymentSvc->>PaymentSvc: Capture payment PaymentSvc->>LedgerSvc: POST /journal (debit buyer, credit merchant) LedgerSvc-->>PaymentSvc: Journal entry confirmed PaymentSvc->>OrderSvc: Payment confirmed event OrderSvc-->>Buyer: Order confirmation `} /> ## Regulatory Notes | Market | Regulatory Body | Key Requirements | |--------|----------------|------------------| | South Africa | FSCA, SARB, PASA | Payment Service Provider (PSP) registration, PASA membership, PCI DSS Level 1, POPIA compliance | | Nigeria | CBN | Payment Solution Service Provider (PSSP) license, CBN sandbox approval, NDPR compliance | | Kenya | CBK | Payment Service Provider license, mobile money regulations, Data Protection Act compliance | | Morocco | BAM, ANRT | Payment institution license (Law 103-12), Bank Al-Maghrib approval, data localization | | DRC | BCC | Payment service authorization, limited regulatory framework — focus on banking partnerships | | Senegal | BCEAO | WAEMU payment institution license, BCEAO e-money regulations | | Ghana | BoG | Payment Service Provider license, Electronic Money Issuer (EMI) regulations | **PCI DSS Compliance**: PAMP Pay maintains PCI DSS Level 1 compliance with no PAN storage. All card data is tokenized at the gateway level (Nedbank) with scope reduction measures including network segmentation and point-to-point encryption. ## SWOT Analysis ## Competitive Positioning ## KPI Dashboard --- ## Payments Enablement Scope PAMP Pay serves as the **Payments Enablement** layer for the entire ecosystem. The following epics define the payment capabilities delivered across all subsidiaries: ### Epic 1: Core Payment Gateway | Story ID | Story | Priority | Points | |----------|-------|----------|--------| | PAY-101 | As a buyer, I can pay with Visa/Mastercard via Nedbank gateway with 3DS v2 | P0 | 8 | | PAY-102 | As a buyer, I can pay via EFT/bank transfer (Nedbank A2A) | P0 | 5 | | PAY-103 | As a buyer, I can pay using M-Pesa (Kenya, DRC) | P0 | 5 | | PAY-104 | As a buyer, I can pay using MTN MoMo (Nigeria, Ghana, Senegal) | P0 | 5 | | PAY-105 | As a buyer, I can pay using PAMP Wallet balance | P0 | 5 | | PAY-106 | As a system, I can tokenize card details for recurring payments | P0 | 8 | | PAY-107 | As a system, I can process refunds (full and partial) | P0 | 5 | ### Epic 2: Ledger & Settlement | Story ID | Story | Priority | Points | |----------|-------|----------|--------| | PAY-201 | As a system, I record every transaction as a double-entry journal in ledger-svc | P0 | 8 | | PAY-202 | As a merchant, I receive automated payouts on my configured schedule | P0 | 5 | | PAY-203 | As an admin, I can view real-time reconciliation reports | P0 | 5 | | PAY-204 | As a system, I can handle settlement failures with retry and escalation | P0 | 5 | | PAY-205 | As an admin, I can trigger manual settlement runs | P1 | 3 | ### Epic 3: Fraud & Security | Story ID | Story | Priority | Points | |----------|-------|----------|--------| | PAY-301 | As a system, I perform real-time fraud scoring on every transaction | P0 | 8 | | PAY-302 | As a system, I enforce velocity limits per card/device/IP | P0 | 5 | | PAY-303 | As a system, I handle 3DS v2 challenge flows for high-risk transactions | P0 | 5 | | PAY-304 | As an admin, I can configure fraud rules and thresholds per market | P1 | 5 | | PAY-305 | As a system, I process chargeback notifications and update ledger | P0 | 5 |