Issues
1
open problems
Refund / replacement proof
If an order has a problem, FAEDA shows what proof exists, what remedy is possible, and what still needs review before refund or replacement is final.
Customer safety rule
This page can prepare a final proof note. It cannot move money, send stock, assign rider, release settlement, credit wallet, or punish anyone by itself.
Issues
open problems
Proof notes
saved reviews
Replace
item path
Refund
partner proof
Current status
Select an approved issue packet, choose replacement or refund, then create a remedy completion certificate packet.
Step 1
Refund or replacement starts from a real issue, not from a random button.
Step 2
Receipt evidence
Handover proof should carry OTP/photo/QR, timestamp, actor, location, and confirmation.
Delivery evidence
Dispatch route, pickup actor, ETA, and failed-attempt reason stay linked.
Payment evidence
Partner-powered payment intent or COD evidence is only an evidence source.
Step 3
Both branch requirements
The selected branch below becomes the active certificate path, but both required chains are always visible for review.
Replacement chain
Refund chain
Shop + support
Replacement item, quantity, condition, freshness, and packing proof are recorded before dispatch.
Blocked here
No stock ledger movement, no customer charge, no silent substitution.
Dispatch checker
Pickup actor, ETA, route, masked contact, and proof requirement must be approved.
Blocked here
No rider dispatch without dispatch gate and human approval.
Customer + rider/shop
OTP, photo, QR, timestamp, actor, location hint, and customer confirmation close the replacement delivery proof.
Blocked here
Proof alone does not post ledger, release settlement, or apply final trust penalty.
Step 4
This reviewer label goes into the closure certificate packet.
Runtime locks
Connected steps