One routing distinction separates a Verve card issued by a Nigerian bank from Visa's VisaNet. It determines the message format your switch expects, the settlement counterparty clearing your funds, and the BIN range table your authorization logic consults. Treating African schemes as regional versions of Visa or Mastercard can yield systems that pass sandbox tests but fail obscurely in production.
This article examines the main African card schemes, their technical requirements, and the integration assumptions most likely to fail.
The Scheme Landscape
Visa and Mastercard use their standard international infrastructure across Africa. Their message formats, BIN registration procedures, and settlement flows are documented. Less documented outside scheme certification programs is how domestic African schemes operate and where they differ.
Verve is Nigeria's domestic debit card scheme and is operated by Interswitch. It is one of the continent's most widely issued domestic card products. BINs in the 5061, 6500, and 6369 series are generally Verve cards, although Interswitch maintains and periodically updates the complete BIN table. Verve transactions use Interswitch's processing infrastructure rather than international scheme connections.
GHLink is Ghana's domestic card scheme, operated by the Ghana Interbank Payment and Settlement Systems authority (GhIPSS). Member banks issue GHLink-enabled cards for domestic debit use. The scheme runs on the GhIPSS national switch, separately from Visa or Mastercard networks. GHLink cards are domestic-only, and the GHLink scheme itself does not support cross-border acceptance.
Interswitch is both a payment processor and the Verve scheme operator. In Nigerian payments discussions, the reference may mean the Verve card network, the Quickteller consumer platform, or Interswitch's acquiring and processing services for merchants and issuers.
Other markets use domestic payment rails alongside card-adjacent instruments. In Kenya, Lipa Na M-Pesa leads retail payments at lower transaction values, while Mastercard and Visa appear more often at higher-value POS and ATM transactions. Domestic rails dominating some transaction layers while international schemes cover others is a common pattern across African markets.
Verve Integration Differences
Verve natively uses ISO 8583 messaging. Visa and Mastercard increasingly provide REST-based APIs for acquirer integrations, whereas Verve connectivity generally uses ISO 8583 socket connections or HTTP wrappers around ISO 8583 payloads, depending on the acquirer's connection design.
PIN is required for most Verve card-present and card-not-present transactions. Unlike the Mastercard or Visa path, CNP authorization cannot rely on CVV alone. This requirement shapes checkout flows for Verve customers.
Interswitch runs its own e-commerce cardholder authentication protocol, Verified by Interswitch (VbI). It differs from standard 3DS 1.0 and 3DS 2.x protocols used by Visa (Verified by Visa) and Mastercard (SecureCode / Identity Check). A 3DS integration cannot be presumed to support Verve CNP transactions.
Verve transactions settle through Interswitch's settlement infrastructure. Your acquiring relationship and Verve settlement account therefore sit with Interswitch, not a Visa or Mastercard correspondent bank. Reconciliation must support multiple settlement counterparties by currency and scheme.
BIN Table Management
Multi-scheme implementations often develop subtle routing errors around BINs. In Nigeria, a card BIN beginning 5061 routes to Interswitch as Verve, not Mastercard, whose prefix range is 51 to 55. Routing must use a BIN table covering every supported scheme, with updates whenever schemes register new BINs.
The result is usually not a hard crash. A wrong BIN route sends authorization to the wrong network, which returns a decline whose response code resembles a card problem rather than a routing problem. Diagnosis is difficult without logging the routing decision beside the response.
GhIPSS publishes GHLink BIN ranges separately from Interswitch's Verve table. Multi-market infrastructure for Nigeria and Ghana therefore maintains at least four BIN sets: Visa, Mastercard, Verve, and GHLink, with more added as coverage expands.
Response Code Mapping
ISO 8583 response codes do not carry identical meanings across every scheme. Code 55 for wrong PIN and code 14 for invalid card number are relatively consistent across Visa, Mastercard, and Verve. Other codes differ. Issuer-generated codes in the 57, 58, 62, and 63 series may mean different things depending on issuer host configuration and how acquiring and processing infrastructure interprets them.
This affects customer error messages and fraud scoring. A code signaling a suspected fraud hold at one issuer may mean insufficient funds at another. Producing clear decline messages requires scheme-aware response translation rather than one global map.
Authorization Flow Differences
With Visa and Mastercard, your acquirer processor connects to the international scheme switch, VisaNet or Banknet, which routes to the issuer's processor. With Verve, your Interswitch connection routes to the issuer over Interswitch's domestic network. GHLink traffic passes through the GhIPSS national switch to the issuing bank.
The result is different latency behavior. Connections from African processors to VisaNet or Banknet traverse regional hubs and have different round-trip characteristics from domestic Interswitch or GhIPSS links. Set authorization timeouts by scheme and corridor instead of using one global value.
What enza Handles and What You Still Need to Understand
For transactions entering the enza API, BIN classification and scheme routing occur before the authorization request reaches our processing core. You write no separate Verve and Visa code paths. Settlement reaches the appropriate scheme counterparty, while reconciliation returns in one feed containing scheme indicators for each transaction.
The scheme landscape still matters. When a Verve transaction declines with a particular response code, you must distinguish a Verve network condition from an issuer decision. Fraud thresholds and PIN-bypass behavior on Verve cards also require different treatment from international scheme cards. Scheme knowledge remains necessary for operations, while enza removes the need to build and certify each scheme integration yourself.
The African card scheme landscape continues to change. Several markets are assessing domestic scheme expansion along the Union Pay and RuPay models. Scheme-aware routing and clean BIN tables require continuing infrastructure maintenance, not a one-time setup, and their value increases as you enter more markets.