SOLUTIONS · FREELANCE SERVICES
Protected checkout for freelance work.
For design, writing, development, marketing, consulting, and other service projects, ArosaPay safeguards milestone payments before release and ties settlement to the agreed deliverable, client confirmation, review window, or dispute outcome.
Payment safeguarded before work begins · Released after confirmation · Review path if contested
MILESTONE STATE
THE PROBLEM
Why freelance work needs clearer release rules
Freelance projects often fail because scope, delivery, revision limits, and payment timing are not recorded in one trusted transaction.
Client concerns
- ·Work may not match the agreed scope
- ·The freelancer may delay or disappear
- ·Deliverables may be incomplete
- ·Revision expectations may be unclear
- ·Payment may move before the outcome is accepted
Freelancer concerns
- ·Client may delay approval after receiving the work
- ·Scope may expand without new payment terms
- ·Revision requests may become open-ended
- ·Payment confirmation may be unclear
- ·Project evidence may be scattered across messages and files
ArosaPay does not replace a contract, project manager, or freelance marketplace. It gives both sides a structured transaction record, release condition, evidence trail, and review path.
HOW IT WORKS
How protected checkout works for freelance milestones
01
Define the milestone
Client and freelancer agree on the scope, deliverable, amount, release condition, review window, and revision expectations.
02
Payment is safeguarded
The client pays through the protected checkout flow. Payment is attached to the milestone transaction and is not released yet.
03
Freelancer delivers
The freelancer submits the agreed deliverable or completion evidence through the supported workflow.
04
Client reviews
The client reviews the deliverable against the agreed milestone terms.
05
Confirm or report an issue
If the work is accepted, the client confirms. If there is a problem, the transaction moves into review before release, refund, or partial resolution.
Confirmation moves the transaction toward release according to the approved settlement process.
FEATURES
Built for freelance milestones where scope matters
Milestone transaction record
Scope, amount, deliverable, release condition, status, and outcome stay attached to one transaction.
Condition-based release
Payment releases only after client confirmation, review window expiry, or another agreed milestone condition.
Revision expectations
Revision limits or review expectations can be recorded in the milestone terms where supported.
Evidence-ready review
Deliverables, messages, documents, screenshots, or completion proof may be attached if review is needed.
Client confidence
The client can fund the milestone without releasing payment before the agreed outcome.
Freelancer confidence
The freelancer can see that payment has been safeguarded before beginning the agreed work.
PRICING
Standard freelance pricing
Custom pricing may apply for approved service platforms, agencies, enterprise merchants, high-value projects, or risk-adjusted milestone flows.
- Standard fee
- 2.9% + KES 30
- Minimum fee
- KES 100
- Charged on
- Completed transactions only
Unlike freelance marketplaces, ArosaPay does not need to own the talent marketplace. It provides a protected checkout and settlement workflow that can sit alongside direct client-freelancer relationships or approved service platforms.
View full pricingCOMPARISON
Freelance marketplace vs protected checkout
Freelance marketplace
- ·Owns discovery and profiles
- ·May charge marketplace fees
- ·Controls the work relationship
ArosaPay protected checkout
- ·Safeguards payment against a transaction record
- ·Records release conditions
- ·Supports confirmation and review
- ·Can support direct client-freelancer or platform-led flows
REVIEW PATH
Review path if a milestone is contested
If a client or freelancer reports a problem, release pauses while evidence is reviewed. Evidence may be requested from either party before release, refund, or partial resolution.
Possible review reasons
- ·Deliverable not submitted
- ·Deliverable differs from agreed scope
- ·Milestone quality contested
- ·Revision expectations contested
- ·Client non-response
- ·Freelancer non-response
- ·Project cancellation
- ·Other issue requiring review
FREELANCERS
Freelancer profiles and limits
ArosaPay may apply transaction limits, review windows, additional checks, or custom settlement rules based on:
Freelancer profile
Project value
Service category
Risk history
Approved agreement
Approved freelancers, agencies, or platforms can see applicable limits and settlement rules during onboarding or in their agreement.
EXAMPLE SCENARIOS
Illustrative freelance milestone scenarios
These are examples, not customer testimonials.
Example
Website design
A client and designer agree on a landing page milestone, delivery date, and revision expectations. Payment is safeguarded before work begins and released after confirmation.
Example
Content project
A writer delivers a batch of articles against an agreed scope. The client confirms accepted deliverables or reports an issue for review.
Example
Development milestone
A developer completes a feature milestone. If the client disputes the output, evidence is reviewed against the milestone record before release, refund, or partial resolution.
FOR DEVELOPERS
Webhook events
Developers can receive signed events for material milestone state changes where enabled for approved freelance or service-platform integrations.
- transaction.funds_safeguarded
- transaction.milestone_submitted
- transaction.client_confirmed
- transaction.revision_requested
- transaction.under_review
- transaction.settlement_released
- transaction.refunded
- transaction.partial_resolution
FAQ
Frequently asked questions
Freelance payments with clearer release rules.
Payment is safeguarded against a milestone record. Release follows client confirmation, agreed review window, or dispute resolution.
Standard pricing: 2.9% + KES 30, minimum KES 100, charged on completed transactions only. Custom pricing may apply for approved service platforms and enterprise flows.