Manual Payment
Manual Payment APIs and webhooks live under Student because manual payments are recorded against an existing student.
Institutes can add offline payments in the Jodo Dashboard, or your system can record them through the Student payment APIs. Use direct payment webhooks to keep your ERP or accounting system updated when a payment is added, updated, or cancelled outside the online payment flow.
How it Works
Section titled “How it Works”- An offline payment is collected by the institute.
- A user records the payment in the Jodo Dashboard with the student, amount, date, and reference details.
- Jodo stores the payment as part of the student’s payment history.
- Jodo sends webhook events when the dashboard record is added, updated, or cancelled.
- Your ERP or reconciliation system consumes those updates and reflects the change in its ledger.
When to Use this Integration
Section titled “When to Use this Integration”- Your institute records offline collections in the Jodo Dashboard.
- Finance teams need dashboard-entered bank transfers, cheques, or cash payments to appear in the ERP.
- Your ERP should receive updates when a manual payment is corrected or cancelled in Jodo.
- Your reconciliation process needs a consistent record of online collections and dashboard-entered manual payments.
Reconciliation Guidance
Section titled “Reconciliation Guidance”Treat manual payment webhooks as updates from Jodo Dashboard. Store the Jodo payment identifier, amount, status, reference number, and timestamp in your system.
If your system receives the same webhook more than once, process it idempotently. Use the payment identifier and event type to avoid duplicate ledger entries.
Webhooks
Section titled “Webhooks”Subscribe to these events to keep your ERP or finance system in sync with manual payment activity in Jodo Dashboard.