Revision
- Specific comments
- Revision
- Resubmission
STEP-BY-STEP GUIDE
How a safe deal works
From agreeing terms to bank-confirmed payout, refund or dispute resolution.
Who can participate
- Individual
- Self-employed person
- Sole proprietor
- Legal entity
- Company representative
- Employer and employee only under an approved employment Country Pack
STATE MACHINE
Main deal journey
- 01Create request
- 02Agree terms
- 03Contract
- 04Funding
- 05Execution
- 06Submit deliverable
- 07Acceptance
- 08Payout
- 09Completion
When revision or a dispute is required
Dispute
- Open dispute
- Decision
- Payout / partial payout / refund
DETAILS
Detailed mechanisms
Safe dealPROF.MIR manages the deal record while the bank or payment partner manages funds.
Verified state changes
Funding, payout and refund states require provider evidence and server-side checks.
ContractsImmutable versions bind parties, terms, applicable countries and SHA-256.
Approval is version-specific
An in-app approval does not replace a legally required electronic signature.
Payment and fundingFunding is confirmed by the financial provider, never by a user toggle.
Provider is the source of truth
The UI reports funds only in connection with a specific deal and verified bank events.
Performing the workStages, evidence and deliverables stay in the deal history.
Keep evidence
Store specifications, files, reports, acts and versioned outcomes with the deal.
AcceptanceThe customer records full acceptance, partial acceptance or specific revision comments.
Use specific criteria
Acceptance and comments must refer to the agreed scope and evidence.
PayoutsPayout starts after acceptance and finishes only after bank confirmation.
Server checks first
Contract, funding, deliverable, act, dispute status, amount and legal gates are rechecked.
RefundsA refund follows a separate provider-confirmed and reconciled flow.
Provider confirmation is final
A requested refund is not complete until its verified financial event is reconciled.
DisputesA dispute records deal-specific disagreement and pauses automatic payout.
Dispute is not a complaint
A dispute concerns party obligations; a complaint concerns conduct or a platform decision.
PROF.MIR feesServer-calculated fees are shown in advance and snapshotted for each deal.
No retroactive change
A new tariff does not alter the fee snapshot of an existing deal.
DocumentsPersonal, public, deal and legal documents have different access rules.
Private by default
Identity documents are not published automatically and deal documents remain deal-bound.
Deal chatA closed participant chat keeps messages, safe attachments and read receipts.
Auditable history
Messages are not silently rewritten; moderation remains recorded and permission-bound.
Country PacksCountry Packs govern legal and operational feature availability.
Separate capabilities
Discovery, contracts, payments, signatures and employment are released separately.
International workMultiple countries and legal links may apply to one deal.
Record each connection
Citizenship, residence, registration and place of performance must not be treated as the same field.
EmploymentEmployment remains separate from services and requires an approved country flow.
Do not disguise employment
Mandatory employment rules cannot be avoided by labeling the relationship as a service.
SecurityNever disclose passwords, payment credentials or authentication secrets.
Secrets stay private
Do not share passwords, PIN, CVV, MFA/SMS codes, bank login or API secrets in deal chat.
Example deal history
- Deal created
- Terms agreed
- Contract created
- Contract approved
- Funding confirmed
- Work started
- Deliverable submitted
- Comments or acceptance
- Resubmission when required
- Payout confirmed
- Deal completed
Example bank events
- Payment created
- Funds received
- Funds confirmed
- Funds reserved
- Payout allowed
- Payout completed
- Refund created
- Refund completed