A national payment platform should be able to gain continental reach without making every participant adopt a second integration architecture.

01

Continental reach belongs inside the sovereignty argument

Connecting to PAPSS presented an architectural challenge: extend the national payment platform’s reach while preserving the participant integration model already established through SIPS Connect.

At Somali Payment Switch, I architected and built a dedicated gateway to handle PAPSS connectivity, message translation, trust verification and recovery. The integration is fully tested end to end and UAT certified, with system integration testing (SIT) certification by PAPSS. This article explains the architecture behind that delivery; user acceptance testing (UAT) and production activation remain distinct milestones.

In my earlier writing about sovereign payment infrastructure, I argued that the operator must be able to understand, govern, maintain and extend its systems. In the work at Somali Payment Switch, that meant building the connective capabilities around the transaction engine: participant integration, message trust, operational visibility, settlement support and financial evidence. PAPSS adds the cross-border connection to that architecture.

Sovereignty does not require isolation from external networks. It requires the ability to connect on terms that leave local responsibilities understandable and locally governable. The domestic platform should decide how participants enter its services. An external network should not dictate the internal shape of every bank integration.

PAPSS adds a controlled cross-border connection to this architecture. The gateway extends network reach while the national switch, participant institutions and applicable settlement arrangements retain their responsibilities.

02

What PAPSS adds and what the gateway owns

PAPSS is the Pan-African Payment and Settlement System, a cross-border financial market infrastructure enabling payments between participating African institutions in local currencies. Its public operating model distinguishes instant payment, prefunding and net settlement. These are related processes with different responsibilities and timing.

The gateway I built coordinates the messages and evidence needed to participate in that environment. It admits eligible instructions, resolves the intended institutions, exchanges PAPSS messages, handles incoming instructions and delivers outcomes back through SIPS Connect. It also preserves the information needed to recover when an exchange becomes uncertain.

Participant institutions retain customer-account posting and their business decisions. PAPSS and the applicable settlement arrangements retain network and settlement responsibilities. Keeping those boundaries explicit prevents a successful message exchange from being mistaken for proof that every financial obligation has been discharged.

03

I preserved the participant boundary instead of duplicating it

SIPS Connect already absorbed differences between participant Core Banking systems and the national payment environment. It provided the place to normalize requests, apply the participant messaging contract, protect identity and return a usable result. I kept that responsibility with SIPS Connect when adding PAPSS.

The integration path remains participant institution, SIPS Connect, PAPSS gateway and PAPSS. A bank does not need a direct PAPSS transport adapter inside its Core Banking integration simply because it wants to use a cross-border service. PAPSS endpoints, channel headers, XML signature conventions and receive-queue behavior belong behind the dedicated gateway boundary.

Preserving the boundary does not mean every participant can use every new service without onboarding or changes. PAPSS introduces additional service inputs, corridor checks, eligibility requirements and lifecycle decisions. Those additions are exposed through controlled SIPS Connect service contracts, rather than by distributing the entire external protocol to every participant.

That distinction is the practical value of the architecture. The platform can extend participant capability while retaining the integration pattern, local trust relationship and ownership model that institutions already understand.

Responsibility map

Continental reach through the existing participant boundary

Responsibility flows across distinct systems. Instructions and outcomes travel in both directions; each boundary retains its own trust decisions.

  1. Participant institutionCustomer accounts and business acceptance
  2. SIPS ConnectCore Banking adaptation and signed local contracts
  3. PAPSS gatewayDurable orchestration, recovery and the PAPSS adapter
  4. PAPSS networkNetwork processing and applicable settlement arrangements
Operating principleA new network should extend participant capability through a controlled contract, without transferring its protocol complexity into every participant system.
04

The gateway translates meaning as well as XML

Using ISO 20022 on both sides does not make the two boundaries identical. The SIPS side and the PAPSS side use different message versions, envelopes, signing profiles and identifier conventions. The gateway therefore works with typed transaction meaning between adapters, rather than treating the incoming XML as a document to forward unchanged.

For example, a credit transfer crosses the local boundary as a SIPS-profile pacs.008 and is rendered into the PAPSS-supported pacs.008 definition. Name verification uses acmt.023 and acmt.024; payment status and status enquiries use pacs.002 and pacs.028; return and recall handling use their own lifecycle messages. Every mapping must preserve the parties, amounts, references and operation being authorized.

I also separated discovery, readiness and foreign exchange (FX) information from payment submission. On the SIPS Connect boundary, these services use signed admi.009 StaticDataRequest and admi.010 StaticDataReport messages under bilateral SPS profiles. A protected business-service identifier selects the discovery, readiness or FX profile, and a schema-defined supplementary payload carries its fields.

