d-bis/proxmox
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
main
proxmox/docs/03-deployment/DBIS_MOJALOOP_INTEGRATION_STATUS.md
defiQUG dfe81767e3
All checks were successful
Deploy to Phoenix / deploy (push) Successful in 5s
Details
Add DBIS RTGS integration decision artifacts
2026-03-28 23:44:30 -07:00

2.5 KiB
Raw Permalink Blame History

DBIS Mojaloop Integration Status

Last updated: 2026-03-28
Purpose: Record the current status of Mojaloop in the DBIS RTGS program so that the architecture does not imply a live switch integration that has not yet been evidenced in the repository or current environment.

Current conclusion

Mojaloop is in scope as a target payments interoperability layer, but it is not yet evidenced as a live, repo-backed DBIS integration path in this workspace.

What is currently available

  • DBIS / OMNL / Fineract operator scripts and documentation
  • HYBX sidecar repositories
  • Chain 138 settlement baseline
  • RTGS planning artifacts that mention Mojaloop as a required integration category

What is not yet evidenced

  • live Mojaloop switch endpoint URLs
  • live auth / credential model
  • callback contract for transfer state changes
  • quote / transfer / settlement-window payload mapping
  • a repo-backed Mojaloop runbook in this workspace
  • a confirmed mapping from Mojaloop transfer lifecycle to:
    • Fineract posting
    • HYBX sidecar orchestration
    • Chain 138 settlement confirmation

Required inputs before implementation

  1. Exact Mojaloop environment(s) available to HYBX / DBIS
  2. Endpoint list:
    • quotes
    • transfers
    • parties
    • callbacks / notifications
    • settlement or hub-side reporting endpoints
  3. Auth model:
    • mTLS
    • bearer/token
    • header and signature requirements
  4. Canonical settlement semantics:
    • prefunded or net settlement
    • window / batch behavior
    • reversal rules
  5. Event ownership:
    • which system is source of truth for transfer state
    • which system triggers on-chain settlement

Decision rule

Until the above is available, Mojaloop should be treated as:

  • Planned in the RTGS matrix
  • not yet a production blocker for the narrowest non-Mojaloop RTGS slice
  • a production blocker for any RTGS claim that explicitly includes Mojaloop interoperability

Next implementation steps

  1. Obtain the exact Mojaloop endpoint and auth contract currently available to HYBX.
  2. Create a DBIS/HYBX Mojaloop integration runbook in this repo.
  3. Freeze the message mapping between Mojaloop events and:
    • Fineract / OMNL journal events
    • HYBX sidecar events
    • Chain 138 settlement events
  4. Add a testable production gate row once a real endpoint contract exists.

Related artifacts

Reference in New Issue View Git Blame Copy Permalink