Backend-created checkout
Payment requests will be created by the secured cloud backend. Provider secrets will never be embedded in the mobile app.
Online school-fee payments
Indelo will separate payment-provider confirmation from official campus posting. The school's ledger, cashbook, receipt numbering, reversal practice, and audit trail remain authoritative.
Payment finality
A parent will see clear status while a payment moves from checkout through provider verification, campus posting, and official receipt publication.
Payment requests will be created by the secured cloud backend. Provider secrets will never be embedded in the mobile app.
The backend will verify provider status, amount, currency, reference, tenant, campus, and duplicate state.
A verified payment becomes a controlled command that the campus applies through Indelo financial rules.
Idempotency and unique business constraints prevent duplicate financial posting and duplicate receipt issuance.
Operations will distinguish verified, queued, delivered, posted, mismatched, refunded, reversed, and review-required transactions.
Planned initial integration is Flutterwave for supported Nigerian payment methods, using CABS's established webhook-routing discipline.
When the campus is offline
The app may show: Payment confirmed by provider. Posting to the school's Indelo ledger is pending.
It will not claim that an official school receipt exists until the campus applies the transaction and publishes the receipt.
Payments readiness
The pilot review covers fee-account quality, receipt rules, provider readiness, reconciliation ownership, refund authority, and campus connectivity.