These are bilateral SPS profiles built on ISO message structures. They are not a claim that ISO mandates one universal PAPSS discovery or FX service. On the direct PAPSS IPS boundary, the corresponding information APIs are HTTP services; the current adapter parses their XML payloads. The gateway converts their meaning into the signed local contract instead of exposing the external API as a participant integration.

05

Institution identity stays separate from connection identity

A technical connection and the institution represented by a payment are different identities. I made that distinction explicit because a gateway can carry traffic for more than one locally represented institution, and PAPSS can relay messages through a network switch identity.

The local institution directory controls which SPS institutions are enabled and where their callbacks must be delivered. PAPSS reference data supplies the network participant identity, supported currencies, capabilities and availability. The association between those directories must be exact and unambiguous; a convenient name match is not sufficient authority for routing money-related messages.

For outbound traffic, the local sender is resolved under SPS controls and associated with its PAPSS identity. For inbound traffic, the protected destination is associated back to the correct local institution and callback. Per-institution receive contexts keep the queue being polled distinct from a generic application identity.

A relaying switch must not accidentally become the business counterparty. The gateway resolves that role from protected message content and the original transaction evidence. This is one reason an adapter needs semantic knowledge rather than only HTTP connectivity.

06

Two trust boundaries require two verification decisions

On the SIPS side, the gateway preserves the local signed-message contract and verifies the represented participant. On the PAPSS side, the adapter handles the approved transport and business-message protection. A valid participant signature does not automatically authenticate a PAPSS submission, and a PAPSS signature does not become a local participant credential.

The gateway verifies the incoming message, preserves its source evidence, maps the instruction into the destination profile and signs the outgoing envelope under that boundary's identity. Mutual TLS protects the applicable transport connection; message-signature verification protects the signed business content. Those controls answer different questions.

The same discipline applies when sending results back. An outcome must be delivered through the configured route for the represented institution, with the correct local message profile and trust configuration. A response that is cryptographically valid but belongs to another institution or another original instruction must not update the payment.

07

I made payment responsibility durable before external dispatch

I built the gateway as a modular .NET application with PostgreSQL coordination and bounded background workers. This gave me one deployable product while retaining distinct ownership for the canonical model, SIPS adapter, PAPSS adapter, evidence and execution. I did not need a separate service for every message family to preserve those boundaries.

The processing path retains the received evidence, admits the instruction, records the local decision and creates durable work for the permitted outbound action. Each stage has a recorded responsibility. The exchange across independent systems spans multiple transactions.

Workers discover committed work, claim it under execution controls and revalidate authority before sending externally. After a process restart, recorded state tells the next worker what remains to be done. Stable transaction and action identities keep a delivery attempt associated with its original business instruction.

The immediate local admission result means that the gateway has accepted responsibility for processing under its contract. It is not the PAPSS business outcome. That outcome must arrive as evidence, be correlated to the original operation and then be delivered through its own callback path.

08

A timeout cannot decide what happened to the money

The difficult case is the request that may have reached PAPSS before its response was lost. A timeout proves that the caller did not obtain a result in time. It does not prove that the network rejected the instruction or that the beneficiary was never credited.

The gateway preserves uncertain handoff as an explicit condition. Recovery uses the original references, subsequent incoming evidence, status enquiry and controlled reconciliation. It does not hide uncertainty by creating a fresh payment and hoping duplicate controls elsewhere will catch it.

Correlation is scoped to the operation. A status report about the original credit transfer, a report about a return and a report about a recall submission can mention related transaction identifiers while making different assertions. Applying them to the same payment state without checking their original message type would manufacture financial meaning.

Callback delivery is a separate problem. If the network outcome is known but delivery back to SIPS Connect is delayed, the gateway should recover that delivery responsibility. It should not repeat the financial submission just to produce another response.

Recovery sequence

Recover the outcome before retrying delivery

If the outcome remains uncertain, keep the original instruction open for investigation. Once the outcome is established, a callback retry only delivers that result.

  1. 01 / SubmitRecord the instruction and its original references before dispatch.
  2. 02 / TimeoutPreserve an uncertain handoff; do not infer rejection or create a fresh payment.
  3. 03 / Recover evidenceUse status enquiry, incoming messages and controlled reconciliation.
  4. 04 / Correlate outcomeMatch the institution, original instruction and lifecycle operation.
  5. 05 / Deliver resultRetry a delayed SIPS Connect callback independently of the payment submission.
Operating principleTransport uncertainty belongs in the recovery model. It must not be converted into a financial verdict.
09

Receiving a payment is a business conversation

PAPSS integration is bidirectional. The gateway polls the configured receive contexts, validates incoming business messages, resolves the local institution and retains the evidence before delivering the appropriate SIPS Connect instruction. The receiving institution remains responsible for its account checks and business acceptance or rejection.

