1. Online checkout is configuration-dependent
Student E-page can start Paystack checkout only when the deployment has been explicitly configured for it. A payment is recorded as successful only after the server verifies the provider reference, amount and currency. Deployments with payments turned off do not collect money through the website.
2. Accepting a quote is not a payment
An itemised quote records the amount proposed for a request. A student can accept or decline it. Accepting a quote does not transfer money and does not create a receipt.
3. TEST payment records cannot be refunded
Admins can add clearly labelled TEST records to exercise the payment-centre workflow. A confirmed TEST record is still not proof of a real bank transaction, and changing or rejecting a TEST record does not move money.
4. Payments arranged outside this build
This page governs only the payment functionality inside the current Student E-page website. It does not verify, record or decide the terms of a separate cash, bank-transfer or other offline arrangement made outside this build.
If a real payment was made outside the site, use the agreed support channel for that transaction and keep the payment evidence. Do not rely on a TEST record as evidence.
5. Refund execution is not automated yet
The website can record a request as Refunded, but it does not currently call a provider refund API or promise a refund timeline. Any real refund decision still needs the business rules for refundable/non-refundable charges, cancellation timing, refund destination and dispute handling to be confirmed.
Until that workflow is implemented, contact support about a real Paystack transaction and keep the provider reference. The site does not invent refund terms that have not been approved.
Contact support