A protected service order is simple in principle: payment is verified before the work is treated as funded, and creator earnings do not become withdrawable just because the buyer clicked pay.
1. The buyer agrees to a clear scope
The package or accepted offer should state the price, delivery expectations, revisions and what is included. That agreement becomes part of the transaction record.
2. Payment is processed and verified
Sira currently uses Chapa for payment processing. Once the payment is verified, the order moves into Sira's funded service flow. The creator can see that the order is real and paid, but service earnings are not yet available to withdraw.
3. Work and communication stay attached to the order
Keep important instructions, files, changes and delivery messages inside the order thread whenever possible. If a dispute happens later, the order record matters far more than a private promise made somewhere else.
4. The creator delivers
The buyer can review the submitted work. If revisions are still available, the buyer can request them. If the issue cannot be resolved normally, either side can use the dispute flow while the order is still in a disputable state.
5. Completion changes the wallet state
When the order is completed or resolved in the creator's favour, the service payout is recorded into the creator's unified wallet according to the transaction's fee rules.
What Sira protection does not cover
If you move the payment outside Sira, the platform cannot apply its funded-order, release and dispute controls to that direct payment. Keeping payment and the critical order record on-platform is what gives the system something concrete to protect.