Decentralised News · Editorial by Heath Muchena · Evidence reviewed 12 November 2026 · Edition 1.0
What Matters
A payment can start and finish in African currencies while institutions still settle a residual balance in hard currency. PAPSS’s published core process describes that arrangement; its separate African Currency Marketplace describes direct local-currency exchange. DN’s instrument separates currency roles and models gross versus net obligations. Neither product announcement establishes a live quote, an available route or autonomous-agent adoption.
DN Evidence Block
- Source review
- 12 November 2026.
- Primary evidence
- PAPSS operating descriptions and product announcements, Pesalink’s connectivity announcement, and central-bank publications.
- DN original
- DN Settlement Currency and Netting Scenario v1.0.0: a local currency-role record and exact arithmetic using reader-entered amounts.
- Established boundary
- Different products describe different settlement arrangements. The calculator illustrates a specified position; it does not observe PAPSS balances.
- Not measured
- No live transaction, executable FX quote, corridor availability test, liquidity benchmark or agent-payment adoption count.
Local currency is a useful claim only when its layer is named
For a business paying a supplier abroad, the immediate question is straightforward: what leaves our account, and what can the supplier spend? For a treasury team, there is a second question: what funding and settlement dependencies make that result possible? A favourable answer to the first does not settle the second.
DN’s thesis is that payment independence should be described through explicit currency roles, participants and obligations. A system can reduce a business’s need to source foreign currency without eliminating every foreign-currency dependency elsewhere. Conversely, an institution’s settlement arrangement does not necessarily require every customer payment to make the same currency journey.
This changes the evidence an analyst should request. Replace a general claim that a rail is independent with a record identifying the product, customer debit, beneficiary credit, funding arrangement and final inter-institution settlement. Then ask which parts have been demonstrated for the proposed transaction.
What the primary documents actually distinguish
| Claim to examine | Documented evidence | Decision boundary |
|---|---|---|
| Local-currency payments remove every hard-currency dependency. | PAPSS’s core description combines local customer payments, prefunding and hard-currency settlement of institutional net positions. [1] | Identify the layer before drawing a conclusion about currency dependence. |
| Every PAPSS product uses that same path. | The separate African Currency Marketplace launch describes direct local-currency trading and settlement. [2] | Keep the marketplace and the core payment service distinct. |
| A network connection proves our payment is available. | Pesalink announced a connectivity arrangement into its Kenyan network. [3] | Confirm the actual bank, direction, account, currency and transaction purpose. |
Core payments, prefunding and final settlement are different steps
The published core sequence credits customers in their local currencies, requires participants to arrange prefunding and describes a daily institutional settlement cycle. Its settlement instructions include a hard-currency leg through Afreximbank. The documentation therefore supports a specific architecture, rather than a blanket statement that all stages avoid hard currency. [1]
PAPSS’s explanatory leaflet also distinguishes central-bank and commercial-bank settlement models. In the latter, commercial banks take the relevant FX-funding role when the central bank does not provide it. A reader evaluating a route needs the applicable model and participant arrangements, rather than an assumption that every country has the same setup. [4]
Operationally, this makes prefunding a separate research question. Who supplies it? In which asset? Under what replenishment terms? Can the participant continue processing payments if that funding becomes scarce? Those questions remain material even where the payer never buys the settlement currency directly.
The African Currency Marketplace needs its own evidence row
The July 2025 marketplace launch reported that more than 80 corporates had transacted across 12 currency pairs during its pilot, with settlement in local currencies. It described permissioned-blockchain-capable infrastructure and direct currency exchange. Those are the operator’s dated pilot statements, not DN measurements of current volumes or available liquidity. [2]
The marketplace’s own site promotes direct currency matching and access through corporate, liquidity-provider and bank relationships. Its marketing numbers are not a substitute for an executable quote for a particular customer. [5] A treasury team should retain the actual pair, size, quote validity, charges, settlement instructions and counterparty conditions it is offered.
There is no need to force the two descriptions into a contradiction. They concern different services. The practical error would be applying a statement about the marketplace to every core payment, or using the core settlement description to deny that a specific direct-pair transaction can occur.
What netting changes: a worked example
Consider a hypothetical settlement participant with outgoing obligations of 2,000,000 and incoming obligations of 1,650,000, already expressed in the same comparison unit and settlement window. Gross two-way flow is 3,650,000. Subtracting incoming from outgoing leaves a net payable of 350,000.
The residual is approximately 9.59% of gross two-way flow. That ratio describes this arithmetic example. It is not a measured PAPSS funding reduction, fee saving or foreign-reserve saving. Changing the direction or timing of the incoming obligations changes the result. If the incoming amount falls to zero, the net payable becomes the entire outgoing amount.
Even a small end-of-window balance does not establish a small intraday funding need. Outgoing obligations might arrive before incoming funds become usable. Legal set-off might not be available between the relevant parties. A settlement service might require buffers or prefunding that are not captured by the final difference. The calculator deliberately keeps those operating questions outside its numerical result.
Use the DN Settlement Currency and Netting Scenario
Enter the currencies at the customer and settlement layers. For the arithmetic, enter both amounts in one comparison currency, at the same precision and for the same participant and period. Any FX conversion must have happened before entry and needs its own evidence. The instrument does not fetch rates or convert the payment currencies.
DN Settlement Currency and Netting Scenario v1.0.0
Currency-role labels and exact arithmetic from reader inputs; no live rates, provider availability, legal netting, prefunding estimate or fee saving.
Use non-sensitive aliases and references. This instrument makes no network requests and writes no browser storage. The downloaded JSON contains your inputs. Do not enter account credentials, wallet secrets or confidential documents. Defaults are illustrative scenarios.
Enter or review the example assumptions, then calculate. No measurement or live data has been loaded.
The export records the original entries, gross flow, net direction, absolute net amount and residual share. It also records whether the entered settlement currency differs from both customer currencies. That comparison is a property of your scenario, not a finding about a provider.
A route record needs more than a currency pair
| Record | Why it changes the decision |
|---|---|
| Product and transaction purpose | Payment execution and currency exchange can involve different services and conditions. |
| Originating and receiving institutions | A country-level announcement does not identify the institutions handling this instruction. |
| Debit and credit currency | These determine the customer’s visible funding and usable receipt. |
| Institutional funding and settlement currency | These reveal dependencies behind the customer experience. |
| Quote timestamp and expiry | A documented price can stop being executable before approval. |
| Beneficiary availability and exception process | Receipt, access, rejection and return are separate operational questions. |
The February 2026 Pesalink announcement identifies a technical connectivity role and describes incoming cross-border access to banks and mobile-money operators in its network. It is useful evidence of an integration, but it does not publish a guaranteed quote or universal account eligibility for every reader. [3]
There is also historical transaction evidence rather than only roadmap language: the Bank of Ghana’s 2023 oversight report records a supplier payment initiated in cedi with a Nigerian recipient receiving naira. That confirms the reported event, not the current availability or price of every Ghana–Nigeria route. [6]
Regional infrastructure does not imply one currency model
The Central Bank of Kenya’s payment-system description distinguishes EAPS transactions in East African local currencies from REPSS transfers through local RTGS arrangements in US dollars and euros. The regional label therefore does not establish which money a service uses. Read each arrangement on its own terms and verify current operational details with the participant. [7]
The same discipline applies to proposed connections with stablecoins or CBDCs. Adding a tokenised asset, API or automated agent changes part of a workflow; it does not by itself replace the issuer, settlement obligation or redemption terms. DN’s money-interoperability evidence record examines those separate monetary claims.
Where an agent can help without inventing payment authority
A useful research agent can assemble the route record, compare the same fields across providers and alert a treasury operator when an approved quote expires. It can flag a changed beneficiary or a mismatch between the requested credit currency and the offered one. Each task has an inspectable input and an explicit output.
The agent should preserve uncertainty. An unspecified settlement currency remains unknown. A pilot announcement stays a pilot observation. An unavailable bank-level quote cannot be replaced by a promotional average. These rules make the record useful for approval because the operator can see which facts still need confirmation.
Execution authority needs its own controls. DN’s cross-border agent workflow separates route research from permission to move funds. If the selected route changes after approval, retain the new route and review the affected controls, as described in the payment-route change record.
Decision table: what can you conclude?
| Evidence available | Supported conclusion | Still unresolved |
|---|---|---|
| Product description only | A specified service is described by its operator. | Your eligibility, price and execution. |
| Dated pilot statement | The operator reports activity in that pilot. | Current capacity and wider adoption. |
| Matched quote and approval | A particular proposed instruction can be reviewed. | Completion and usable beneficiary receipt. |
| Transaction and reconciliation evidence | That transaction’s observed outcome can be analysed. | Performance across a representative sample. |
| Calculator output | The entered obligations have a reproducible arithmetic relationship. | Legal netting rights, liquidity and actual settlement obligations. |
Methodology and limits
DN reviewed the listed primary materials on 12 November 2026 and compared this scope with the full body of its existing cross-border agent article. The new contribution is currency-layer analysis and netting arithmetic, not another remittance cost ranking.
The tool calculates gross flow as outgoing plus incoming and net position as outgoing minus incoming. Monetary arithmetic uses integer smallest units at the selected precision. The displayed residual percentage rounds to two decimal places; it is null when gross flow is zero. No prefunding, fees, default probability or legal set-off benefit is inferred.
All examples are hypothetical. The source review is a dated snapshot, not an automatic update feed. Future changes in settlement models, participant access, product naming or primary operating descriptions require editorial review. Unsupported adoption and performance fields must remain unknown.
Frequently asked questions
Does a local-currency payment mean the dollar is absent everywhere?
No such conclusion follows from the customer endpoints alone. Identify the funding and settlement currencies of the specific service and participant arrangement.
Are core PAPSS payments and the African Currency Marketplace interchangeable?
They are separately described services. Preserve the product name in the record rather than combining their features into one universal route.
Does the 9.59% example show a 90.41% saving?
It shows only the residual share of two-way flow in the stated scenario. It does not measure costs, required liquidity, reserve use or a saving achieved by a real participant.
Can I enter outgoing cedi and incoming naira directly?
No. The calculator requires a common comparison unit. Convert through a justified, dated method outside the tool, then retain that reference. Different currency amounts cannot simply be subtracted.
Does this demonstrate AI-agent adoption?
No. The reviewed sources support payment and exchange mechanisms. They do not establish a counted population of autonomous agents transacting through them.
Can the instrument execute a payment?
No. It performs local calculations and exports your scenario. It has no bank connection, wallet connection, payment authority or live-rate service.
Corrections and changelog
Send a correction with the article title, affected statement and a dated primary reference to press@decentralised.news. Use redacted references; do not send account credentials or private payment records. Version 1.0.0, 12 November 2026: initial primary-source review and local instrument. The original continent-wide agent-adoption map remains unmeasured.
Primary sources
- PAPSS: core payment, prefunding and settlement processes.
- PAPSS: African Currency Marketplace launch, 7 July 2025.
- Pesalink: PAPSS connectivity announcement, February 2026.
- PAPSS: payment and settlement-model leaflet.
- PAPSS African Currency Marketplace: operator product description.
- Bank of Ghana: Payment Systems Oversight Annual Report 2023.
- Central Bank of Kenya: national and regional payment-system descriptions.
Published schema and illustrative record
The schema documents this instrument’s JSON format. The example below contains constructed illustrative inputs and outputs; it is not a provider measurement, verified case or live dataset. The instrument above creates a separate record from the inputs you choose. These resources do not establish an API or an automatic monitoring service.
JSON Schema — dn.settlement-currency-netting.v1
Schema version 1.0.0. The schema identifier is a versioned reference, not an asserted network endpoint.
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "urn:dn:settlement-currency-netting:v1",
"title": "DN Settlement Currency and Netting Scenario record v1",
"type": "object",
"additionalProperties": false,
"required": [
"schemaId",
"schemaVersion",
"instrument",
"recordType",
"createdAt",
"sourceReviewDate",
"inputs",
"outputs",
"assumptions",
"limits"
],
"properties": {
"schemaId": {
"const": "dn.settlement-currency-netting.v1"
},
"schemaVersion": {
"const": "1.0.0"
},
"instrument": {
"const": "DN Settlement Currency and Netting Scenario"
},
"recordType": {
"const": "reader_entered_scenario"
},
"createdAt": {
"type": "string",
"format": "date-time",
"pattern": "^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}\\.\\d{3}Z$"
},
"sourceReviewDate": {
"const": "2026-11-12"
},
"inputs": {
"type": "object",
"additionalProperties": false,
"required": [
"alias",
"serviceModel",
"debitCurrency",
"creditCurrency",
"fundingCurrency",
"settlementCurrency",
"comparisonUnit",
"precision",
"outgoing",
"incoming",
"sourceRef"
],
"properties": {
"alias": {
"type": "string",
"maxLength": 120,
"minLength": 1
},
"serviceModel": {
"type": "string",
"enum": [
"papss_core",
"papss_acm",
"other_or_unspecified"
]
},
"debitCurrency": {
"type": "string",
"maxLength": 12,
"pattern": "^[A-Z]{3,12}$"
},
"creditCurrency": {
"type": "string",
"maxLength": 12,
"pattern": "^[A-Z]{3,12}$"
},
"fundingCurrency": {
"type": "string",
"maxLength": 12,
"pattern": "^[A-Z]{3,12}$"
},
"settlementCurrency": {
"type": "string",
"maxLength": 12,
"pattern": "^[A-Z]{3,12}$"
},
"comparisonUnit": {
"type": "string",
"maxLength": 32,
"minLength": 1
},
"precision": {
"type": "integer",
"minimum": 0,
"maximum": 18
},
"outgoing": {
"type": "string",
"pattern": "^(0|[1-9]\\d*)(\\.\\d+)?$",
"maxLength": 70
},
"incoming": {
"type": "string",
"pattern": "^(0|[1-9]\\d*)(\\.\\d+)?$",
"maxLength": 70
},
"sourceRef": {
"type": "string",
"maxLength": 240
}
}
},
"outputs": {
"type": "object",
"additionalProperties": false,
"required": [
"grossTwoWayFlow",
"netPayable",
"netReceivable",
"absoluteNet",
"pairedGrossOffset",
"netDirection",
"residualGrossPercent",
"settlementLabelDiffersFromBothCustomerLabels",
"comparisonLabelDiffersFromSettlementLabel"
],
"properties": {
"grossTwoWayFlow": {
"type": "string",
"pattern": "^(0|[1-9]\\d*)(\\.\\d+)?$",
"maxLength": 70
},
"netPayable": {
"type": "string",
"pattern": "^(0|[1-9]\\d*)(\\.\\d+)?$",
"maxLength": 70
},
"netReceivable": {
"type": "string",
"pattern": "^(0|[1-9]\\d*)(\\.\\d+)?$",
"maxLength": 70
},
"absoluteNet": {
"type": "string",
"pattern": "^(0|[1-9]\\d*)(\\.\\d+)?$",
"maxLength": 70
},
"pairedGrossOffset": {
"type": "string",
"pattern": "^(0|[1-9]\\d*)(\\.\\d+)?$",
"maxLength": 70
},
"netDirection": {
"enum": [
"pay",
"receive",
"flat"
]
},
"residualGrossPercent": {
"anyOf": [
{
"type": "string",
"pattern": "^(0|[1-9]\\d*)(\\.\\d+)?$",
"maxLength": 70
},
{
"type": "null"
}
]
},
"settlementLabelDiffersFromBothCustomerLabels": {
"type": [
"boolean",
"null"
]
},
"comparisonLabelDiffersFromSettlementLabel": {
"type": "boolean"
}
}
},
"assumptions": {
"type": "array",
"minItems": 4,
"maxItems": 6,
"items": {
"type": "string"
}
},
"limits": {
"type": "object",
"additionalProperties": false,
"required": [
"networkMetricsMeasured",
"fxRatesFetched",
"legalNettingEstablished",
"prefundRequirementEstimated",
"feeSavingEstablished"
],
"properties": {
"networkMetricsMeasured": {
"const": false
},
"fxRatesFetched": {
"const": false
},
"legalNettingEstablished": {
"const": false
},
"prefundRequirementEstimated": {
"const": false
},
"feeSavingEstablished": {
"const": false
}
}
}
}
}Illustrative example JSON record
This fixed example is published for inspection and integration testing. Its record timestamp is not an evidence-verification timestamp.
{
"schemaId": "dn.settlement-currency-netting.v1",
"schemaVersion": "1.0.0",
"instrument": "DN Settlement Currency and Netting Scenario",
"recordType": "reader_entered_scenario",
"createdAt": "2026-11-12T12:00:00.000Z",
"sourceReviewDate": "2026-11-12",
"inputs": {
"alias": "example-same-window",
"serviceModel": "papss_core",
"debitCurrency": "GHS",
"creditCurrency": "NGN",
"fundingCurrency": "GHS",
"settlementCurrency": "USD",
"comparisonUnit": "USD",
"precision": 2,
"outgoing": "2000000.00",
"incoming": "1650000.00",
"sourceRef": "Illustrative arithmetic; not observed PAPSS flows"
},
"outputs": {
"grossTwoWayFlow": "3650000.00",
"netPayable": "350000.00",
"netReceivable": "0.00",
"absoluteNet": "350000.00",
"pairedGrossOffset": "3300000.00",
"netDirection": "pay",
"residualGrossPercent": "9.59",
"settlementLabelDiffersFromBothCustomerLabels": true,
"comparisonLabelDiffersFromSettlementLabel": false
},
"assumptions": [
"All amounts use the same comparison unit, participant and settlement window.",
"Any FX conversion occurred outside this tool and is not verified.",
"Integer smallest-unit arithmetic; residual percentage rounded half up to two decimals.",
"Currency-label comparisons describe entered labels only."
],
"limits": {
"networkMetricsMeasured": false,
"fxRatesFetched": false,
"legalNettingEstablished": false,
"prefundRequirementEstimated": false,
"feeSavingEstablished": false
}
}
