Connected rails. Fiscal certainty.
RRA EBM 2.1 and mobile money, explored in a safe simulation.
Payment webhook
Payment success is not fiscal acceptance
Live rollout requires verified payment callbacks, duplicate-event protection, approved item codes and certified fiscal middleware.
API inspector
CIS initialization, fiscal response and payment events
/sandbox/rra/cis{
"sandbox": true,
"tin": "000000000",
"bhfId": "00",
"dvcSrlNo": "SIM-VSDC-001",
"cisName": "MoTa",
"cisVersion": "1.0-sandbox",
"cisSrlNo": "SIM-CIS-001",
"prcOrdCd": "01",
"sale": {
"receipt": "SIM-6F06125B",
"totAmt": 92347,
"taxAmt": 14086.83,
"items": [
{
"name": "Sale",
"quantity": 1,
"taxClass": "Standard",
"unitPrice": 92347
}
]
}
}Displayed paths are illustrative contracts, not callable production endpoints. Saved receipts remain simulated.
Integration specifications
Production gates, not live connections
RRA EBM 2.1
CIS approval, VSDC initialization and signed authority responses. Apply the approved item catalog and the 24-hour offline limit.
Payment lifecycle
Verify provider identity and amount. Deduplicate event IDs. Poll payment status if callbacks are missed. Fiscal acceptance is recorded separately.
Portable fiscal core
SQL aggregates and 500-row cursor exports. Rwanda-approved hosting and cross-border authorization must be established before live deployment.