POS Terminal Architecture
A POS system has three layers: terminal hardware, a backend server for routing, and a payment gateway. The terminal must implement EMV Level 2 kernel certification for chip cards. The backend uses Node.js or Python with PostgreSQL, handling concurrent transactions with idempotency keys to prevent duplicates. PCI DSS compliance is mandatory: card data must never be stored on the terminal, and PIN blocks must be encrypted at the terminal level.
Payment Processing Flow
A POS handles three primary channels. For card payments, the terminal reads data through the secure element, builds an EMV request with currency code 566 for NGN, and sends it through the gateway to NIBSS for routing to the issuing bank. For bank transfers, the system generates an NQR code and listens for confirmation via webhook or NIBSS status API polling. For USSD, the terminal generates a payment code the customer dials to authorise. Redundancy across all three channels ensures continuity when any single channel is down.
NIBSS and Paystack Integration
Terminals register through a licensed PTSP using ISO 8583 or modern REST APIs. Paystack provides a dedicated POS API handling card present transactions, transfer confirmations, and settlement. Most production systems integrate at least two gateways for redundancy: if Paystack goes down, transactions route through Flutterwave or Interswitch based on backend routing rules.
Transaction Settlement
Settlement follows a T+1 cycle. The system generates a batch submitted to the gateway for NIBSS clearing. The POS reconciles settled amounts against original records using the gateway transaction ID and NIBSS trace number. Unmatched transactions are flagged for manual review. Automated reconciliation reduces accounting from hours to minutes.
Offline Mode, Inventory, and Receipts
Network outages are common across Nigeria. In offline mode, the terminal authorises transactions locally based on predefined rules, stores encrypted records in a local database, and submits them to the payment gateway when connectivity is restored. Risk is managed through cumulative transaction limits per terminal. The inventory module decrements stock in real time and synchronises across terminals using optimistic concurrency control with conflict resolution. Receipt printing is legally required under CBN guidelines using ESC/POS commands over Bluetooth, USB, or network. Digital receipts via SMS or email are increasingly expected by Nigerian consumers.
Frequently Asked Questions
How much does it cost to develop a POS system in Nigeria?
A basic POS software system costs between ₦5 million and ₦15 million depending on features. Hardware-integrated systems with NIBSS certification and full payment processing capabilities range from ₦15 million to ₦40 million.
Do I need CBN approval to deploy POS terminals in Nigeria?
Yes. All POS terminals must be registered with NIBSS and comply with the CBN Guidelines on Agent Banking and POS Operations. Terminals must support contactless payments by Q1 2027 under updated CBN directives.
What payment channels should a Nigerian POS system support?
A comprehensive POS system should support contactless card payments, chip and PIN, bank transfers via NQR, USSD payment codes, and QR code payments. Integration with at least two payment gateways is recommended for redundancy.
Your Next Step
Start with a working prototype handling a single payment channel, test with a small merchant network, and progressively add features. The CBN Regulatory Sandbox allows testing with limited users before full PTSP licensing. If you are planning a POS system, begin with a technical discovery session mapping your features against NIBSS requirements. Our team has built POS systems that process millions daily and passed PTSP certification on the first submission. Book a free consultation.