A refund is one click, and never automatic

When a customer asks to cancel, Arxos does everything except the part that matters. It matches the request to the order on file, checks that the message came from the email on that order, calculates the exact refund from the platform, and writes the reply the customer will get. Then it stops.

The founder sees one card: who, which order, how much, and why. One click approves it, and the refund and the reply go out together. One click declines it, and Arxos drafts a different answer instead.

We could automate the click. The verification is deterministic, the amount comes straight from the platform, and the reply is already written. But a refund is money leaving your business, and a system that moves money on its own has to be perfect, not good. No model is perfect.

So the line is drawn where it belongs: Arxos does the work, you make the call. Down the road, founders will set their own caps, say, auto-approve anything under twenty dollars. That will be a founder loosening the rule for their own store, on purpose. The default never changes: money moves when a person says so.