# UX/Ops validation checklist

Use before launch or major copy/process changes.

## UX quality

- [ ] each payment state has clear title/body/CTA
- [ ] pending states include wait window and next action
- [ ] failure states avoid ambiguous debit language
- [ ] success states show transaction references

## Customer trust

- [ ] no misleading "success" copy before final confirmation
- [ ] mandate consent details are explicit
- [ ] cancellation/pause path is visible and simple

## Support readiness

- [ ] support macros include reference IDs and expected timelines
- [ ] escalation triggers are explicit
- [ ] incident banners/messages are pre-approved

## Metrics and monitoring

- [ ] pending aging metric tracked
- [ ] support contact rate tracked by payment state
- [ ] refund SLA breach tracking active