How Nigerian Acquirers Should Plan POS Failover Between NIBSS and UPSL

Content authorBy EGSPublished onReading time11 min read
A close-up view from a customer's perspective showing a hand holding a smartwatch near a payment terminal at a café checkout.

Route a POS transaction to the second Payment Terminal Service Aggregator (PTSA) only when you can prove the first one never accepted the financial request. Once the request crossed the wire, the outcome is unknown, and the correct move is to keep the original identifiers and resolve the state through reversal or reconciliation.

Failover must preserve transaction integrity

Switching routes is safe when nothing financial was accepted, and dangerous the moment it might have been. That's the whole design question. Transport failure and transaction failure look identical from the terminal's point of view, which is why a failover rule written around link health alone will eventually debit a cardholder twice for one purchase.

Card scheme rules already treat the uncertain state as an obligation. Mastercard's Transaction Processing Rules require an acquirer to send a reversal within 60 seconds of receiving the authorization response when a transaction fails to complete, and to support reversals whenever the acquirer host can't communicate a response back to the terminal.

Read that requirement backwards and you get your failover rule. If the scheme expects a reversal tied to an original authorization, then the original message identity has to survive the outage, which means your failover logic can't be allowed to mint a fresh transaction and walk away from the old one.

What does the current mandate require?

The Central Bank of Nigeria (CBN) requires active links to both aggregators and automatic switching during an outage. The circular signed by Dr. Rakiya Yusuf, Director of the Payments System Supervision Department, dated December 11, 2025, gave acquirers one month to maintain live connections to both the Nigeria Inter-Bank Settlement System (NIBSS) and Unified Payment Services Limited (UPSL), a deadline that also covered processors and Payment Terminal Service Providers (PTSPs). NIBSS and UPSL must notify banks immediately during downtime and file an incident report within 24 hours.

Notice what the mandate does not say. It doesn't define a timeout threshold or the evidence standard that proves a request was never accepted. Those are left to the participants, which means the regulator has handed you the obligation to switch without handing you the rules that make switching safe. Your dual-PTSA design has to supply that layer yourself, agreed in writing with your processor and both aggregators before the first automatic reroute fires in production.

Who controls each transaction stage?

Flowchart depicting recovery gaps in financial transactions, featuring rounded cards, arrows, and vector icons in a clean, blue-themed design.

Map ownership first, because every recovery gap in a dual-PTSA setup sits in the space between two parties who each assumed the other was handling it. A single POS payment already passes through the merchant and the terminal, then onward through the PTSP and the PTSA on its way to the issuer. Add a second aggregator and you've added a decision point.

The friction is measurable. NIBSS has put the failure rate for card transactions on POS terminals at 13 to 15 percent, against 0.7 percent for NIBSS Instant Payment transfers, and the gap comes largely from the number of hops a card message makes.

So the chain length is the risk. More hops mean more places where a response dies in transit, and a failover design that doesn't name an owner for each hop will produce transactions nobody is accountable for reconciling. The four subsections below assign those owners.

Terminals preserve the original transaction

The terminal's job during an outage is memory. It holds the System Trace Audit Number (STAN) and the Retrieval Reference Number (RRN), then follows whatever routing configuration the acquirer pushed to it.

That identity has to carry forward. The Worldpay ISO 8583 host specification states plainly that a reversal should carry the same RRN as the original message, because the RRN is how the transaction is traced across its whole life cycle.

Which tells you where most PTSP applications go wrong. If the terminal application generates new identifiers when it fails over, it has destroyed the only key your processor could have used to match the two attempts, and the duplicate becomes invisible until settlement.

Start building your financial platform?

Speak with EGS engineers about open banking, payment infrastructure, cloud systems, and enterprise software.

Get in Touch →

PTSAs manage routing availability

NIBSS and UPSL move POS traffic toward the processor you nominated. They don't decide whether a cardholder was debited. The CBN licensed NIBSS as a PTSA in August 2011 and granted the second license to UPSL on April 19, 2024, specifically to break the single-aggregator dependency.

Route-health signals and outage notices from either aggregator are useful inputs. They are not financial evidence. An aggregator telling you a link is down says nothing about the forty messages that were in flight when it went down.

Treat PTSA telemetry as a trigger for investigation and a trigger for routing new traffic, never as proof of outcome for traffic already sent. That distinction is the one your operations team will be tempted to collapse at three in the morning.

Processors determine recorded outcomes

The processor journal is your source of truth. Whether a request was declined or left hanging is settled by what the processor logged and by the reversal and reconciliation records that follow.

Switching platforms encode this behavior explicitly. In Postilion's eSocket.POS, when the real-time connection doesn't respond inside the configured window, the sink declines the request with response code 91 and generates a 0420 reversal advice, and it queues advices rather than discarding them when no connection exists.

