What Transaction Type values should we map from Mojaloop (e.g., PPA) to Tazama’s expected format (e.g., "WITHDRAWAL")?
What Transaction Type values should we map from Mojaloop (e.g., PPA) to Tazama’s expected format (e.g., "WITHDRAWAL")?
Mapping is not required. The Mojaloop FSPIOP specification defines the Mojaloop transaction types and enumerates them in descriptive terms. The specific values are catalogued as such in the Mojaloop-specific v4.0.0 configuration for Rule-078. These values are not mapped to ISO20022 equivalents: the default ISO20022-based configuration for Rule-078 carries the ISO20022 values. In Tazama, Rule-078 evaluates the value contained in the transaction message, whatever it is, from whichever schema it originates, in the value's own right and according to the rule configuration. There is no inter-schema mapping, per se, and the only place where the specific value then matters is the mapping between the value and the rule result band, and then downstream between the rule result band and a specific typology weighting according to a typology configuration. Design note: this value-to-band-to-weighting mapping for a "categorical variable" is an approach from Tazama's primal design and these values (and values like it) should be moved to the Event-Director for interrogation and up-front model (typology) sub-division. Source: Tazama Head of Product, August 2026.