Surfaces, roles and current terminology

Permissions, settings and activation

• If Admin offline payment pages show Feature not activated, activate via Activations / https://soq.edu.sg before operational use.
• Match paid amount, payer name, and reference before approving.
• Approval should grant the purchased entitlement once; avoid duplicate approvals.
• Rejection should tell the learner what evidence to resubmit.

Core workflows

Prepare the module

1. Open Financial ? Offline Payments at the configured Admin URL.
2. If the page is a Feature not activated stub, stop and activate the module first.
3. Confirm bank instructions shown to learners are accurate.
4. Run a test submission only after the working UI is available.

Approve a real payment

1. Open the pending offline request and compare amount, reference, and receipt.
2. Approve only when evidence matches the order.
3. Confirm the learner gains course or product access.
4. File the request under history and keep the external bank proof.

Result states

• Success: Evidence matches, approval posts once, and the learner can access the purchase.
• Pending: The request awaits staff review or clearer payment evidence.
• Denied: The module is inactive, evidence mismatches, or the staff role cannot approve.
• Error: Stub UI, duplicate credit risk, or save failure; do not approve until the module and evidence are sound.

Operational notes

• Current Admin offline payment views may be Feature not activated stubs — document that status honestly to operators.

Related guides

• Cart Checkout and Payments
• Sales List
• Activation
• Payment Gateways