> ## Documentation Index
> Fetch the complete documentation index at: https://docs.myfundingmachine.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Review an identity name difference

> Confirm that a verified Stripe identity belongs to the onboarding contact when the names differ.

An Operator may use a nickname in the CRM while Stripe verifies their full legal
name. Staff can review that difference without changing the contact's name or
asking the Operator to repeat a successful verification.

1. Open the client in **Admin → Onboarding → Identity verification** and expand
   **Identity evidence & corrections**.
2. Paste the Stripe Dashboard verification-session or customer link and select
   **Link existing verification**.
3. Compare the **Operations contact**, **Saved cardholder evidence**, and
   **Stripe verified name**. Check the supporting evidence yourself.
4. Enter a reason for accepting the difference and check **I reviewed the evidence
   and confirm these names belong to the same person**. Do not enter identity
   document numbers, card numbers, or document images in the reason.
5. Review any additional warning about an earlier document-only verification or
   another account using the session. Select **Confirm same person and link** only
   when you also accept those displayed exceptions.

The confirmation applies to the exact Stripe session, report, and names reviewed.
If the evidence changes, select **Link existing verification** again and review the
current names. Changing the pasted link clears the previous confirmation.

Only authorized onboarding staff can accept a name difference. Stripe must still
show a successful verification with the required checks; this action cannot accept
failed, incomplete, redacted, or nameless evidence. Existing account and Location
checks still apply. Middle-name differences continue to match automatically.

The app records the reviewer, time, session, report, and reason before updating CRM
KYC to **Verified**. The linked record displays the reason after completion. The
verified name is shown for review but is not copied into the database.

Use **Reopen verification** to undo the link and return CRM KYC to **Incomplete**.
The review decision remains in the audit history. The audit records a confirmation;
an interrupted CRM update does not mean linking completed. Check the current status
before retrying.

Card ownership and signed-agreement review remain separate. See
[Accept an earlier identity verification](/staff/legacy-identity-verification) for
document-only checks completed under earlier requirements.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.