Receipt acknowledgement and business response are not interchangeable. For the selected inbound payment profile, a pacs.002 business response can serve the required confirmation role; other message families use a separate receipt acknowledgement. A name-verification request still needs its account-verification answer. The adapter applies the operation's agreed profile rather than one generic ACK rule.

The gateway also preserves returns and recalls as related but distinct lifecycles. A recall asks for recovery of an earlier payment. Acceptance of that request does not itself return funds. A return has its own financial instruction and evidence. A refusal has its own resolution message. The original payment history remains available throughout that conversation.

10

Information is useful only when its authority is clear

Discovery asks which institutions exist and what capabilities they advertise. Readiness asks whether the intended institution is eligible for the requested interaction. FX asks about a specific corridor, currencies, amount and applicable calculation. Treating all three as a generic lookup would lose the evidence needed to decide whether a payment can proceed.

Participant observations and indicative rates can be refreshed into local projections, while an applicable live enquiry or payment-specific FX acquisition has its own timing and evidence. A displayed indicative rate must not silently become the authority for a different payment amount. When cross-currency processing is enabled, the payment's financial intent must stay bound to its relevant rate, currencies and derived amounts.

The gateway retains the original observation context rather than making old information look new simply because a local request arrived later. Similarly, receiving a PAPSS position snapshot gives the platform information to inspect; it does not turn the gateway into the owner of participant balances, liquidity policy or settlement obligations.

11

Certification and the responsibility to operate

End-to-end testing exercised the integration as a connected payment flow. UAT certification and PAPSS SIT certification mark acceptance milestones for the tested scope.

Production activation and the enablement of an individual participant or corridor remain separate decisions. Production operation brings its own institution onboarding, environment, settlement and operational responsibilities.

The institutional value also depends on who can operate and extend the result. Source ownership, documented contracts, diagnosable state, controlled escalation and transferable knowledge matter alongside successful test exchanges. A platform remains dependent if only one person can explain why a payment is uncertain or how a network profile affects a message.

I was responsible for the architecture and implementation of this integration, connecting these responsibilities into a system the institution can understand, operate and extend. SPS owns the infrastructure, and its team carries the ongoing operational responsibility. That is the same sovereignty objective as the earlier work: local capability must grow as connectivity expands.

12

The next connection should reuse the institutional boundary

PAPSS gives the existing national payment architecture a continental connection while preserving the participant boundary. SIPS Connect continues to own participant adaptation; the gateway owns durable cross-border orchestration; the PAPSS adapter owns network-specific behavior; institutions retain the financial authority that belongs to them.

That separation makes future change more manageable. A PAPSS profile change should be assessed in its network boundary and mapped deliberately into the local contract. A new participant should be onboarded through the established integration model. A delayed callback should be diagnosed as delivery work. An uncertain payment should be investigated from its evidence.

For another payment operator evaluating a similar connection, those are the questions I would start with: who owns participant integration, who owns the network protocol, who can assert the financial outcome, and what evidence survives when the conversation breaks? Agree those boundaries before the first successful transfer becomes the architecture.

Field conclusion

Extend network reach through a dedicated adapter while preserving participant integration, financial authority and the institution's ability to understand the outcome.

Public evidence ledger

Inspect the basis for this note.

These links point to public implementation evidence or authoritative documentation used for the claims above. The interpretation is mine; institutional code and ownership remain with their respective owners.

  1. 01
    PAPSS payment and settlement model

    Official explanation of instant payment, prefunding and net settlement. This supports the network overview, not the qualification status of the SPS integration.

    Open source evidence
  2. 02
    PAPSS participation and connectivity

    Official participation models and connection responsibilities. Institution eligibility and settlement arrangements remain distinct from gateway message orchestration.

    Open source evidence
  3. 03
    SIPS Connect architecture and participant contract

    Version-pinned public README describing participant Core Banking adaptation, ISO 20022 orchestration and message protection. This is background for the preserved SIPS Connect boundary, not evidence of the PAPSS gateway’s certification.

    Open source evidence
  4. 04
    SIPS Connect financial safety controls

    Version-pinned documentation of identity reservation, duplicate control, replay and timeout recovery in SIPS Connect. The gateway recovery design described here remains the author’s implementation account.

    Open source evidence
  5. 05
    SIPS Connect inbound transaction handler

    Public participant-side transaction handling implementation. This illustrates the existing integration foundation; it is not the PAPSS gateway implementation.

    Open source evidence
  6. 06
    ISO 20022 message catalogue

    Official message definitions, including administrative requests/reports and payment lifecycle messages. The SPS information-service payloads are bilateral profiles, not universal PAPSS messages.

    Open source evidence
  7. 07
    The earlier sovereignty argument

    My independent essay on national control, institutional capability and replaceable integration boundaries. Its Mojaloop evaluation is separate from this PAPSS implementation.

    Open source evidence