Integrations¶
Payment gateways and third-party/cross-service integration contracts.
| Doc | Covers |
|---|---|
| Payment Workflow | The hub: invoice-first pattern, shared pay page, intent creation/initiation — read this first regardless of which gateway you're integrating. |
| M-Pesa (Daraja) Reference | Safaricom Daraja API technical reference (STK push, B2C, config tiers). |
| Paystack Reference | Paystack API technical reference (transactions, transfers, settlements). |
| Paystack Callback Page | The frontend contract for the public Paystack redirect-callback page. |
| PayHero Reference | PayHero Africa (API 2.0.0): tenant accounts and Teams, channel routing, M-Pesa and cross-border mobile money, card and bank, offline paybill, callbacks, wallet payouts and KYC. |
| Notifications REST API | How non-Go services (TruLoad/.NET, ERP/Python) send notifications without NATS. |
| Finance Integration Map | How each service's events post into treasury's general ledger. |
| eTIMS API — External Integrator Quickstart | For companies integrating KRA eTIMS fiscalization directly against our API, outside the full Codevertex SaaS suite. |
| Email Hosting | Per-mailbox hosted email plans and pricing for tenants — not a developer API. |
| Developer Portal — Current State & Roadmap | What's ecosystem-wide vs. eTIMS-specific in the credential/environment/certification/rate-limit pattern, and what's still roadmapped. |