Process & Escrow Guide
Indian Compliance Version — Rev 2026.1
Jifwa is a transaction-safeguarding technology application that replaces insecure verbal contracts and chasing invoices with an objective, consensus-driven milestone verification model. Here is exactly how we protect both buyers and sellers:
1. The Peer Consensus Workflow
Milestone Consensus Drafting
The buyer (client) and seller (contractor/agency) collaboratively draft the project milestones directly in their Jifwa workspace. Each milestone must have clear, objective deliverables and a dedicated value.
Secure Milestone Locking
Before the seller initiates development, the buyer secures the milestone funds. The funds are isolated instantly in the secure Jifwa Vault, indicating absolute commitment and proof of liquidity.
🔒 INR Routing: Fast local bank deposit via NEFT, IMPS, RTGS or UPI under strict compliance.
Milestone Execution & Claim
Knowing that the money is 100% locked and guaranteed, the seller completes the work. The seller then uploads concrete completion proof (e.g., GitHub commit, staging URL, e-way bill, sign-off sheet) to the milestone portal and triggers the "Claim Completion" command.
Consensus Verification & Payout
The buyer reviews the uploaded evidence. Once verified, the buyer clicks "Approve & Release". Jifwa instantly routes the locked funds directly to the seller's verified bank account without billing delays.
2. Detailed State Machine Transitions
Every milestone transitions through highly controlled, secure, logical states to prevent unauthorized movement of funds or unilateral contract breaches:
| State | Description | Allowed Commands |
|---|---|---|
| DRAFT | Terms are being defined by both parties. No payment has been committed. | EDIT_TERMS, SIGN_AGREEMENT |
| LOCKED | Funds are isolated in Jifwa Vault. Secure lock active. | CLAIM_COMPLETION, DISPUTE_FREEZE |
| SUBMITTED | Deliverables have been submitted. Under review by buyer. | APPROVE_RELEASE, REQUEST_REVISION, FREEZE |
| RELEASED | Funds have left Jifwa Vault into Seller bank account. | None (Terminal State) |
| DISPUTED | Milestone locked due to disagreement. Team notified. | MEDIATE_SETTLE, UNILATERAL_RELEASE |
3. Cryptographic Verification & Security Protocols
Jifwa secures data integrity and contract consensus using enterprise cryptographic and architectural practices:
- Unalterable Consensus Signatures: Every action — milestone creation, contract signatures, locking actions, and release confirmations — is cryptographically logged with strict tenant authentication checks.
- PCI-DSS Level 1 Compliance: Secure routing is backed by PCI-DSS Level 1 payment processors, utilizing end-to-end tokenization. Jifwa never reads or stores raw bank details or card numbers.
- Automatic Vault Isolation: Locked milestone funds are assigned dedicated tracking tokens in specialized corporate vault accounts. No pooling or cross-usage of transactional capital is permitted.
4. Objective Verification Guidelines
To prevent delays and ensure mutual satisfaction, Jifwa recommends that both parties adhere to the following strict verification guidelines:
Ensure each milestone specifies exactly how it can be tested or verified. For example, "Site must score above 90 on Google Lighthouse" or "Delivery of source code on a public GitHub repository".
In case of minor revisions, document them directly in your project log. This ensures that if Jifwa support is called to mediate, our specialists have access to an accurate context log.
Ready to learn more?
Read our detailed Buyers & Sellers Manual to see how we protect each party specifically, or learn about our founders on our corporate About Us page.