Verified student identity
Students verify a recognised school email or submit student identification for manual review. Verification confirms the evidence reviewed; it is not a guarantee of future conduct or work quality.
See how identity, agreements, payments, work approval, and disputes are handled—and what remains in beta.
Current product status
Public product beta
USDC settlement uses Solana Devnet test assets. Local NGN funding is integrated, but local payout is not yet enabled. CampusGig does not currently offer regulated escrow.
Students verify a recognised school email or submit student identification for manual review. Verification confirms the evidence reviewed; it is not a guarantee of future conduct or work quality.
The selected student and client accept the same written scope, amount, and deadline before funding. Later edits create a new version that both sides must accept again.
CampusGig records verified provider or network evidence before a contract becomes active. Payment state changes happen on the server and are written to an audit trail.
Either party can open a documented dispute. Release is frozen while the case is open, and administrators can review the agreement, conversation, delivery, and payment evidence.
Payment model
Flutterwave creates a transaction-specific virtual account. CampusGig validates the webhook and independently verifies the transaction reference, currency, status, and amount before marking the gig funded. Local payout and refund automation are still restricted.
The current beta uses test USDC and a CampusGig-controlled signer. A program-controlled vault exists in source form but is not deployed or independently audited. Never send real or mainnet assets to a beta wallet address.
Report a concern
Do not send more money or move the conversation off-platform. Save the gig ID, usernames, messages, payment reference, and any transaction signature. Open a dispute from the contract page for an active gig; use support for account access or security issues.