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

# Notification Records

> Keep your own copy of every email notification Ingo sends to your recipients by designating a BCC address. Covers what is copied, what is not, and why retention stays under your records policy. Available for Notify — Classic and Notify — Managed Parties.

Many programs are expected to keep copies of the communications sent to their customers. Ingo supports this with a **client-designated BCC address**. Once configured, a copy of each email notification Ingo sends to your recipients is delivered to the address you provide. One-time access code (OTAC) emails are not copied (see [What is and is not copied](#what-is-and-is-not-copied)).

Because the copies land in a mailbox you own, **you control retention, search, and retrieval** under your own records policy and regulatory obligations.

<Info>
  You can set **one BCC address for each `participant_id`**. Your Integration Manager sets it during implementation, and it then applies to the email notifications sent under that `participant_id`. It is not set per recipient or per payment.
</Info>

***

## How it works

<Steps>
  <Step title="Provide a BCC address">
    Give your Integration Manager the address that should receive copies. Use a shared mailbox or an archiving or journaling system you own, not a person's inbox.
  </Step>

  <Step title="Ingo configures it on your program">
    The address is added to your notification configuration. No API change is required on your side.
  </Step>

  <Step title="Email notifications are copied">
    Each time Ingo sends one of your recipients an email notification, the same message is delivered to your BCC address. The recipient does not see the BCC address.
  </Step>

  <Step title="Your system retains the copies">
    Your mailbox or archiving system stores the copies for as long as your records policy requires.
  </Step>
</Steps>

***

## What is and is not copied

| Channel | Copied to BCC | Notes |
| - | - | - |
| Email notifications | **Yes** | Email notifications sent to your recipients for the configured program. |
| One-time access code (OTAC) emails | **No** | Excluded for security. Leaving access codes out of copies follows security best practice and limits fraud exposure. |
| SMS notifications | **No** | SMS messages have no BCC option. If you need a record of SMS, raise it with your Integration Manager. |

***

## Retention

Ingo does not provide an email archive or a retrieval service for recipient notifications. **The BCC copy is the supported way to keep a record of what was sent**, and the retention period is whatever your own policy sets.

<Warning>
  Keep the BCC mailbox active and able to accept mail, so it isn't full, deleted, or rejecting messages. That way every copy is received and kept.
</Warning>

***

## Recommendations

* **Use a mailbox built for records.** Journaling or archiving systems index messages and enforce retention automatically.
* **Use a dedicated address.** A dedicated address keeps notification copies separate from normal business mail and makes them easier to search.
* **Allow for volume.** You receive one copy for each copied email notification, so size the mailbox to match your program's volume.
* **Confirm before go-live.** Ask your Integration Manager to send test notifications in UAT so you can check that copies arrive at your BCC address.

***

## Setting up or changing the address

To add, change, or remove your BCC address, contact your Integration Manager.

If you have more than one `participant_id`, each one takes its own BCC address. You can point them all at the same mailbox or use a different mailbox for each. A single `participant_id` cannot copy to more than one address. If you need copies in several places, forward them from your BCC mailbox.