Forge Json
Get Started
clean

Clean Up KYC Customer Data

Normalize onboarding records, phone numbers, and country codes for downstream KYC workflows

  • Normalizes onboarding and KYC records
  • Detects phone↔country mismatches
  • Produces a deterministic downstream customer shape

Paste an onboarding record — instantly normalize phone numbers, country codes, and dates locally in your browser.

Continue

Why this package exists

Common problems

  • KYC onboarding data often arrives with extra whitespace, locale-specific dates, inconsistent country names, and phone-number formatting differences.
  • Phone numbers frequently include punctuation (`+1 (202) 555-0123`) downstream systems do not expect.
  • Country names (`United States` vs `USA`) need deterministic ISO alpha-2 codes for analytics, compliance, and reconciliation workflows.
  • Most onboarding flows have no upfront sanity check that the phone country code matches the declared country.

When to use

Use this before downstream KYC review, onboarding approval, fraud checks, or compliance workflows that require a deterministic customer record shape.

Expected outcome

A trimmed, normalized onboarding record with ISO country code, ISO 8601 date of birth, normalized phone number, and a `_country_check` sub-object confirming whether the phone prefix matches the declared country.

Automatically detects

  • Untrimmed names
  • Punctuated phone numbers
  • Country names
  • Locale-shaped dates
  • Phone/country mismatches

What the wizard asks

5 steps

Each step shows your input, the question, and a preview of the output.

  1. 1

    Trim whitespace from onboarding fields?· Optional

    Strip leading/trailing whitespace from names and other string fields before downstream matching or validation.

  2. 2

    Normalize the date of birth to ISO 8601?· Optional

    Convert locale-shaped dates like `01/02/1995` into deterministic ISO 8601 (`1995-02-01`).

  3. 3

    Normalize the phone number format?· Optional

    Turn `+1 (202) 555-0123` into `+12025550123` so downstream systems can process a clean E.164-style prefix.

  4. 4

    Convert country names into ISO alpha-2 codes?· Optional

    Map country names like `United States` and `United Kingdom` into deterministic ISO alpha-2 country codes downstream systems can rely on.

  5. 5

    Confirm the phone country code matches the declared country?· Optional

    Add a `_country_check` sub-object that flags phone↔country mismatches — a common onboarding and fraud-review signal.