So the platform already distinguishes "declined with a reversal raised" from "unknown." Your failover rules should inherit that distinction instead of flattening every non-response into a retry, because a response code 91 with a matched reversal advice is a resolved transaction, and an unanswered request with no advice is not.

Acquirers own recovery policy

You own the policy. Retry limits and reversal triggers are acquirer decisions, and no PTSA or PTSP can make them for you without blurring the responsibility lines the regulator drew.

The clock is already set. Under the CBN circular effective June 8, 2020, refunds on disputed or failed POS and web transactions must be treated within 48 hours, and switches had to compress the chargeback cycle to 24 hours.

Work backwards from 48 hours and your internal deadlines write themselves. If a failover produces an uncertain transaction at 09:00, the reversal attempt and the manual refund have to fit inside two days, so your exception queue needs an owner with a name.

Why can blind resubmission create duplicates?

Resubmitting a transaction with a new identity turns one purchase into two financial records that no system can reconcile. The sequence is ordinary. A request goes out through NIBSS and the cardholder is debited, but the approval response dies on the way back because the link dropped. The terminal sees a timeout. If your logic then builds a fresh message with a new STAN and RRN and pushes it through UPSL, the issuer approves again.

Now you hold two debits and a merchant dispute. Multiply that by volume. POS transactions in Nigeria were worth N18.78 trillion in the first quarter of 2026, up 79.03 percent year on year according to NIBSS data cited by Financial Derivatives Company.

At that volume, a duplicate rate low enough to look like rounding error in a test report becomes a daily dispute queue your contact center can't clear inside the 48-hour window. The resubmission path is where dual connectivity stops being resilience and starts being a liability.

Start building your financial platform?

Speak with EGS engineers about open banking, payment infrastructure, cloud systems, and enterprise software.

Get in Touch →

Which failures permit route switching?

Switch routes only in the cases where transport failed before the financial request was accepted. Build the matrix around transaction state, not link state, and give every row an owner and an evidence requirement:

  • Connection refused or gateway unreachable before transmission, owned by the terminal and PTSP, evidenced by connection logs showing no bytes sent.

  • Request transmitted with no response inside the timeout, owned by the processor, evidenced by the journal entry and the reversal advice raised against it.

  • Response received late, after the terminal gave up, owned by the processor and the acquirer together, evidenced by correlated timestamps across both route logs.

The Uptime Institute's Annual Outage Analysis 2025 found that IT and networking issues accounted for 23% of impactful outages in 2024, a rise the report attributes to complexity and misconfiguration. Adding a second aggregator adds exactly that kind of complexity, so your matrix has to be narrower than your instinct.

No request crossed the connection

Reroute freely here, and only here. The condition is that connection and gateway evidence shows no financial message was ever accepted by the first PTSA, which means a refused TCP connection or a failed handshake.

Timeouts are the trap. The Worldpay ISO 8583 reference guide recommends a client timeout value of at least 25 seconds and adds five seconds for each additional network hop between the device and the host.

Nigerian POS traffic runs through more hops than that baseline assumes once you insert a PTSA and a processor between terminal and issuer. If your terminal timeout was tuned for a shorter chain, it will declare "no request sent" on transactions that were in fact accepted, and your safest failover case quietly becomes your most dangerous one.

The response was lost

Treat this as unknown and resolve it, never resend it. Keep the original STAN and RRN and raise a reversal.

Timing matters more than most designs allow for. The Worldpay host specification warns that a timeout reversal not sent within 10 minutes of the original transaction may fail if the original was approved and already passed to settlement.

Ten minutes is shorter than most incident bridges take to assemble. So the reversal has to be automatic and queued by the platform during the outage, otherwise your recovery arrives after the settlement file has closed and the only remaining remedy is a manual refund.

Recovery remains delayed

Bound the retries, then escalate to people. Define a fixed retry count with a defined interval and hand the case to a named investigator.

The regulatory ceiling here is tight. Where an instant reversal fails because of a technical issue or system glitch, the CBN requires manual reversal within no more than 24 hours, and processors must deliver daily settlement reports by 8am on a T+1 basis.

Line those two up and the operational consequence is clear. Your investigators get one settlement cycle to find the transaction, so if route history and processor journals aren't joined in a single searchable view before the incident, the 24-hour clock expires while someone is exporting logs.

The failed route returns

Bring traffic back in stages, after you've checked health and reconciled what happened during the outage. Validate the link and then raise the traffic share gradually instead of flipping everything back at once.

A restored link also says nothing about the transactions stranded during the failure. The NIP case study published in AfricaNenda's SIIPS 2025 report notes a maximum processing time of 20 seconds per transaction, with most completing in under one second.

