Role, payout and activity approvals

This is the subscription-payment control point. Paystack payments are provider-confirmed automatically when the Paystack transaction is successfully verified. Manual Transfer payments remain pending until Super Admin reviews the proof and chooses Approve Payment or Reject Payment. After an approved payment, use Assign Tally to place the paid member into the correct FIFO tally queue.

Approve a request to issue a controlled registration link tied permanently to the requesting Agent or Vendor. Successful subscription payments through an approved link create the 10% commission ledger entry for that referrer.

Review the four required qualifications. Location-admin applications are approved through the hierarchy and finalized by Super Admin. A location is rechecked at final approval so no duplicate location administrator can be created.

Default is MANUAL. Turn automation on only after end-to-end testing. Paystack transfers use the Paystack balance and verified bank recipients; this package does not claim to debit a bank account directly.

A payout is created only when its port threshold is reached. Super Admin approval is required before execution. The next port is not credited until the approved payout is actually recorded as executed.

Use this to confirm whether the server accepted verification messages. An accepted PHP mail request does not by itself guarantee inbox delivery; SMTP/provider configuration may be required on AfeesHost.

This queue is live and scoped to the signed-in administrator. Registration submissions remain visible even when email delivery has failed. Payment submissions are shown in the Manual transfer approvals section below.