Security
The concrete controls behind every escrow contract, described plainly, with no vague assurances.
Every contract is a double-entry ledger: money that enters escrow is recorded against a dedicated escrow account, and release or refund posts matching entries on both sides. Balances are never a single mutable number; every movement leaves a paired trail that must balance.
Each payout is created exactly once per release, enforced at the database level. Money-moving requests carry idempotency keys, so a retry can never double-charge or double-pay. Incoming payment webhooks are signature-verified, and amounts and currencies are checked for exact matches before a contract is marked funded.
Sellers uploading identity documents and a selfie are reviewed by our team, not an unreviewed algorithm. Verified accounts can transact above ₦10,000; unverified accounts are limited to that amount for creating, funding, and receiving payouts. The limit is enforced server-side, not in the app.
Card details never touch Saharix servers. Checkout is handled by licensed, PCI-compliant payment processors, and data in transit is encrypted with TLS.
Dispute resolutions, payout retries, and KYC decisions are performed through role-gated admin tools, and each action is written to an audit log with the actor, timestamps, and before-and-after state.
Delivery evidence, dispute files, and KYC documents are stored privately. They are streamed to verified deal parties and authorized staff only; never public URLs, never indexable.
Rate limits guard authentication, payments, and messaging. High-risk events can trigger manual review or temporary restrictions while we protect the parties involved.
Disputes, refunds, and the appeal process are documented in our Dispute Policy and Refund Policy.