# Registration and Payment Statuses

Every registration on a community event has both a **registration status** (who the registrant is and whether they are attending) and a **payment status** (where they are in the payment lifecycle). These statuses appear on the [Manage Registrations](/plan/community-events/manage-registrations.md) page and drive several downstream behaviors such as email eligibility, reporting, and refund options.

## Registration Statuses

Registration status reflects the registrant's role and attendance state for the event.

| Status           | Meaning                                                                                        | How It's Set                                                                                                                                                                                            |
| ---------------- | ---------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Attendee**     | The registrant is registered and plans to attend.                                              | Selected on the public registration form when the registrant chooses "I am registering as an attendee."                                                                                                 |
| **Non-Attendee** | The registrant submitted the registration on behalf of others but is not attending themselves. | Set automatically when a registrant selects "I am registering on behalf of someone else" during registration.                                                                                           |
| **Attended**     | The registrant was present at the event.                                                       | Set by an event manager via the **Mark Attended** bulk action or the **Attended** checkbox on the registration detail view. See [Manage Registrations](/plan/community-events/manage-registrations.md). |
| **Cancelled**    | The registration has been cancelled and is no longer active.                                   | Set when a registration is cancelled. Cancelled registrations cannot be edited or updated.                                                                                                              |

{% hint style="info" %}
**TIP:** Non-Attendee registrations do not receive event reminder emails and are excluded from attendance totals. They still appear in the registrations list and in the CRM when [Add Event Registrants to CRM](/plan/community-events/add-registrants-to-crm.md) is enabled.
{% endhint %}

## Payment Statuses

Payment status reflects where a registration sits in the billing and invoicing lifecycle. Payment statuses only apply when the event has fees configured in [Event Payment](/plan/community-events/event-payment.md).

| Status        | Meaning                                                      | How It's Set                                                                                                                                                                                      |
| ------------- | ------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Unpaid**    | A balance is owed for this registration.                     | Default status when a registrant completes a paid registration but has not yet paid (for example, selecting "Pay by Check").                                                                      |
| **Paid**      | The registration has been paid in full.                      | Set automatically when an online payment is processed, or manually when an event manager clicks **Mark Paid** on the [Manage Registrations](/plan/community-events/manage-registrations.md) page. |
| **Refunded**  | A refund has been issued for the registration.               | Set when a user with the **Refund** event permission processes a refund. Refunds appear as separate negative-total rows in the [Payment Details export](/plan/community-events/export.md).        |
| **No Charge** | The registration is complimentary and has no associated fee. | Set automatically for registration types with a $0 fee, for Non-Attendees on paid events, and for registrations fully covered by a 100% discount or promo code.                                   |

{% hint style="warning" %}
**NOTE:** Registrations with invoice history — including refunded or partially paid registrations — cannot be deleted, which protects historical payment records. Cancel the registration instead.
{% endhint %}

## Statuses in Exports and Reporting

Both registration and payment statuses are included in event exports:

* **Registration export** — Includes each registrant's registration status, payment status, and attendance state.
* **Payment Details export** — Lists one row per transaction with a **Transaction Type** of "Payment" or "Refund." See [Export](/plan/community-events/export.md) for details.

## Related Documentation

* [Manage Registrations](/plan/community-events/manage-registrations.md) — Update attendance and payment statuses in bulk or individually.
* [Email Notifications](/plan/community-events/email-notifications.md) — Understand how statuses affect which emails are sent.
* [Event Payment](/plan/community-events/event-payment.md) — Configure fees, discounts, and payment methods.
* [Registration Types](/plan/community-events/registration-types.md) — Define the registration options available to the public.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://support.pears.io/plan/community-events/registration-and-payment-statuses.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.