Authentication errors ask me to reconnect

1. Given HMRC access has expired or been revoked
2. When PlayPay checks obligations or submits data
3. Then the message tells me to reconnect HMRC
4. And the app does not treat the failure as a successful no-obligations state

Validation errors point to data that must be fixed

1. Given HMRC rejects a submission with a validation error
2. When the result is shown
3. Then PlayPay marks the submission as failed
4. And the message explains that the data must be corrected
5. And the app does not automatically retry the same invalid payload

Duplicate or closed obligation responses are not generic failures

1. Given HMRC says the obligation is closed or already submitted
2. When the result is shown
3. Then PlayPay identifies the non-retryable HMRC outcome
4. And it prevents another submission for the same closed period

Service outages are retryable

1. Given HMRC is unavailable or returns a retryable server error
2. When submission fails
3. Then PlayPay keeps the draft pending
4. And the message tells me to retry later
5. And recovery can sync queued submission logs

Published error coverage uses named scenarios

1. Given HMRC error handling is published in capabilities
2. When I review the error page
3. Then each supported error path has a named outcome
4. And no supported path is documented only as a generic failed state