Crypto-Fiat P2P Exchange Platform
Budget: $3,000 – $5,000 USD
We are building a production-ready P2P exchange platform for trading local currencies and cryptocurrencies, inspired by platforms like Binance P2P and Paxful, but with custom workflows, strong security requirements, and a focus on fraud prevention.
The platform is web-only, and a complete Figma UI design is already available.
We are looking for an experienced backend-focused developer or team with proven P2P / escrow system experience.
This is not an MVP and not a simple CRUD project.
- Core Features (Must-Have)
P2P trading system:
Create ads
Start deals
Countdown timer
Auto-cancel if buyer does not act
Real-time chat inside each deal
Upload payment proofs (images / files)
Escrow-based trading (internal ledger system)
Deal status flow:
Pending → Paid → Confirmed → Cancelled → Disputed
Transaction history linked to chat & disputes
Scheduled & real-time notifications (WebSockets / Push)
Support / Dispute system with multi-stage resolution
- Escrow & Wallet Logic (Critical)
Sellers must deposit crypto into the platform wallet before creating ads
Buyers do not deposit funds
Platform uses an internal wallet/ledger system (NOT on-chain wallets per user)
Sellers can request withdrawals after deal completion
Platform fees are deducted from seller’s deposited crypto
Support for multiple cryptocurrencies and local currencies
- Security & Fraud Prevention (Mandatory)
The developer must have experience with:
Secure escrow flow design
Fraud scenarios (false payment claims, chargebacks, reversals)
Double-spending prevention
Race condition handling (no double deal execution)
Rate limiting
Audit logs
Admin override for disputes
KYC / AML integration (can be modular or phased)
Any solution that sacrifices security or performance for simplicity will be rejected.
- Dispute & Admin Panel
Disputes follow three stages:
Automated system checks
Automated escalation rules
Manual admin decision (final authority)
Admin panel must allow:
Viewing all deals & chats
Reviewing evidence
Overriding deal states
Logging every admin action (audit trail)
- Performance & Scalability
Initial user base may be small
Architecture must scale to hundreds of thousands of users
Real-time updates without page refresh
Strong concurrency handling
No two users can lock the same ad simultaneously
- Tech Stack (You Must Propose)
Please propose:
Backend framework (and why)
Real-time solution (WebSockets, etc.)
Database choice (and transaction handling strategy)
Security approach for escrow & disputes
We expect clear technical reasoning, not generic answers.
- What We Explicitly Reject
No-code / low-code platforms
Plugins or scripts that reduce security
Developers without real P2P exchange experience
Over-simplified escrow logic
“We’ll fix it later” approaches
- Deliverable
Fully functional production-ready web application
Clean, documented code
Secure architecture
Based strictly on provided Figma designs
- Required to Apply (Important)
To be considered, you must include:
Links or descriptions of previous P2P / escrow-based projects
A brief explanation of how you would:
Prevent double spending
Handle payment fraud
Manage race conditions
Answers to a short technical scenario (will be provided)
The platform is web-only, and a complete Figma UI design is already available.
We are looking for an experienced backend-focused developer or team with proven P2P / escrow system experience.
This is not an MVP and not a simple CRUD project.
- Core Features (Must-Have)
P2P trading system:
Create ads
Start deals
Countdown timer
Auto-cancel if buyer does not act
Real-time chat inside each deal
Upload payment proofs (images / files)
Escrow-based trading (internal ledger system)
Deal status flow:
Pending → Paid → Confirmed → Cancelled → Disputed
Transaction history linked to chat & disputes
Scheduled & real-time notifications (WebSockets / Push)
Support / Dispute system with multi-stage resolution
- Escrow & Wallet Logic (Critical)
Sellers must deposit crypto into the platform wallet before creating ads
Buyers do not deposit funds
Platform uses an internal wallet/ledger system (NOT on-chain wallets per user)
Sellers can request withdrawals after deal completion
Platform fees are deducted from seller’s deposited crypto
Support for multiple cryptocurrencies and local currencies
- Security & Fraud Prevention (Mandatory)
The developer must have experience with:
Secure escrow flow design
Fraud scenarios (false payment claims, chargebacks, reversals)
Double-spending prevention
Race condition handling (no double deal execution)
Rate limiting
Audit logs
Admin override for disputes
KYC / AML integration (can be modular or phased)
Any solution that sacrifices security or performance for simplicity will be rejected.
- Dispute & Admin Panel
Disputes follow three stages:
Automated system checks
Automated escalation rules
Manual admin decision (final authority)
Admin panel must allow:
Viewing all deals & chats
Reviewing evidence
Overriding deal states
Logging every admin action (audit trail)
- Performance & Scalability
Initial user base may be small
Architecture must scale to hundreds of thousands of users
Real-time updates without page refresh
Strong concurrency handling
No two users can lock the same ad simultaneously
- Tech Stack (You Must Propose)
Please propose:
Backend framework (and why)
Real-time solution (WebSockets, etc.)
Database choice (and transaction handling strategy)
Security approach for escrow & disputes
We expect clear technical reasoning, not generic answers.
- What We Explicitly Reject
No-code / low-code platforms
Plugins or scripts that reduce security
Developers without real P2P exchange experience
Over-simplified escrow logic
“We’ll fix it later” approaches
- Deliverable
Fully functional production-ready web application
Clean, documented code
Secure architecture
Based strictly on provided Figma designs
- Required to Apply (Important)
To be considered, you must include:
Links or descriptions of previous P2P / escrow-based projects
A brief explanation of how you would:
Prevent double spending
Handle payment fraud
Manage race conditions
Answers to a short technical scenario (will be provided)