Four wallets opened automatically when you sign up. Convert between them at admin-managed rates.
How it works
Send across borders with escrow protection built in.
Most cross-border transfers ask you to choose between speed and safety. Thagbiz Trust gives you both, in the same flow: instant payment when the recipient is verified, or protected escrow when work needs to be delivered before money releases.
funded → awaiting_release → released, refunded, or disputed. No reversals once a state lands.
From light identity to source-of-funds. Limits scale with your verification depth.
Every case stays attached to the transaction. Compliance reviews evidence before any state change.
1/5A REAL EXAMPLE
What a protected payment actually looks like
Skip the abstract diagrams. Here's the same flow a Thagbiz Trust user walks through when paying a freelancer in another country.
The scenarioOlu, in London, needs to pay Amara, a designer in Lagos, ₦750,000 for a brand pack.
Amara wants to see the money is real before starting. Olu wants to know the work ships before funds leave for good. Protected escrow handles both, and every state below corresponds to a row in the ledger.
1
Olu sends ₦750,000Olu funds the escrow from his NGN wallet. Funds leave his available balance and move to reserved.
draft2
Amara sees the secured fundsAmara sees the protected payment in her dashboard. She can confirm completion, but cannot withdraw until release.
funded3
Amara marks the work doneAmara delivers the brand pack and marks the work complete. The release moves to Olu for approval.
awaiting_release4
Olu releases the paymentOlu approves. The funds move from reserved to Amara's wallet, fully released. Ledger entry recorded.
released2/5ESCROW LIFECYCLE
Five states. Forward-only. Auditable.
Every protected payment moves through exactly these states. No state is reversed, no state is skipped. That's what makes the ledger trustworthy in disputes.
Sender's wallet debits to reserved. Recipient can see protected funds but cannot withdraw.
Recipient marked work complete. Now waits for the sender to approve the release.
Sender approved. Funds move from reserved into recipient's available balance.
Either party initiated and both agreed. Funds return from reserved to sender's available.
Either party opened a case. Compliance reviews evidence before any release or refund.
3/5VERIFICATION LEVELS
Your limits scale with your verification
Thagbiz Trust uses four KYC levels. Each level unlocks more of the product. Verification is never gated on the client. Every limit and every block is enforced at the API on each action.
LevelWhat it unlocksWhat you submitPer-transaction limit
Level 0
Not verifiedAccount created. You can sign in and explore the dashboard, but deposits, escrow, and withdrawals are blocked until you start verification.
Sign-up details onlyView only. Money operations blocked.Level 1
BasicAnchored identity: we confirm your Nigerian BVN or NIN against the issuing authority through Youverify. Unlocks low-value send and receive.
BVN or NIN$500 deposit / $200 payout per transactionLevel 2
StandardGovernment ID plus a selfie liveness check. Matches your face against the document and confirms a real person is on the device.
Driver's licence, voter's card, or passport + active liveness$5,000 deposit / $2,500 payout per transactionLevel 3
EnhancedAddress verification and an AML / PEP / sanctions screen. Required for the higher transaction caps and for business corridors.
Proof of address + AML screening$50,000 deposit / $25,000 payout per transaction4/5WHAT YOUVERIFY ACTUALLY DOES
Every identity decision is a real API call to Youverify, recorded as its own check.
We do not run identity checks ourselves. Each verification step is a server-to-server call to Youverify, the result is stored as a VerificationCheck row, and your KYC level only moves up when the relevant checks succeed. Anything ambiguous is held for a compliance admin to look at, not auto-passed.
CheckWhat Youverify confirmsHow it runs in our flowUsed at
BVN lookupThat the Nigerian Bank Verification Number you submit belongs to you and is currently linked to your full name and date of birth.POST /kyc/checks/bvn. Youverify returns a hash of the matched identity record. We persist the outcome as a VerificationCheck row and advance your KYC level on success.L1
NIN lookupSame as BVN but against the National Identification Number registry. Used when a user does not have a BVN.POST /kyc/checks/nin. Same persisted-check pattern as BVN.L1
Government ID documentThat the driver's licence, voter's card, or passport you upload is genuine and that the photo matches the holder named on the document.POST /kyc/checks/drivers-license, /passport, or /voters-card. We send the document image to Youverify, store the structured response, and trigger a face match against your liveness selfie.L2
Active livenessThat a real person, not a photo or a deepfake video, is on the camera in this session. Required so the Level 2 document match has a trustworthy reference selfie.We mint a session token through POST /kyc/checks/liveness, hand it to the Youverify Web SDK (mobile uses the native iOS / Android SDK with the same API). The SDK runs head-turn and blink prompts on-device, then posts the captured clip to Youverify. Our webhook records the outcome.L2
Address verificationThat the residential or business address you provided is real, reachable, and traceable to you.POST /kyc/checks/address. Youverify schedules the verification with a local agent network and posts the result back to us as a webhook event we mark the check succeeded or failed on.L3
AML / PEP screeningThat you are not on sanctions lists, politically-exposed-persons watchlists, or adverse-media databases that would block you from regulated payments.POST /kyc/checks/aml. Youverify runs your name against global watchlists and returns a structured match set. Any hit is held in the compliance review queue, not auto-passed.L3
5/5WHEN SOMETHING GOES WRONG
Disputes, support, and release decisions stay attached to the original payment.
Dispute resolutionCompliance reviewed
Either party can open a dispute. The escrow moves to disputed and the funds stay reserved.
- Both sides upload evidence (messages, deliverables, receipts) directly into the case.
- A compliance admin reviews and decides release, refund, or partial split.
- Every action is logged in AdminAction records with the reviewing admin's identity.
- The original transaction stays referenced. The case never floats free of its payment.
Support continuitySame thread, same context
Open a support ticket from inside the dashboard and the agent already sees your transaction.
- Tickets stay linked to the wallet, escrow, or transaction you opened them against.
- Compliance, operations, finance, and support each handle their own queue. No generic inbox.
- If a support thread needs to escalate to a formal dispute, the history travels with it.
- Status changes (response, resolution, escalation) emit notifications in-app.
READYOPEN AN ACCOUNT