Refunds should be structured and documented.
1. Open the target order and select refund.
2. Choose refund type (full, partial, or delivery component where available).
3. Enter required notes/reason.
4. Confirm refund submission.
Clear reasoning improves transparency and reduces repeated claims.
Use partial refunds for item-level or quality-specific issues.
1. Select affected items or amount.
2. Add notes describing scope.
3. Submit and verify reflected status.
Partial refunds are preferable when service was partially successful and only part of value is in dispute.
Disputes follow strict deadlines and evidence standards.
When a dispute opens:
1. Review reason code immediately.
2. Gather delivery proof, timestamps, and communication history.
3. Submit evidence before merchant response deadline.
4. Track case status through resolution.
Do not wait until final day. Late evidence can be excluded.
Strong evidence often includes:
- Delivery proof photo
- Delivery communication logs
- Item condition proof before dispatch
Weak or missing evidence substantially increases loss risk.
Dispute losses can trigger financial reversals.
Impacts may include:
- Transfer reversal/recovery from merchant transfer amounts
- Net payout reduction in current or upcoming cycle
- Operational flags for repeat risk patterns
Build repeatable proof-of-delivery habits to reduce these events.
If a dispute touches subscription charges, related subscription state can be affected.
Action steps:
1. Review disputed cycle details.
2. Verify customer communication and consent trail.
3. Coordinate with support on subscription continuity decision.
If fault is clear, proactive refunds can reduce chargeback risk and preserve merchant reputation.
Example error