A misspelled name on a certificate needs more than a quick text edit. The issuer needs to identify the right credential, confirm the requested spelling, choose the scope of the change, and check what the recipient can actually see afterward.<\/p>\n
This guide covers a single name-correction request for an already issued credential. It does not treat a correction as permission to change the achievement, issue another award, or update every record belonging to a person.<\/p>\n
Ask the recipient for the credential link, the name currently displayed, and the exact name they want displayed. Use your established participant record and correction policy to confirm that the request belongs to the right person and award. A similar name alone is not enough to select a record.<\/p>\n
Keep identity evidence in your approved private support process. Do not put supporting documents, private correspondence, or a history of former names on the public certificate. Request only the information your review actually needs.<\/p>\n
In Sertifier, recipients can submit a name-change request from their credential viewing page. The official recipient guide<\/a> describes signing into Verified, opening Help, selecting the name-change option, and sending the corrected name to the issuer for review. This submits a request; it does not establish that the correction has already been approved.<\/p>\n These are suggested operating checks, not a claim that the platform automatically makes these decisions for you.<\/p>\n Sertifier’s recipient editing guide<\/a> describes both general recipient profile editing and editing from a sent campaign’s Recipients step. It states that saved recipient updates appear on the live credential verification page and that an update notification can be chosen.<\/p>\n Read the current interface and guidance alongside the approved request. Do not assume that every profile edit affects only the certificate currently open. If the effect on other records is unclear, resolve that question before saving.<\/p>\n For a spreadsheet-based change across recipients, use the separate recipient import scope guide<\/a>. A bulk upload has different review needs from a single support request.<\/p>\n Consider a fictional support case. A sample credential displays Sample A<\/strong>, while the issuer’s approved participant record calls for S\u00e1mple A<\/strong>. The recipient points to that credential and requests the missing accent. The achievement and recipient are otherwise unchanged.<\/p>\n The names above are synthetic labels. In a real case, preserve the person’s approved spelling instead of replacing an unfamiliar character or abbreviating a name to make the design fit.<\/p>\n A saved form is the start of verification. Compare the live credential with the approved correction, then inspect a fresh download if your program distributes downloadable certificates. An older file already saved on someone’s device should not be assumed to update when the hosted record changes.<\/p>\nSeparate a spelling correction from a different request<\/h2>\n
\n
Choose the scope before changing the value<\/h2>\n
A worked example: one character needs correcting<\/h2>\n
\n
Check the result beyond the edit screen<\/h2>\n
\n