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

# Key concepts: registrations and orders

> Difference between registrations and orders, payment statuses, change history, and transfers.

Before operating the organizer panel, it helps to understand how Rocky Global models registrations, payment orders, and their history.

## Registrations vs. orders

| Concept          | What it is                                                                                                           | Examples                                                       |
| ---------------- | -------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------- |
| **Registration** | The participant's primary record in the event. It has a unique **locator** that never changes.                       | John Smith registered for Oceanman 5K                          |
| **Order**        | A payment transaction linked to a registration (or a store purchase). One registration can have **multiple orders**. | Initial fee, hoodie purchase, distance change, add-on services |

### Operational rule

As long as the registration is in **OK** status, the athlete is **officially registered**, even if a complementary order (store, fee change, extras) is still **pending** payment.

Typical example:

1. Order #1001 — 5K fee — **APPROVED** → registration **OK**.
2. Order #1045 — official hoodie — **PENDING** → the athlete remains registered; only the product payment is missing.
3. Order #1089 — change to 10K — **PENDING** → the registration temporarily moves to **CR** until the change payment is approved.

See order details in [Orders](/en/roles/organizador/finanzas-liquidacion).

## Order payment statuses

| Status                   | Meaning                                                                                      |
| ------------------------ | -------------------------------------------------------------------------------------------- |
| **APPROVED**             | Successful payment through the gateway (Redsys or Stripe).                                   |
| **OK**                   | No charge (100% discount or complimentary). Counts as paid.                                  |
| **FAILED**               | Gateway issues: card declined, insufficient funds, or declined transaction.                  |
| **PENDING**              | The user reached checkout but did not complete payment, or a fee change is awaiting payment. |
| **PARTIALLY\_CANCELLED** | Partial refund applied; the order keeps the non-refunded balance.                            |
| **CANCELADO**            | Order voided by full refund or administrative cancellation.                                  |

<Info>
  In each registration's detail you'll see all linked orders with status, amount, and line items. From **Finances → Orders** you can view the event-wide list.
</Info>

## Registration statuses

| Code          | Meaning                                                                                                                                                   |
| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **OK**        | Confirmed registration with at least one paid order.                                                                                                      |
| **CR**        | *Change Rate* (fee change). A distance/fee change is **pending payment**. The athlete remains registered if they already had a previously approved order. |
| **PENDING**   | Registration created but without approved payment on the main order.                                                                                      |
| **CANCELADO** | Registration cancelled.                                                                                                                                   |

## Change timeline and history

### CR code in history

When an athlete requests a **fee change**, the registration moves to **CR** status until the new order is approved. In the registration detail you'll see:

* The current active fee.
* Associated orders (initial, change, store, etc.).
* Audit notes indicating when the change started and which order is pending.

After the change payment is approved, the registration returns to **OK** with the new fee applied.

### Registration transfers

When **transferring** a registration to another athlete:

* The **original locator does not change**. It remains the same code shown on receipts, QR codes, and bib assignment.
* The owner changes (`user_id`) and the transfer is recorded in the registration's **transfer history** (date, sender, recipient, who executed the action).

This lets you trace the full timeline if an athlete presents an old physical receipt to claim a spot they already transferred: the locator is the same, but the history shows the current owner.

<Warning>
  A participant can transfer their own registration **only once** from the athlete self-service area. The organizer can perform additional transfers from the panel if they have permission.
</Warning>

## Relationship diagram

```mermaid theme={null}
flowchart TD
    R[Registration\nfixed locator] --> O1[Order 1: initial fee]
    R --> O2[Order 2: store / extras]
    R --> O3[Order 3: fee change]
    O1 -->|APPROVED| OK[Registration OK]
    O3 -->|PENDING| CR[Registration CR]
    O3 -->|APPROVED| OK
```

## Next steps

<CardGroup cols={2}>
  <Card title="Event orders" icon="receipt" href="/en/roles/organizador/finanzas-liquidacion">
    Complete transaction list.
  </Card>

  <Card title="Edit registration" icon="pen-to-square" href="/en/roles/organizador/gestion-participantes">
    Manual changes from the panel.
  </Card>
</CardGroup>