CHARGE_VERSION_MISMATCH
Charge changed since read: what the CHARGE_VERSION_MISMATCH error means and how to fix it.
HTTP 412. Problem type: https://docs.ovok.com/errors/charge-version-mismatch.
What this means
The charge changed since the version your If-Match header names, so your change was not applied over someone else's.
Troubleshooting
- Read the charge again (
GET /v1/patient-billing/charges/<chargeId>) and look at what changed. - Send your change again with
If-Match: W/"<version>"naming the version you just read.
Retry safely
Nothing was written. The same request fails again; send it with the current version.
If the problem persists
Share the HTTP status, problem type, request path, response timestamp and traceId with your administrator or support contact. Remove access tokens, provider secrets and patient data first. The Error responses guide explains the response fields, and the machine-code registry lists every endpoint-specific type.
Last updated on