Limitation - Refunds Workflow

- Refunds are not implemented as an automated workflow
- Refunds are done by a Pay API admin outside STRR.
- `REFUNDED` Payment Status exists in API
- Need to check as fees might not be refundable by policy
- Audit/compliance expectations - do we need payment history trail in STRR?

Start by reviewing how STRR integrates with the Pay API and where payment status values, including REFUNDED, are represented. Confirm whether refunds should be automated, whether fees are refundable under policy, and what audit history compliance requires; done means these requirements are resolved into an agreed workflow.

Written by the indexing model from the issue text.