Institution Adapter · Banking
Banking Adapter
The Banking Adapter maps bank-native transaction, account, authentication and channel context into the common TRUST SDK request model. Its role is to preserve the bank’s operational semantics while isolating downstream TRUST services from institution-specific field structures.
Bank ADesign objective
Enable a bank to integrate with one governed TRUST contract without forcing the bank to replace its native transaction schema.
Adapter Responsibilities
| Responsibility | Technical role |
|---|---|
| Field mapping | Maps bank-native transaction fields into TRUST SDK request fields. |
| Authentication context | Preserves channel and authentication-strength evidence used downstream. |
| Correlation | Maintains transaction identity across adapter, SDK, API and audit layers. |
| Validation | Checks required fields before the request enters the governed pipeline. |
| Canonical handoff | Ensures the downstream normalization stage receives a consistent integration contract. |
Example Institution Payload
{
"bank_txn_id": "BANKA-003",
"account_ref": "ACC-***",
"channel": "MOBILE_BANKING",
"amount": 25000,
"currency": "RWF",
"authentication": "STRONG",
"destination_country": "KE"
}
TRUST SDK Request Mapping
{
"transaction_id": "BANKA-003",
"institution": "Bank A",
"institution_type": "BANK",
"channel": "MOBILE_BANKING",
"authentication_strength": "STRONG",
"amount": 25000,
"currency": "RWF",
"destination_country": "KE"
}
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 does not make the trust decision. It performs controlled technical translation and validation. AI scoring, explanation and recommendation remain downstream, and the bank retains final transaction authority.