payments

Shopkeepers want to know where their money is, in their language, without opening a dashboard. Start with answers that need no permission, add one-tap confirmed actions, and keep refunds and credit behind explicit approval.

A principal-level design question with money, regulation, fraud and a dozen languages in one queue. The answer that scores separates complaint types by what the agent may do, and keeps every money decision in deterministic systems.

Delegated spending needs a mandate the user sets, limits enforced outside the model, merchant and price checks, and a clean way to undo. Decide where confirmation stays.

Agent checkout protocols keep the merchant as merchant of record, but disputes and customer ownership move. Integrate one protocol through your payment provider, start small and price the risk.