---
title: "Customer profiles: addresses, IDs and related people"
description: "Capture the details that matter for compliance and communication—addresses, identity documents and the people connected to a customer."
lastModified: "2026-06-13"
lang: "en"
wordCount: 521
url: https://qualyhq.com/training/contacts/customer-profile-ids-and-related-people
---
## Site navigation

- [For schools](/international-education/for-schools.md) — For international education schools
- [For agents](/international-education/for-education-agents.md) — For international education agents
- [Explore](/training.md) — Watch videos on how to use Qualy
- [About](/about.md) — Learn about Qualy's mission and values
- [Pricing](/pricing)
- [5-min demo](/demo.md)
- [Login](https://dashboard.qualyhq.com)

# Customer profiles: addresses, IDs and related people

> Store the structured details payments and compliance rely on.

## At a glance

- **Intended for:** Everyone
- **Available in:** All plans
- **Reading time:** 4 minutes
- **Last updated:** 31st May 2026

## Quick summary

On a customer's Profile tab you can store name and contact details, one or more addresses, identity documents (passport, national ID, tax ID and more), and related people (such as a parent or partner). These details support compliance and accurate communication.

## Overview

A customer's **Profile** is more than a name and email. It holds the structured details that keep payments smooth and compliance satisfied—addresses, identity documents and the people connected to the customer.

## Name and contact information

Set the customer's **first** and **last name**, **email**, **phone** and **preferred language**. Email matters most: it powers portal sign-in and notifications, and the preferred language sets the language of everything the customer sees.

## Addresses

Add one or more **addresses**, each labelled by type (for example **primary**, **billing** or **mailing**). Multiple addresses are useful when a customer's residential and billing locations differ.

## Identity documents

Store the customer's **IDs**—passport, national ID, driver's licence, tax ID, visa, student ID and more. For each, record the number, issuing country and any relevant dates.

Accurate identity details support compliance checks and reduce the chance of a payment being held for review.

## Related people

Capture **related people**—a parent, partner, friend, colleague or other contact connected to the customer—so the right people are on record when you need them.

Decide which fields your team must always fill in. Setting required fields in your customer settings keeps records consistent and audit-ready.

## Frequently asked questions

### What identity documents can I store?

A range of types including passport, national ID, driver's licence, tax ID, visa, student ID and others, each with a number and issuing country, and dates where relevant.

### Can a customer have more than one address?

Yes. You can store multiple addresses and label them by type—such as primary, billing or mailing.

### What are related people for?

They capture the people connected to a customer—such as a parent, partner, friend or colleague—so you have the right contacts on record.

### Can a parent pay for a student or get portal access?

Yes. A parent paying on a student's behalf can pay and use the customer portal to see what's owed and download receipts—anyone with an email can be given access. Schools and agents, by contrast, use the separate partner portal.

### Which profile fields are required?

First and last name and an email are the practical essentials (email is needed for portal access and notifications). You decide which other fields are mandatory in your customer settings.

### Can I set a preferred language per customer?

Yes. Set the customer's preferred language so their portal and notifications appear in it.

### Why does accurate identity data matter?

Correct names, IDs and addresses keep payments smooth and support compliance checks. Mismatched details can slow down processing.

## Prefer doing this via the Qualy API?

Head over to our developer docs for everything you need—endpoints, examples, and simple how-tos.

[View API Docs](https://docs.qualyhq.com/docs)

## More on Qualy

**Industries**

- [For schools](/international-education/for-schools.md) — For international education schools
- [For agents](/international-education/for-education-agents.md) — For international education agents

**Support**

- [Training](/training.md)
- [System status](https://qualyhq.statuspage.io/) — Qualy system status
- [Product updates](https://changelog.qualyhq.com) — As we work on Qualy, here we spotlight what we’ve learned and updated across our products
- [Contact](/contact-us.md)

**Product**

- [Demo](/demo.md)
- [Enterprise](/enterprise.md)
- [Testimonials](/testimonials.md) — Learn what some customers have to say about Qualy
- [About](/about.md) — Learn about Qualy's mission and values
- [Blog](/blog) — International education payments blog by Qualy
- [Trust center](/trust.md)
- [API](/api.md) — Qualy API for international education payments
- [Zapier](/zapier.md) — Connect Qualy to 7,000+ apps with Zapier

**Legal**

- [General terms](/terms-and-conditions.md)
- [Payer terms](/terms-for-payers.md)
- [Privacy policy](/privacy-policy.md)
- [BECS DDR](/becs-dd-service-agreement.md)
