mojaloop→tazama

Payment Platform Adaptor

How a Mojaloop payment becomes a Tazama message

Tazama accepts exactly four ISO 20022 messages. None of them is a translation of a single Mojaloop message — each is assembled from a trigger plus several cached enrichment messages, across time. Some required fields are filled with constants because no Mojaloop message carries the value at all.

Every field, value and JSON payload here is transcribed from the DRPP golden-path capture and the schema-validated samples — nothing is reconstructed.

Open the mappingsSee the one with no gaps

The golden path — 18 messages, one payment

MWK 60 → ZMW 1 · cross-border via DRPP

  1. 01 · sdkPOST /transfers
  2. 02GET /parties
  3. 03PUT /parties
  4. 04 · sdkresp · await party
  5. 05 · sdkacceptParty
  6. 06POST /fxQuotes
  7. 07PUT /fxQuotes
  8. 08 · sdkresp · await conversion
  9. 09 · sdkacceptConversion
  10. 10POST /quotespain.001
  11. 11PUT /quotespain.013
  12. 12 · sdkresp · await quote
  13. 13 · sdkacceptQuote
  14. 14POST /fxTransfers
  15. 15PUT /fxTransfers
  16. 16POST /transfers · PREPAREpacs.008
  17. 17PUT /transfers · FULFILpacs.002
  18. 18 · sdkresp · COMPLETED
Triggers a Tazama messageRead as enrichmentNot consumed — 8 of these are SDK-private

The four ingestion schemas

pain.001

pain.001.001.11

← 10 POST /quotes

The quote request. Carries the payer's name components and merchant classification, which have no home in the pacs.008 — and has the most constant-filled required fields of the four.

42
mapped
3
sources
15
gaps

pain.013

pain.013.001.09

← 11 PUT /quotes/{id}

The quote response. Carries the payee-side economics — receive amount, fee and commission — which have no home anywhere in the pacs.008, and the real charge bearer that pain.001 could only guess at.

41
mapped
4
sources
11
gaps

pacs.008

pacs.008.001.10

← 16 POST /transfers

The payment itself. Emitted on transfer PREPARE so Tazama evaluates before settlement, and the only message carrying both currencies plus the rate that connects them.

38
mapped
5
sources
11
gaps

pacs.002

pacs.002.001.12

← 17 PUT /transfers/{id}

The outcome. The only one of the four with no class-A gaps — every required field resolves to a real Mojaloop value, two of them from HTTP headers rather than the body.

11
mapped
3
sources
0
gaps

“Gaps” counts required fields the real world has but Mojaloop never carries — class A below. The spread between pacs.002's zero and pain.001's fifteen is itself a finding.

How to read a mapping

Mojaloop fields sit on the left, grouped by the message they came from. The validated Tazama payload sits on the right. Arrows connect them. A field with no arrow is constant-filled — and there are five different reasons for that, only two of which are defects.

AData gapdefect

The real-world fact exists, but Mojaloop never carries it. The constant is a small untruth in the data.

BContract constant

Fixed by Tazama's ingestion contract, or structurally implied by Mojaloop. There is nothing to source.

CPPA-generated

An identifier or timestamp the PPA is meant to mint when the scheme supplies none.

DArrives after the triggerdefect

The value does exist in Mojaloop, but only in a message that follows the one that triggers emission.

EAbsent in this capture

A slot exists in the message; the golden path simply did not populate it. Another flow might.