Update Cardholder Data

Correct the personal data of a cardholder that has not been approved yet and — when it is in submission_failed — resubmit it in one call.

Use this when the provider rejected the submission because of the data itself (a mistyped ID number, a phone already used by another cardholder, a non-ASCII address). The description field of the cardholder carries the reason.

Only the fields present in the body are changed; everything else is kept. The values are written to the linked user's meta — the source of truth the submission rebuilds from — so a later POST /v1/users/{id}/cardholder sees the same corrected data.

Allowed while the cardholder is in submission_failed, reject, rejected_by_admin or pending_review. An approved cardholder (pass_audit) or one under review at the provider cannot be edited.

For submission_failed the submission workflow is started again right away (same as POST /v1/cardholders/{id}/retry) and the response comes back with status wait_audit; the provider's decision arrives through the usual cardholder webhook. In the other statuses the data is stored and the cardholder keeps its status — submit it with POST /v1/cardholders/{id}/submit once it is reviewed.

KYC documents are not part of this call: re-upload them with POST /v1/users/{id}/kyc/documents (the newest non-rejected document per slot is used) before resubmitting.