Payments
Connected providers and workflows
Connect payments, messages, email, webhooks, and approved external systems.
EduIntels integrations help school workflows move beyond manual re-entry. Connect supported providers, verify transactions, deliver communication, process callbacks, and exchange approved data more reliably.
Payment gateways SMS and email Approved APIs
Payments
Flutterwave
SMS
Termii
SMS
Twilio
Email
SMTP
Custom
Approved API
Provider-readyConfigure supported payment and messaging services.
Webhook-awareReceive and verify external transaction events.
TraceableRecord provider status, responses, attempts, and failures.
ExtensibleScope approved custom connections when justified.
Available integration areas
Connect the providers that complete your school workflows.
Each integration has its own credentials, charges, approval rules, limits, security requirements, and implementation responsibilities.
Provider availability may change. Credentials should be stored and managed carefully, with test-mode validation before live transactions or messages are enabled.
Payment gateway
Paystack
Create payment links, initialise transactions, verify references, process callbacks, and validate signed webhook events.
Payment gateway
Flutterwave
Support hosted payments, transaction verification, callback handling, webhook validation, and finance status updates.
SMS provider
Termii
Send configured SMS messages using approved sender details, channels, provider credentials, and delivery responses.
SMS provider
Twilio
Use account credentials and an approved sending number for outbound SMS where the provider and destination support it.
Email delivery
SMTP Email
Connect an approved mail server for transactional messages, templates, result delivery, reports, and operational communication.
Scoped integration
Custom APIs
Connect approved external services after security, ownership, data mapping, frequency, support, and failure recovery are agreed.
Data onboarding
Imports
Bring approved spreadsheet records into controlled import workflows with validation, row-level feedback, and audit history.
Data portability
Exports
Generate reports, documents, result files, and approved exports for leadership, records, or downstream use.
Operational extension
Devices and verification
Support ID-card verification, output files, and device-ready workflows where the required hardware and integration are agreed.
Controlled data movement
Move information through a verified integration path.
A reliable integration should know what initiated the request, what the provider returned, whether the response is authentic, what changed, and how failures will be handled.
Live integration is enabled only after credentials, test transactions, callback URLs, security checks, and operational ownership have been confirmed.
EduIntels workflow
Invoice, message, report, import, or approved request.
Integration control
Credentials, validation, payload, reference, and logging.
External provider
Gateway, SMS, SMTP, device, file, or approved API.
Payment integration
Verify payment before updating the school’s finance records.
Payment integration should not depend only on a browser redirect. EduIntels can initialise provider transactions, retain references, process callbacks, verify provider status, record gateway events, and generate downstream finance documents when payment is confirmed.
Payment links
Generate controlled links connected to the relevant invoice and expected amount.
Transaction verification
Confirm provider status using the saved reference before treating the payment as successful.
Webhook validation
Check provider signatures or secrets and reject unauthenticated events.
Event history
Record attempts, provider payloads, processing state, failures, and final outcomes.
Receipt workflow
Prepare official receipt and finance-document records after successful verification.
Implementation checklist
Clarify ownership before enabling any provider.
| Decision | Questions to resolve | Typical owner |
|---|---|---|
| Provider selection | Which gateway, SMS provider, email service, device, or external platform will be used? | School leadership and implementation team |
| Credentials | Who owns the account, keeps the secret keys, approves changes, and rotates access? | Authorised administrator |
| Charges and limits | What are the transaction fees, SMS costs, rate limits, sender rules, or service restrictions? | School finance and provider |
| Data mapping | Which records and fields move in each direction, and which system remains the source of truth? | Process owner and technical team |
| Failure handling | Who reviews failed messages, rejected webhooks, unmatched payments, duplicate events, or unavailable providers? | Named operational owner |
| Testing and go-live | Which test cases must pass before live credentials and production callbacks are enabled? | Implementation team |
Integration questions
Know the scope, cost, and responsibility before connection.
Which payment gateways can EduIntels connect to?
The current payment integration layer supports Paystack and Flutterwave configuration for payment links, transaction verification, callbacks, and signed webhook processing.
Which SMS providers are supported?
EduIntels includes configurable support for Termii and Twilio in its messaging layer. Provider availability, sender approval, pricing, and delivery rules remain subject to the provider.
Can the school use its own email server?
Yes. SMTP settings can be configured for school or platform email delivery, subject to valid host, port, authentication, encryption, sender, and provider limits.
Can EduIntels connect to another system through an API?
Approved custom API work can be scoped after the external system, authentication method, required data, frequency, ownership, security, and failure-handling requirements are understood.
Are third-party charges included in the EduIntels subscription?
Usually not. Payment transaction fees, SMS units, email-provider costs, devices, and external platform charges are generally billed by the relevant provider or quoted separately.
How are webhook events protected?
Provider callbacks can use signature or secret verification, event recording, duplicate detection, processing status, and controlled transaction verification before finance records are updated.
Connect what your school actually uses
Plan integrations around real workflows, not a long provider list.
Tell us which payment gateways, SMS provider, email system, devices, data sources, or external applications your school needs to connect. We will confirm feasibility, security, scope, cost, and rollout requirements.