Institution Adapter · Mobile Money
Mobile Money Adapter
The Mobile Money Adapter maps wallet transaction, subscriber, agent/channel and authentication context into the same TRUST SDK request contract used by other ecosystem participants. This supports interoperability without forcing the mobile-money platform to expose a banking-style native schema.
Mobile Money BDesign objective
Allow a mobile-money operator to use the same governed TRUST assessment service while preserving mobile-money-specific transaction and channel semantics.
Adapter Responsibilities
| Responsibility | Technical role |
|---|---|
| Wallet transaction mapping | Maps mobile-money transaction identifiers and wallet context into the SDK contract. |
| Channel context | Preserves app, USSD, agent or API channel characteristics where available. |
| Subscriber/device context | Transfers relevant pseudonymized identity/device evidence downstream. |
| Validation | Checks required fields before SDK submission. |
| Canonical handoff | Produces a technically consistent request for the normalization layer. |
Example Institution Payload
{
"wallet_txn_id": "MMB-004",
"wallet_ref": "WALLET-***",
"channel": "USSD",
"amount": 18000,
"currency": "RWF",
"auth_level": "LIMITED",
"destination_network": "EXTERNAL"
}
TRUST SDK Request Mapping
{
"transaction_id": "MMB-004",
"institution": "Mobile Money B",
"institution_type": "MOBILE_MONEY",
"channel": "USSD",
"authentication_strength": "LIMITED",
"amount": 18000,
"currency": "RWF",
"destination_network": "EXTERNAL"
}
Where this adapter fits
InstitutionNative transaction and channel context.
AdapterSchema mapping and validation.
TRUST SDKCommon governed request contract.
API GatewayControlled technical entry point.
Canonical ModelCommon transaction representation downstream.
Governance & Integration Boundary
The adapter is an interoperability boundary, not a replacement for the operator’s existing fraud, AML/CFT or transaction-control systems. TRUST remains advisory.