Agency bill pay and NAMQR: integrate faster without skipping diligence
Pre-integrated agency tariffs, NAMQR TLV fixtures, and step-up 2FA in the NamPost module—shorten pilots while keeping PSD-10 and PSD-12 controls.

Fintechs lose months negotiating bilateral access to billers and QR schemes. The NamPost module ships mock NAMPAY/IPN endpoints, agency commission engine, and NAMQR generate/scan paths aligned to platform contracts—so you validate product logic before commercial MOUs.
What is pre-integrated
- Agency: NamWater, MTC, municipal presentment with tariff-accurate
fee+commissionin responses. - NAMQR: Tag 26 IPP alias + Tag 65 Token Vault validation; offline batch replay.
- PIS + 2FA: Every initiation requires step-up token—mirrors PSD-12 supervisory language.
- USSD channel:
channel: ussdon shared backend; simulator codes documented in channel matrix docs.
Diligence that still applies
- Your consumer benefit narrative in NPIF application (min 200 chars).
- Idempotency on retries—Ndishi's spaza depends on it.
- Rate limits and cap banners in the participant portal.
- Regulator reporting—fee drift triggers amber on Observation Deck.
Anti-pattern
Treating pre-integration as permission to skip disclosures. PSD-10 fee lines must appear in UX and API payloads—same business rule, two representations.
Apply for the payments track at /nampost/payments.
Ready for your 6-week PoC?
Apply for sandbox accessMore Articles
PSD-12, SmartPay, and step-up 2FA on every payment initiation
Namibia's PSD-12 pattern requires step-up authentication before each payment—not login-only MFA. How the NamPost sandbox enforces that in APIs and UX.
April 30, 2026
Synthetic SmartCards and grant cohorts: testing without harming beneficiaries
How NamPost sandbox seeds statistically shaped SmartCards, grant sequences, and agency tariffs—zero production PII in default namespaces.
April 30, 2026
