Supabase platform
HisabERP uses Supabase for authenticated application access and its PostgreSQL data foundation.
Supported scope- Session-based authentication
- PostgreSQL application data
- Organization-scoped access model
HisabERP integrations
Know what works today, what needs configuration and what is still planned.
The directory uses explicit statuses so an authentication button, callback route or roadmap item is never presented as a fully activated production integration without the required provider setup.
Connection directory
A transparent register of the current integration surface.
Provider credentials, commercial agreements and production validation remain separate from the existence of an application path.
Email and magic-link access
Users can access HisabERP with email and password or request a password-free magic sign-in link.
Supported scope- Email sign-in
- Email registration
- Password reset
- Magic-link authentication
Google sign-in
The application includes the Google OAuth sign-in path for organizations that prefer managed identity access.
Supported scope- Google OAuth entry
- Redirect back to the requested workspace
- Existing-account authentication flow
Apple sign-in
The application includes an Apple OAuth sign-in path for deployments that configure the provider.
Supported scope- Apple OAuth entry
- Redirect back to the requested workspace
- Existing-account authentication flow
telebirr reconciliation callbacks
HisabERP can receive token-protected telebirr callback events and normalize them into the reconciliation workflow.
Supported scope- Provider callback endpoint
- ETB transaction normalization
- Transaction, order and payer references
- Organization source mapping
M-PESA Daraja reconciliation callbacks
HisabERP can receive M-PESA Daraja callback events and normalize receipt, amount, phone and order references for reconciliation.
Supported scope- Daraja callback endpoint
- Receipt and checkout references
- Amount and phone normalization
- Token validation
Audit CSV export
MFA-verified administrators can export enabled business, authentication and security-alert evidence as spreadsheet-safe CSV.
Supported scope- Business audit export
- Authentication audit export
- Security-alert evidence
- Defined reporting window
External monitoring webhook
Structured server errors can be forwarded from the deployment to an external monitoring endpoint.
Supported scope- Structured error forwarding
- Deployment-level logging
- Operational alert integration
Public REST API
A documented customer-facing API for approved business records is planned for a future platform phase.
Supported scope- Scoped API access
- Documented resources
- Token and permission model
Business event webhooks
General outbound events for invoices, payments, inventory and customer records are planned.
Supported scope- Signed event delivery
- Retry handling
- Subscription management
Bank feeds
Direct institution feeds are a roadmap item and will depend on supported bank interfaces and commercial agreements.
Supported scope- Statement ingestion
- Transaction matching
- Reconciliation assistance
Ecommerce connectors
Connectors for online storefront orders, products and customer records are planned for a later integration phase.
Supported scope- Order import
- Product synchronization
- Customer mapping
Production readiness path
An integration becomes “Available” only after the complete path is verified.
Confirm the business use case
Define the exact records, provider events, teams and reconciliation outcome required.
Configure credentials safely
Store provider secrets in deployment configuration rather than source code or browser-visible settings.
Validate provider behavior
Test signatures, tokens, payload variations, duplicate events, failures and recovery handling.
Control production rollout
Document ownership, monitoring, support escalation and the status shown to customers.
Need another connection?
Submit an integration requestDescribe the workflow—not only the provider name.
Share the source system, records involved, expected direction, update frequency, authentication method and business outcome. HisabTech can then assess whether the work belongs in configuration, a controlled beta or the product roadmap.