The core operational problem is misjudging when authorized transaction funds will actually arrive. Settlement timing determines when you receive the money, while float management governs what you can do before then. These assumptions are often missed during initial integration and become costly after launch.
This article explains African banking corridor cycles, how to plan for their variation, and how a card operation should manage float carefully.
Settlement Cycle Basics
Settlement moves funds from the payer's bank to the receiving bank after a card transaction. Authorization takes milliseconds, while settlement follows a deferred cycle: T+0 (same-day), T+1 (next business day), T+2, or T+3, based on the corridor.
Here, "T" means the transaction date. A Monday transaction settling T+1 reaches the merchant or acquirer on Tuesday; T+2 means Wednesday. For a high-volume merchant or platform, moving from T+1 to T+2 leaves one extra day's volume in transit, creating material float at scale.
The chain includes the issuing bank, the card scheme settlement system, the acquiring bank, and the acquirer's settlement account. Each adds processing time. A scheme usually runs settlement once or twice per business day. Thus T+0 is not available everywhere, even when technically feasible, because the transaction must meet that corridor's settlement cutoff.
African Corridor Variability
African banking corridors have less uniform settlement timing than the European SEPA zone or the US ACH network. Market-specific details differ considerably.
Nigeria: NIBSS (Nigerian Interbank Settlement System) runs the domestic settlement infrastructure. Verve transactions processed through Interswitch and settled via NIBSS can settle same-day or T+1 when processed before the NIBSS cutoff. International scheme transactions (Visa, Mastercard) through correspondent banks generally run T+1 to T+2, while USD-to-NGN conversion adds complexity because of the Nigerian foreign exchange market.
Ghana: GhIPSS runs domestic settlement. T+1 is the normal expectation for domestic card transactions, but cutoff times are important. Transactions arriving after the GhIPSS settlement run cutoff, typically early-to-mid afternoon, settle the next business day rather than that day.
East Africa: Kenya, Uganda, and Tanzania each use different central bank settlement systems. Cross-border East African transactions rely on correspondent banking relationships and generally settle on T+2 or T+3. The EAC payment interoperability framework is progressing, but cross-border timing is not yet uniform or predictable across every corridor.
Cross-border and international: Where the issuing and acquiring banks are in different African countries, or an African card is used for international e-commerce, settlement uses international scheme systems, including Visa's VSS and Mastercard's GCMS. These usually settle in USD on T+2 or T+3, with local currency conversion performed by the acquirer.
Settlement Timing and Float
Float is authorized money that has not settled. During this period, the merchant or platform does not hold the funds, only an authorization, which is the issuing bank's commitment to transfer them. The transfer occurs when settlement completes.
When a platform or marketplace pays sellers before card scheme settlement arrives, its settlement-cycle float becomes a working capital cost. Paying sellers at T+0 while receiving scheme funds at T+2 requires two days of transaction volume funded from its own capital. At high daily volumes, substantial working capital remains tied up in transit.
A failed settlement batch extends the expected cycle. Processing errors, format mismatches, or network issues can cause this. Liquidity must cover the gap while resolution proceeds, which may require one to three additional business days depending on the scheme and acquirer process.
Reconciliation in Practice
Reconciliation matches internal transaction records with scheme settlement files and the related credits to the settlement account. It appears simple, but creates operational work because of:
- Timing mismatches: transactions processed on one day may appear in a settlement file the following day or the day after, depending on scheme cutoff times
- Rejected items: transactions that cleared in your system but were rejected during scheme settlement processing, typically due to BIN routing or message formatting issues
- Reversals and refunds: transactions reversed after clearing appear as separate line items in subsequent settlement files, not as corrections to the original transaction
- FX adjustment items: for transactions settled in USD with local currency conversion, FX rate differences between the authorization rate and the settlement rate create small discrepancy items
Manual matching cannot support volumes above a few hundred transactions daily. It turns operations into a bottleneck and allows errors to build. Production card operations require automated reconciliation with exception flagging.
Reserves and Liquidity Planning
Some African central banks require acquirers or payment service providers to keep settlement reserves at the central bank or a designated correspondent bank. These funds cover obligations after processing failures. The CBN and BoG both impose reserve or capital adequacy requirements on licensed payment processors.
Even without a formal reserve rule, an operational settlement liquidity buffer is prudent. Size it using daily transaction volume, the usual cycle length in each corridor, and the historical rate of settlement delays. Covering three to five days of peak transaction volume is a reasonable starting point, then adjust for corridor mix and counterparty reliability.
How enza Handles Settlement Timing
enza's settlement layer connects each corridor to its card scheme settlement system and sends normalized confirmation data through the API. The feed contains per-transaction confirmation timestamps, scheme batch references, and FX rate records for international transactions.
For each corridor, we document the settlement cycle, same-day cutoff times, and escalation route for delayed batches. The material applies to the corridors where we operate, rather than describing settlement globally.
enza handling the connections does not remove the need to understand corridor settlement mechanics. That knowledge supports float management, liquidity planning, and accurate merchant communication about fund availability. The most common preventable settlement dispute we see starts when merchants receive an arrival estimate based on authorization time instead of the settlement cycle. Setting expectations against the actual T+1 or T+2 cycle for that corridor prevents the dispute.