Define a measurable outcome
Record scope, price, timing, stages, evidence and acceptance criteria before funding.
PROF.MIR LEARNING CENTRE
Help centre
Step-by-step guidance for profiles, deals, contracts, funding, deliverables, payouts and disputes.
Open the safe-deal guideROLE-AWARE HELP
Choose your role
KNOWLEDGE BASE
Help centre sections
Getting startedCreate a profile, choose the correct role and check country availability.
Create a verified profile
Use factual identity, country and legal-status information, then follow the applicable moderation flow.
For customersA guided journey from a request to acceptance or dispute.
Define a measurable outcome
Record scope, price, timing, stages, evidence and acceptance criteria before funding.
For providersA journey from a published profile to a bank-confirmed payout.
Work only after confirmation
Review the contract and wait for confirmed funding before starting a protected stage.
For companiesOrganizations act through verified representatives with limited permissions.
Separate responsibilities
Managers, lawyers, accountants and authorized signers receive only the access required for their work.
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.
Service statusTechnical availability does not release legal or financial capabilities.
Check the real mode
Server-side configuration determines whether the financial flow is SANDBOX or production.
FAQ
Frequently asked questions
When is the provider paid?
After acceptance, required document and legal checks, and bank-confirmed payout.
Can the customer cancel a payout?
Not arbitrarily; the contract, deal state, acceptance, disputes and submitted bank instructions control the outcome.
Where are the funds?
They remain in the applicable bank or payment-provider flow, not in an arbitrary PROF.MIR wallet.
What is a Country Pack?
A versioned set of country-specific rules and release gates for contracts, payments, documents, signatures and employment.
What does SANDBOX mean?
It is a test financial mode and does not prove real funds movement.
Why can a user not mark a deal paid?
Only verified provider events can establish a real financial state.
What is contract SHA-256?
It is a digest of the exact contract version; any content change produces a different value.
Can an agreed contract be edited?
No. Changed terms create a new immutable version.
Can a repeated click send two payouts?
Idempotency protection binds retries to the existing command.
Who can see the deal chat?
Active deal participants, authorized representatives and specifically assigned moderators.
Which data must never be sent in chat?
Passwords, PIN, CVV, MFA/SMS codes, bank logins, API secrets and private keys.
How is a complaint different from a dispute?
A dispute concerns party obligations in a deal; a complaint concerns conduct, content or a platform decision.