Against that baseline, anything still unresolved minutes after recovery is a state problem. Restoring the route returns capacity, so the reconciliation of the outage window has to run as a separate workstream with its own sign-off.

How should teams prove failover readiness?

Prove it by failing on purpose, in a test environment that mirrors production message flows. Pull the link mid-transaction. Delay a response past the timeout and then deliver it. Send the same reversal five times. Fail the reversal itself and reconcile the whole mess afterwards.

Idempotency is the pass criterion that catches most defects. As the engineering guidance on ISO 8583 reliability puts it, the same 0400 with the same STAN and RRN sent five times must result in one logical reversal, and the retry side is non-negotiable.

Your evidence pack needs to show the same discipline:

  • Correlated traces across terminal, PTSA, processor, and settlement for every test case, stored immutably.

  • Dashboards and alerts that distinguish route health from unresolved transaction count.

  • A runbook per failure row in your matrix, each with a named decision-maker and an escalation time.

Testing that only proves the link switched has proven the easy half. The regulator asked for failover, but your exposure sits in the transactions that were mid-flight when it happened.

How can EGS test your design?

Bring in an architecture review before your next scheduled failover test. Energize Global Services (EGS), founded in 2007 and headquartered in Yerevan with offices in Boston and Sofia, builds POS terminal software and card processing platforms for financial institutions, and holds ISO 27001 and AICPA SOC 2 certification.

An engagement at this level covers your POS and payment-processing message flows end to end and deliberate failure testing against the matrix described above. EGS does not certify you with NIBSS or UPSL, and nothing here substitutes for the testing those aggregators require of you directly.

Talk through your dual-PTSA failover design with EGS engineers and come away with the specific list of failure cases your team hasn't tested yet.

Start building your financial platform?

Speak with EGS engineers about open banking, payment infrastructure, cloud systems, and enterprise software.

Get in Touch →

Use connection and gateway records showing that the session failed before any financial message was accepted. Check the terminal, PTSP, and PTSA logs for transmission status, then compare them with the processor journal. A route outage notice alone isn't enough because messages can remain in flight when connectivity fails.

The terminal should retain the original STAN and RRN throughout retries, reversals, and reconciliation. The PTSP, PTSA, processor, and settlement records should carry those values unchanged. If a new route receives a request that represents the same financial attempt, its records must still point back to the original identifiers.

An acquirer should issue a manual refund when a reversal fails or the transaction remains unresolved after the allowed recovery process. First confirm the debit and review the processor journal, reversal records, and settlement data. Assign the case to a named owner so the refund is completed within the applicable CBN deadline.

Monitor route availability separately from unresolved transaction volume. Track requests with missing responses, late approvals, reversal-queue age, duplicate identifiers, and reconciliation status for the outage window. Alerts should show when a transaction needs investigation, because a healthy connection doesn't prove that earlier requests reached a final outcome.

Test failover before production use and repeat it after routing, terminal, processor, or message-handling changes. Include mid-transaction disconnections, delayed responses, repeated reversals, failed reversal delivery, and route restoration. Preserve correlated traces and settlement results for each test so the team can verify one logical outcome per transaction.

Schedule a Meeting

Book a time that works best for you

You Might Also Like

Discover more insights and articles

A project manager in business casual attire discusses a document intake process with a team in a modern office, focusing on a large monitor.

Bank document intake workflow: A readiness checklist

This article gives you a checkpoint-by-checkpoint method for testing a document intake process before you turn it on. It includes a worksheet structure you can copy into a spreadsheet and the evidence each control needs to produce.

Two business partners collaborate on configuring a POS terminal in a modern office, surrounded by payment devices and colleagues.

EthioPay for Ethiopian Banks: Turn Readiness into a Delivery Plan

This article explains how an Ethiopian bank moves from "we want to participate" to a dated, costed integration plan for the country's domestic card scheme and instant payment rails. It covers service selection and a phased release sequence.

A modern smartphone displaying a mobile banking app lies on a wooden desk, surrounded by abstract payment cards and a notebook.

AfriGO Card Readiness: Plan Your Nigerian Bank’s Rollout

This article is a readiness guide for moving from "we're considering it" to a controlled pilot on Nigeria's domestic card rails. It covers role definition and launch scope, then maps the transaction flow so you can assess systems and assign requirement ownership through the workstream matrix that holds the whole program together.

A professional seated at a desk uses a smartphone and payment card, engaged in online banking in a bright, modern office.

G2P Payments in Africa: Build Reliable Social Payment Infrastructure

This article traces the full lifecycle of a government social payment in Africa, from eligibility approval through to reconciliation and investigation evidence. It assigns operational ownership at each system boundary and sets out how to control exceptions and assisted access.