Student-Level Payment Model
All payments in Lynk are:
Created for a specific student
Independent of batches
Independent of organisations
Persistent even if a student moves between batches or coaches
This ensures:
One clear payment record per student
No duplicate or conflicting payment requests
Stability when operational structures change
Batches are used only for session delivery, not billing.
Who Can Request Payments
When an organisation exists, only the admin is allowed to request payments from students.
Admin:
Can view all students
Can request payments for any student
Manages payment follow-ups
Ensures consistent billing across the academy
Coach:
Cannot request payments for students tagged to an organisation batch
Can seek payments only for students tagged to their own self created batches
Focuses only on sessions, attendance, and notes
This separation prevents payment confusion and protects students from mixed communication.
What Organisations Do Not Change
Even when operating under an organisation:
Payments are not batch-based
Payments are not organisation-owned
Payments do not move when batches change
Payments remain tied to the student record
The organisation only defines who has permission to act, not where payments live.
Why Lynk Is Designed This Way
Lynk uses a student-centric payment model to:
Support students attending multiple batches
Avoid billing breaks during batch or coach changes
Maintain clean, long-term payment history
Reflect real academy workflows
This keeps payments simple, predictable, and durable.
Summary
Payments in Lynk are always student-level
Batches and organisations do not own payments
Only admins can request payments when an organisation exists
Coaches never handle payments
Student payment records remain stable across operational changes