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

# Account Verification Channels

> Return additional email and phone verification channels for an account

By default, a user's login identifier (`loginId`) is also the channel that the user can verify. For example, the login identifier might be the user's email address or phone number.

Some accounts have additional verified channels that differ from their login identifier. For example:

* The login identifier is an email address, and the account also has one or more verified phone numbers.
* The login identifier is a username, and the account also has verified email addresses or phone numbers.

Returning these channels allows OwnID to offer the user an appropriate verification challenge, such as a one-time passcode (OTP) sent by SMS.

## Return additional channels

Extend the response from your [`/getOwnIdDataByLoginId` server-side endpoint](/building-blocks/build-server-endpoints) with either or both of these optional fields:

* `emails`: An array of verified email addresses associated with the account.
* `phones`: An array of verified phone numbers associated with the account.

```json theme={null}
{
  "ownIdData": "...",
  "emails": [
    "user@example.com"
  ],
  "phones": [
    "+123456789"
  ]
}
```

Only return channels that your system has already verified. Email addresses must use a valid [`addr-spec` format](https://www.rfc-editor.org/rfc/rfc5322.html#section-3.4.1), and phone numbers must use the international [E.164 format](https://www.itu.int/rec/T-REC-E.164/en), including the leading `+` and country code.

<Note>
  OwnID uses the returned email addresses and phone numbers only to orchestrate verification challenges. OwnID never persists these values.
</Note>

## Configure delivery providers

Returning additional channels makes them available for orchestration, but OwnID also needs a provider to deliver the corresponding challenge. Configure an [email provider](/explore/customize-emails/introduction) for email OTP challenges, an [SMS provider](/explore/customize-sms/introduction) for SMS OTP challenges, or both.