AFRISWITCH

Architecture & HMAC Proxy

AfriSwitch relies on a secure institutional architecture based on an HMAC proxy that protects access to the internal API https://api.afriswitch.net/api/v1/. The enterprise portal acts as the orchestration, authentication and standardisation layer.

1. Overview


Client (Partner System / Postman)
        ↓
AfriSwitch Enterprise Portal (organisation authentication)
        ↓
HMAC Proxy (automatic signature)
        ↓
Institutional AfriSwitch API
        ↓
Institutional Response
        ↓
Portal (standardised formatting)
        ↓
Client

2. Role of the AfriSwitch Portal

3. The HMAC Proxy

The HMAC proxy is an internal component that signs all outgoing requests to the institutional API. Partners never need to generate any signature manually.

Internal service used:

call_institutional_api(
    portal_company=request.company,
    method="GET/POST",
    path="/api/v1/...",
    json_body=request.json_body,
    params=request.GET,
    use_hmac=True,
)

This service:

4. Response Structure (Portal)

{
  "status": 200,
  "data": {
    ...
  }
}

The data field contains the institutional response (sensitive values masked in the documentation).

5. Security

6. Testing & Validation

Conclusion

This architecture ensures a secure, scalable and institutional-grade integration for all AfriSwitch partners.