Security & Escrow
Last updated 14 August 2026
This page is how Tent actually moves money and identity data — escrow, ledger, KYC, and access control — not a generic security brochure.
Escrow before delivery
Campaign and offer funds leave available balance and sit in escrow until proof is approved, the 72-hour window ends, or an admin resolves a dispute.
Paystack rails
Top-ups, bank-account verification, and withdrawals run through Paystack. Tent never stores raw card numbers. NGN and USD wallets are separate.
Identity before cash-out
Creator withdrawals require Smile ID verification (NIN/BVN) and a Paystack-verified bank account. Blacklisted or strike-capped accounts cannot withdraw.
Dispute-safe by default
Either side can open a dispute while escrow is locked. Funds do not move until an admin releases or refunds them.
Escrow lifecycle
1. Advertiser funds a campaign or accepted offer. Tent deducts available balance, credits escrow, and writes a ledger row. Starter plans also pay the 5% platform fee at this step.
2. The creator delivers in the deal room and submits proof. Escrow stays locked while the advertiser reviews or requests revisions.
3. On approval — or after the 72-hour auto-release window if no dispute is opened — the creator is credited (80% of the agreed payout). Unclaimed slots and lost disputes refund the advertiser.
What we protect
Wallet balances cannot be edited from the client. Money movement goes through server-side RPCs with row-level security. Paystack webhooks are verified with HMAC. Sensitive admin actions (disputes, strikes, manual wallet adjustments) require an Admin role. Rate limits sit in front of auth and money endpoints.
KYC and full bank details are not rendered to other users and are not written to application logs. Social "Verified by Tent" badges are admin reviews of a handle, not OAuth tokens from the social network.
Reporting a concern
Suspected fraud, a compromised account, or a security issue: security@usetent.co. We investigate before any manual wallet action is taken.