Institution Adapter · FinTech
FinTech Adapter
The FinTech Adapter maps Open API-style transaction payloads, application context and authentication metadata into the common TRUST SDK request model. It provides a low-friction integration path for API-native digital financial services.
FinTech CDesign objective
Enable API-native FinTech platforms to integrate rapidly with TRUST while retaining one common downstream assessment contract.
Adapter Responsibilities
| Responsibility | Technical role |
|---|---|
| Open API mapping | Maps API-native payment payloads into the TRUST SDK request structure. |
| Application context | Preserves channel/application metadata useful for contextual assessment. |
| Authentication context | Passes relevant assurance indicators into the common request model. |
| Validation | Rejects malformed technical requests before downstream processing. |
| Canonical handoff | Provides a stable contract to the normalization and intelligence pipeline. |
Example Institution Payload
{
"payment_id": "FTC-005",
"app_id": "FINTECH-C",
"channel": "OPEN_API",
"amount": 12000,
"currency": "RWF",
"auth_method": "TOKEN",
"destination": "MERCHANT"
}
TRUST SDK Request Mapping
{
"transaction_id": "FTC-005",
"institution": "FinTech C",
"institution_type": "FINTECH",
"channel": "OPEN_API",
"authentication_strength": "TOKEN",
"amount": 12000,
"currency": "RWF",
"destination_type": "MERCHANT"
}
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 standardizes technical integration without claiming that every FinTech must use an identical internal data model. TRUST consumes the governed SDK contract, not the institution’s proprietary native schema.